when event date and file creation date are different...

[lulumine]

I have a lot of film-based photographies to digitize (scan or photo from photo), and I want to keep both origin date (the event in past) and digitalization date (file creation today) in metadata, being sure that any further modifications will not update them.
Does anybody have return on experience about it (it seems to be a common expectation...) ?
Is it possible to manage it properly with a couple of the 3 standards metadata fields :
- Date time original
- Date time digitized
- Date content created
Or do I need to use other exif fields? or customized XMP fields?
Thank you very much for your help.
Olivier

[Hert]

The specs say this about these fields:
Date Time Original: Date and time when original image was generated
Date Time Digitized: Date and time when image was stored as digital data, can be the same as DateTimeOriginal if originally stored in digital form
Date Content Created: The date the intellectual content of the document was created (rather than the creation date of the physical representation)

Hope that helps you to decide which date goes where.

[lulumine]

Thank you very much for your anwser : I've made some tests and was near of using Date content created fixed with ExifTool, but it seems now not so simple!

Considering an image of the Nativity (mural painting) from Sandro Bocelli, recorded today with a digital camera (or a scan) from a by film-based photography recorded itself 20 years ago, I have 4 dates I would like to register :
- event date (nativity) : 0000:00:00
- painting date : 1477:01:01 (estimate between 1476-1477)
- 1st analogue shoot : 1994:07:09
- 2nd digital shoot : 2014:07:09

Does somebody already have had to manage this kind of situation with pre-defined date fields, assuming that the three first one dates should be secured from overwriting (import, copy, metadata update by a DAM, ...)
A first idea should be :
- Date Time digitized = Date Time Original = 2nd shoot date (automatically created by the digital camera)
- Date content created = painting date
- but what about the 1st shoot : Date Time Original overwritten with ExifTool ??? but it's not fully secured from overwritting...
- and the event date ???

Is it possible with date fields? or should I use string fields (or give up information)?
Thanks in advance.
Olivier

[Hert]

How about this:

- painting date : 1477:01:01 (estimate between 1476-1477) -> date time original
- 1st analogue shoot : 1994:07:09 -> date time content created
- 2nd digital shoot : 2014:07:09 -> date time digitized
- event date, perhaps in a custom field?

[lulumine]

I've launched a first batch with your proposal, and wait for few days before having such experience on it (evaluate the risk to overwrite these dates...).

btw, changing these dates changes also both folder and name used for each files impacted by my renaming rule : the only way I've found to manage it is to create the new folder and move the files manually in the folder display : Have I a way to reapply the renaming rules and move the files accordingly, as in ingest process (I've tried to ingest again, but received the message that "files has been probabiliy already ingested") ?

[Hert]

Not knowing how your folder structure or what your file naming structure is, I see two options;

1. Move the files to a temporary folder, rename them, delete the folder from catalog and then import from that folder again
2. Use a rename rule that includes folder naming. you'd have to know exactly what you're doing though.

On a three level folder hierarchy, a rename rule for existing files could be:

Code: Select all

..\..\..\%yyyy\%yyyy-%mm\%yyyy-%mm-%dd\%yyyy%mm%dd-%FileName.%FileExtension

Folders will be created as needed.

[lulumine]

1. Move the files to a temporary folder, rename them, delete the folder from catalog and then import from that folder again

Yes, and we can imagine an option for ingest process (called "move" : an alternative to "copy"?), assuming that files to be moved must be already ingested (rejected if not), and using the embedded Folder/renaming rules....

2. Use a rename rule that includes folder naming. you'd have to know exactly what you're doing though.

Should be an option in the "operations" menu, asking for a folder/renaming rule and moving the current selection accordingly....

=> but for both, I don't know if it can be considered as a core feature....

[Hert]

2. There is a rename option in the Operations menu. It's called "Rename Files". That is the option that I mean and where you can enter the rename rule by clicking the Text tab.

[lulumine]

I've understood and identified your proposal 2.
My concern was it would be more clear to me to search for a MOVE option versus a RENAME one in order to move a file (very clear with separate boxes for folder & renaming rules).
But ok, it works with renaming !

[bimo]

Olivier,

according to the MWG it must be:
- 1st analogue shoot : 1994:07:09 -> DateTimeOriginal
- 2nd digital shoot : 2014:07:09 -> DateTimeDigitized

For the painting: additional informations for an artwork or object shown in the picture are handeld within the IPTC Extension section; so:
- painting date : 1477:01:01 (estimate between 1476-1477) -> DateCreated (Artwork/Object Detail)

- event date (nativity) : 0000:00:00
Well, this item isn't covered by any standard I know of. If you need a separate date field then be lucky to be a PSU user and create a custom field. Otherwise: the standards for the Event field allow not only a title but also a description as content, thus it could be "Nativity; Date: 0000:00:00" or whatever would fit better.

The DateContentCreated is off topic because afaik it's the date the metadata information has first been added to the picture.

Sorry for my late contribution, hth!
Michael