Yes, that would be a good idea. Let me just say though that in most cases
when WE rename a section (which we do occasionally) we don't care to have
the recordings inside renamed as well. For example: We may have a recording
of a meeting which we named "April Sales Meeting". Maybe we renamed the
section from "Sales" to "West Coast Sales" (to reflect that we're going to
have multiple regional sales sections) but the recording should still be
named "April Sales Meeting."
When you start a recording does it give you the opportunity to name the
sound file? As I recall, ON 2003 just named it according to the section
name or page name.
Do you allow people to take notes on different pages while they are
making a recording? While this may sound like the more flexible option, I
strongly recommend against it. You should practically insist that people
use a separate page (or page group) for each recording and a separate
recording for each page (or page group). Then, if someone decides to drag
and drop a page with a recording associated with it then OneNote can
easily find the correct recording to move with it and can easily modify
the links in the page pointing to the sound file to reflect the new
folder name that the sound file has been moved to. The actual file name
of the sound file can remain the same but the path to that file will have
changed. The page groups would have to be tied more intrinsically
together to keep from splitting up recordings or breaking the links to
major portions of notes all the time.
Without these kinds of restrictions (or at least warnings to the user)
then ON would have a rat's nest of links to keep track of and
continuously modify when people moved things around. If they cut and
pasted text that had a sound file associated with it most people will
expect that link to the sound file to stay intact. You must either warn
them to prevent them from ruining the integrity of their data or truly be
able to keep that link functioning no matter what the user did. I don't
think I would want the overhead that would be necessary to accomplish
this.
Now, if you kept all the sound files in a completely separate folder
structure then you could move the pages around and even allow cutting and
pasting of snippets of notes and the links would remain intact. However,
this would then require that the sound files always remain in exactly the
same place once they were created. It would also be very difficult to
keep track of when the last link to that sound file was deleted and ask
the user if they wanted to delete that sound file.
This is why I can't wait for the new file system. With files actually
records in a database it wouldn't matter where in the "directory
structure" a file was stored or moved to. The "directory structure" would
be just one more field in the record. All links to files will only need
to include the unique key of the record for the "file system's" database
engine to find the record. The only time you will need to modify a link
is if the file linked to gets moved to a different logical volume with
respect to the link itself.