Conference azur::mcc

| In talking  with  people from the field, I've received feedback
| saying that access  to  the DECmcc notes file is time consuming
| from remote locations.  The average number of notes/replies can
| be in the area of 15-30 per day.

    If this is the only problem that needs to be solved, I'd suggest a COM
    file that extracts the new notes into a local file.  Something like
    this:

    	$ notes
        open/noautomatic mcc
    	save /all /unseen /seen new_mcc_notes.txt 
    	close
    	exit
    	$ exit

    This saves all the unseen notes and marks them as seen in your
    notebook.  It can be run in batch over night and all the previous day's
    notes will be available locally.  Skipping over notes that you aren't
    interested in is quick this way.

    I'd prefer to keep the conference as it is.  If there is a split, we'll
    have 3 conferences to reference: the developers conference, the
    end-user conference, and the old MCC conference to make sure the note
    we've entered hasn't already been discussed.

If we all made better use of title names and keywords, the notes file
would be easier to navigate.

Its nice having ONE place to look for information on DECmcc!

    I think it would be more time consuming having it in two; you'd have to
    read at two places to look for answers.
    
    /Nils
    
    PS.
    By the way, I'm reading this notesfile in Stockholm, Sweden and I think
    the responstime is quite good.  I also have a batchjob that extracts
    all unread notes and mails them to me at the customer site a couple of
    times a day.  It's a very good way of reading the notes.   DS.
    

RE .7

>    If this is the only problem that needs to be solved, I'd suggest a COM
>    file that extracts the new notes into a local file.  Something like
>    this:
>
>        $ notes
>        open/noautomatic mcc
>        save /all /unseen /seen new_mcc_notes.txt 
>        close
>        exit
>        $ exit
>
>    This saves all the unseen notes and marks them as seen in your
>    notebook.  It can be run in batch over night and all the previous day's
>    notes will be available locally.  Skipping over notes that you aren't
>    interested in is quick this way.
>
>    I'd prefer to keep the conference as it is.  If there is a split, we'll
>    have 3 conferences to reference: the developers conference, the
>    end-user conference, and the old MCC conference to make sure the note
>    we've entered hasn't already been discussed.
>
>
You're right !

There is a great tool that I use to read remote notes. It's called RNU (Remote
Notes Utility), which does nightly extracts, presents an overview of the new
entries for the day, from where you can pick the ones that are of interest to
you. You can also keep a local directory of the notes, in which you can search
for keywords, and get to the notes having the keyword in their title in a quick
way. 

See     REGAL::RNU for more info.

EricV.

>
>    If this is the only problem that needs to be solved, I'd suggest a COM
>    file that extracts the new notes into a local file.  Something like
>    this:

There are a couple of utilities going along to avoid bad response times to
conferences. I currently use PAVN and it is great. Take a look at ODIXE::AVN or
REGAL::RNU for more info.

About splitting I don't think it is a bad idea. At least to have a "bugs
reporting" conference away from a "general purpose" one. Anyway, as someone
said, the key issue is to encourage everyone to use meaningful titles in topics
and replies, such as "Problem: MCC-E-XXXXXX Something" and not "Problem with
MCC" or "Help wanted". In this way it will be possible to search all over the
conference with no or little waste of time.

Cheers

Luis

    I find it usefull to have all the information in a single place. Sure,
    some of it is of no direct interest to me.  But knowing the information
    exists and can be found in ONE place makes things easier when I change
    my mind (or a customer changes it for me) later.
    
    Regards,
    
    Glen R.
    

	From the  responses  to  date,  it  appears clear to me that we
	should leave things as is.

	I'll write lock this note, and we can all get back to work.

	Thanks for your input on this.