Apr 062015
 

NMCVE8   intro & overall

  1. NMCVEL   title history in reverse start-order:
    1. NMCW8I    now: “

      best/proper discussion thread creation & other-management for common email/messaging & posting systems


      –broadened the topic

    2. NMCVEX   originally to next: “best titling of discussion threads starting with email/message-system Subject naming”  —
  2.  image:
    TBA
  3.  NMEOUM  What to do

    1. NMEOUZ   Follow the rules
  4. NMCWZH   pros thru cons (of doing the rules, especially “get right from the start the thread’s subject and, where applicable, its location”)

    1. NMDICS   dramatically important if doing routine topics, such as appointments or orders  or member/customer requests or tech support or similar greetings
      1. NMDIHO   as otherwise one get a mess of similarly vague or generically named threads, and with typical organization including finding limitations this then can’t be significantly fixed, so one can’t tell one from the other without opening up & reading each one.
    2. NMCX0N   dramatically important if the messaging/posting system has organization including finding limitations as:
      1. NMDJ5D  cannot change thing(s), notably name and/or location, after sent/posted, as…
        1. NMCX51   cannot rename a thread/message’s title/name/Subject-text after its been sent/posted
          1. NMD3A7  so if it starts bad, it remains bad
          2. NMCX6V   which is the norm for most all email & message systems
        2. NMD3AN   cannot move a message/post from one thread to another
          1. NMD3B6   which is still the unfortunate norm in seemingly most every messaging & even posting system, where the only exception I’ve run across so far is WordPress extensions to move comments.
      2. NMCX6E  lacks good or any search by post/message content
        1. NMDJ4G  as such search can then somewhat workaround (find things) especially when they weren’t named/located right especially when then fixing name/location is impossible.
        2. NMCX9F   not true for better email clients as Gmail.
        3. NMCX9P   very true for the VA’s Secure Messaging facility
      3. NMDJFR   lacks good or any dynamic multi-categorizing else multi-tagging else single folder-filing
        1. NMDJIF   as this can somewhat workaround other problems, similar as search does.
        2. NMDJN3   WordPress has multi-categorizing with renamable nested categories.
        3. NMDJJX   Gmail has multi-tagging, including renamable tags.
        4. NMDJKN   IMAP has single-folder filing, I think nestable.
        5. NMDJL5  the VA’s Secure Messaging facility has single-folder filing.
    3. NMCWZW   significantly cuts down the info clutter, loss, & repeat, and the time to gather together the good picture
      1. NMD4YI  especially as typically required as every time one goes to just make another decision, even every time just to schedule another appointment
      2. NMD4UH   especially when its been a few days or more since one hasn’t thought the matters discuss
      3. NMD4YU  so especially if your recipients know else sense this better way, then you can really piss them off by not doing this.
    4. NMCXCH  enables the keeping of much more useful records of what happened
    5. NMCX10   small temporary con: once understood, takes just a short time (1 minute to 2 seconds depending on how routine) to figure out the best way start/continue a conversation
      1. NMDIRY  but this short term small initial pain for the communication starter results in fast & huge gains for everyone.
    6. NMCXD9  con: takes some time learn & get and unfortunately a skill not yet taught standard.
  5. NMCVK0   the rules

    1. NMCVRN  In posting and messaging systems with discussion threading,
      1. NMEOZF   see much of “Rules including steps to properly post” except maybe for Meetup specific.
        1. NMEQDJ   much of the non-Meetup stuff to be moved here.
      2. NMDIVF    NMDIVF: get right from the start the thread’s title/name/Subject-text and, where applicable, its location
      3. NMCWX6  using it to manage events especially appointments
        1. NMCWY7   is best to define exactly 1 discussion thread per event and per groups of events.
        2. NMD5BD  the thread’s title/name/Subject-text (so topic)
          1. NMELWI   examples with extra explaining links added:
            1. NMELYT  “2014.11.13 next Psychology appointment(s) for Michael by Leigh”
          2. NMEP5U   format
            1. NMEMPE   start with the date&time range else start else point
            2. NMD560   then seemingly typically best to include the department else topic of the appointment
              1. NMD59B  as “dermatology
            3. NMD5EX   then include the matter according to what it is (as “appointment”, “meeting” or “event”), because that’s what it is,
            4. NMEN9A  then the parties notably involved
      4. NMEP8G  (systems) lacking nested discussion threads
        1. NMEP9J   include systems
          1. NMEPA3   hopefully decreasing but still most
          2. NMEPAJ   from most to least including (nested discussion threads)
            1. NMEPBF   WordPress: each post can have comments nested down to any (selectable) number of levels.
            2. NMEPBU   –below this point the full feature is absent
            3. NMEPCD   Meetup except that every event can have multiple discussion (comment) threads and the group’s discussion board can have multiple, unnested forums each with multiple discussion threads
            4. NMEPEO   every messaging system I can recall including standard email
            5. NMEQ3F  SMS: only creates threads automatically, seemingly only about 1 thread per every two addresses (phone numbers) talking on a particular day.
        2. NMEPH9   here if one wants to create a sub-thread (notably for a sub-topic), one has notably more work to do:
          1. NMEQ6C  Do one of the following:
            1. NMEQ6T   use the existing thread to handle multiple sub-conversations by new text/content having pointers/references to earlier content
              1. NMEQBQ   –the typical only practical solution for SMS.
              2. NMEQDJ   a big drawback is it is tricky to identify where the ends of every thread often without rereading quite a bit so very easy for even the skilled to miss earlier matter(s) still needing follow-up
            2. NMEQ7Z   somewhat laboriously create 2 threads (parent & child) which ideally both clearly link to the other
              1. NMEQAO  steps in order:
                1. NMEPJ4   first, if the parent thread doesn’t exist but might be needed, create it.
                2. NMEPLA   create the sub-thread including by
                  1. NMEPNO   have the thread’s title/name/Subject-text include, usually start with, a reasonably complete quote of the parent’s title which is also ideally a link to the parent, and (as followed by) by the words which uniquely define the parent
                  2. NMEPRH   if the thread’s title/name/Subject-text couldn’t include a link to the parent, as soon as possible after it (as ideally next line), say “parent: <url/>”
                3. NMEPU1   append, as reply to, the parent thread saying “just created new sub-thread on “[sub-thread’s unique name (not including parent name)]” [URL to subthread]”
                4. NMEPXH   –so immediately else soon both threads, parent & child, refer and ideally point to each other, so each can found from the other as readily as possible, including to avoid accidentally creating topical duplicates of either.
      5. NMCVRV   every discussion thread
        1. NMCWD9   should be one-subject-per-thread: should, as much as practical, only contain content which would fall-under the meaning of the thread’s title/name/Subject-text
        2. NMCVSN   is generally started by a New Post or New Email,
        3. NMCVLF   the thread’s title/name/Subject-text
          1.  NMD33V  is very key to effectively identifying all the messages/posts in one’s mailbox folder (as Inbox) and every thread, most especially/essentially when the system lacks good or any search by post/message content
          2. NMDL06   standard formats
            1. NMDL0P   are typically readily possible for routine topics
            2. NMDL2S   are generally very helpful when the convention is easy to read plus {easy to do for at least a large collection of thread types}.
            3. NMEHRM   are most generally defined here
          3. NMEHSG   for systems which don’t have an explicit field for the thread topic
            1. NMEHTE   as on standard email (other than the 1st email of the thread which has a Subject field), as WordPress comments, and on Meetup (both event listing comments, Pages (as title can’t be renamed) and Discussion Board posts other than the 1st one),
            2. NMEHVP   to the thread’s title/name/Subject-text, do one or more of these, from most preferred:
              1. NMEI54   use outline format, including as that automatically (by structuring) emphasizes the topic right on top of everything over which it applies.
              2. NMEI7P   make the title stand out, by doing one or more of these, from most preferred:
                1. NMEIF1   give it 1st thing, ideally on its own line.
                2. NMEIA1   use bolding –not possible in plaintext.
                3. NMEIAJ   use a proportionately bigger font –not possible in plaintext
                4. NMEIC2   put key words in ALL-CAPS, including all words if short.
          4. NMCVOJ   very much should be all of, from roughly most important:
            1. NME5CT   after the immediate name is prefixed in order with all its ancestor thread’s title/name/Subject-text (which is always “” (nothing) in an environment without a nested-thread/outline),
              1. NMCVXE   naming the topic meaningfully, including:
                1. NMDKMY   aiming to include universal details, especially if distinguishing, as, in often this order:
                  1. NMCZ49   the date&time range else start else point, whenever the subject is about that
                    1. NMCZ5M   in the format
                      1. NMCZ5V   ideally say “2015.04.05Sun1751-.06Mon0844pst”
                      2. NMEGVB   lexically sorts chronologically
                      3. NMEGVX   includes using generally-military date & time formatting
                    2. NMCZC1   likely first, before any other concept, or else near first
                      1. NMCZIC   as date&time is probably the topic most universal so helpful to include first to start with the familiar plus compare including otherwise incomparable topics/subjects.
                    3. NMEGC2   when item(s), as event(s) including appointment(s), date&time(s) haven’t yet been fully determined
                      1. NMEGFT   as typically the case when messaging/posting to someone to schedule them
                      2. NMEGDX   use as the date&time the earliest that they could be then follow it by say “ next”
                        1. NMEGI2   where this date&time…
                          1. NMEGMR   should be unique meaning never used for such a collection (as scheduling) before
                          2. NMEGOU   if appending to whatever is currently scheduled (the far typical case)
                            1. NMEGQG   should generally be the date&time of the most-in-the-future scheduling else, if none, the current date&time.
                    4. NMEGTF   for the date&time, reduce precision: as much as practical per NMDKKC: notably by dropping/not-giving digits to the right per the format, while still generally {truncating in full time subunits, so for instance not giving odd-looking “2015.0”  to cover all months except Nov & Dec}.
                      1. NMEGZ7   so for instance, for the subject date&time in scheduling a future event where the exact date&time is not yet determined (or perhaps may change), only go enough digits of precision (to the right) so that the topic won’t be confused with any other foreseeable events
                        1. NMEH8Z   so for instance if scheduling the next event where the last scheduled event was 2015.03.06Mon1239pst , if the next event be that same day possibly in that same hour, you are best to spell out the full date&time, but if that same day but not that same hour you should give only up to the hour, and if not that same day but that same month you should give up to the day, and if not that same month but that same year, give only up to the month, and if not that same year, give up to the year.
                  2. NMEMDY the department/topic (example),
                  3. NMEMET   the matter (as “appointment” or “meeting”)…
                    1. NMEN6M  followed without-space by  “(s)” if one or more or “s” if multiple.
                  4. NMEMKP  the parties notably involved
                    1. NMEMSS   generally from most to least focused on
                    2. NMEN22  each preceded by say a preposition describing its relation
                  5. NMENN5  unless a parent thread on the topic already exists and this is a significant effective sub-thread, per NMD4AY, generally should NOT include text/concepts as:
                    1. NMENO4   “Where & When” details & topic
                    2. NMENQX   particular person(s) participating
                    3. NMCWOS   NMCWOS:  “setting up” or “[re]scheduling” or “changing” or “moving” or “delaying” or “results|findings|conlusions” as a single thread on whatever the core subject is can better handle that (example: for events).
              2. NMDKKC  just enough details to be unique, else not much more than that, so only one thread with this name (within all mailboxes and/or posting locations) for the reasonably foreseeable future, including
                1. NMDKKZ   favoring the most distinguishing details
            2. NMCYN0  should NOT normally include words/concepts:
              1. NMD4AY  NMD4AY: [NOT words/concepts] that would (typically make the topic too narrow so) needlessly create/need additional threads due to one-subject-per-thread
                1. NMCW47   choose the topic big enough so this doesn’t happen
                2. NMD4PH  as  for the case of especially event threads NMCWOS
              2. NMCYOD   “me” or “I” or “you”
                1. NMCYPV   as this is a discussion, not a monologue or article/letter, so who this is only correct from one side of the discussion
                2. NMCYSB   and instead do 1 or more of:
                  1. NMCYT6   omit these words
                    1. NMCYW3   regularly works, as for medical appointments
                  2. NMCYTE   use names as “Susan”
                    1. NMCYUN   seems often just first names are sufficient (and also good privacy respecting)
                  3. NMCYVH   use the person’s title
              3. NMCYZ2   “notes” or “message” or “email” or “post” if referring to the message/post/thread content, as that is effectively redundant so unneeded.
            3. NMDKE2   optionally including a short unique ID, as KCGUID, to give a very short & reliably unique way to reference the thread.
            4. NMCW12   short
    2.  

  6.  success of this

  7.   design goals


  8. NMCVDS  section additional history, in start-time order:

    1. NMCV9R   until this point, content was in a specialized email system, including message {NE0EPF in say Id 366061717}
    2. NMCVAS    moving to here, now via copy to new draft (of 2nd latest & similar post) create this post http://1.JotHere.com/4556 then cut out else update content to fit;
    3. NMEOFT  much authoring: from 0 to ~131 points, including todo NMEQDJ ; also cut q(NMCZ3B  should include:); add to category “discussion/message board LXYYJA”, “rule N0BY8E”, “Universal Rules & Guidelines for Meetup.com L2PFGY LR7MKT”, “writing LGYLMM”,  “posting/messaging NMESUI”, “dicussion|conversation threading NMETMC”; spellcheck; apply N14GIY latest mod; publish 1 2015.04.06Mon1731pst.