Freckles said:
Is there any way to append a note to a file without effecting that
file's name.
In other words if I have a file "PHOTOGRAPHS" How can I add a note to
this file such as "Vacation in the mountains 2013."
Thanks,
Freckles
Sometimes, the OS adds information, by keeping an XML file
somewhere in the appropriate "library". Every OS will
keep modifying the approach, and what can be stored. The
info may be kept in a centralized place, rather than putting
one XML file next to each picture. I think for movies, they
may have done something different (perhaps media center ?
separate folder for each movie and XML file ?)
http://windows.microsoft.com/en-us/windows7/tag-pictures-so-theyre-easier-to-find
In general terms, you can annotate in several different ways -
1) Within the picture file itself. Schemes like EXIF, use
a separate 4CC code and description. Viewer software is
supposed to ignore 4CC codes they don't recognize. But
this area is complicated, in terms of what works, doesn't work,
what changes might bust some tool and so on. So if you use
EXIF or IPTC or <<four_letter_acronym_of_the_week>> the onus
is on the user to determine whether it's safe, transparent,
or whatever.
2) Alternate streams method. This method started with MacOS, which
kept a data fork and resource fork, for each file in the file
system. The resource fork provided a means to store separate info
from the data section.
The NTFS file system, uses "alternate streams" for this, so if
an application developer wanted, they could transparently add
descriptions to things. Kaspersky for example, in one release
of their AV software, kept track of whether a file had been scanned,
using an alternate stream.
To detect the presence of Alternate Streams, try this app.
http://technet.microsoft.com/en-us/sysinternals/bb897440
Since regular applications don't go looking for Alternate
Streams, this might be less dangerous than (1). Alternate
Streams only work on NTFS, and copying to FAT32, would lose
the Alternate Stream (a form of laundering, if you will).
3) A function added by means of libraries. What that means in
practice is, the OS recognizes certain folders or collections
of folders, need "features" added to them. For example, a
central XML file could keep comments for each picture, and
they would provide some means, on a per-picture basis, for a
user to add to the info. In the case of Media Center and movies,
it seemed to involve keeping a folder per movie, and then adding
a file next to the movie to describe it. These would be examples
of schemes that only exist inside the library, and not at some
arbitrary storage location (like, right underneath C
.
The information is lost in that case, if the file is transferred
to a foreign system.
The scheme in (1) is the most robust, in that copying the file
to a BeOS computer, your added info would not get lost. But on
the other hand, any changes made to the file, might have undesired
side effects that you can't predict in advance. (Like, copying the
file back to the camera, and having it barf.) Any other schemes which
store the info outside the file, have the exposure that the
annotation gets lost, if you transfer the file in certain ways
(to foreign computers, devices, or file systems).
So while I like the other Paul's suggestion, the onus is on the
user to do the research when using these.
http://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model
http://en.wikipedia.org/wiki/Exchangeable_image_file_format
As far as I know, this could be one of the first tools, to allow
adding annotations internally to the files. (Unlike the MacOS
generalized scheme, that used things like Resource Fork and only
worked for as long as you didn't carelessly lose the fork.)
http://en.wikipedia.org/wiki/ExifTool
*******
A forum used by photographers, may have more info on the side
effects of some of this stuff.
http://www.dcresource.com/forums/showthread.php?37781-EXIF-Reader-gt-Focus-Distance-Info
In your search engine, try...
site:dcresource.com exif
as a search. You can do site specific searches to find stuff.
HTH,
Paul