In light of volatility of the created / modified timestamps, and the
mentioned inconsistencies across different OS, best practices for retaining
the origination time of the file would be to copy the original creation
timestamp to another format.=A0 For new files, ideally this would happen at
recording, or as part of the ingest process.
My recommendations for where are:
1) BWAV BEXT chunk
2) appending timestamp information into the filename.
3) an external database
4) any combination of above, or proprietary methods
Each method has its pluses and minuses of course, many of which are readily
apparent.
-jeremiah
On Sat, Apr 24, 2010 at 4:35 AM, simmosonics <> wrote:
>
>
> --- In <naturerecordists%40yahoogroups.co=
m>,
> Paul Jacobson <> quoted from
> http://thomas.kiehnefamily.us/whats_in_a_creation_date:
>
> "...In the case of Windows, the assumption is that any copy operation
> creates a new file and is treated as a new object, but leaves behind a
> paradoxical situation where the modification date precedes creation. In
> Macintosh, every copy of a file, so long as it is made on a compatible
> volume, can be traced back to the original object by creation date -- in
> essence, every copy of a Macintosh file is simply a new version, not a ne=
w
> object."
>
> Perhaps this has already been said, but...
>
> It would be great if an operating system's metadata kept three dates:
>
> Creation date [when the data in the file was originally captured/created]
> Copy date [only filled if the file is a copy]
> Modification date [when the file was last modified]
>
> No matter how many copies were made, the Creation date would never
> change...
>
> - Greg Simmons
>
>=A0
>
--
-----------------------------------------------------------
jeremiah moore | SOUND |
http://www.jeremiahmoore.com/
------------------------------------
"While a picture is worth a thousand words, a
sound is worth a thousand pictures." R. Murray Schafer via Bernie Krause
Yahoo! Groups Links
|