Hi Mike,
At the BFI we've experimented with embedded metadata in the file outcomes from an outsourced photograph digitisation project, to achieve a workflow benefit. Thought it may be of interest.
We had no records for the physical objects in our collections management system, so working with our system supplier to use their beta metadata mapping, extraction and importing application, we established this workflow:
1. Digitiser embeds descriptive metadata in file headers (we used XMP Dublin core namespace and other XMP headers, as well as some IPTC). They used batch file processing from CSV capture method, I believe.
2. Digitiser FTPs files to watched folder in our application server
3. Tool extracts metadata, imports to database to create new records for physical object (populating mapped fields)
4. Tool continues, creating record for digital collection assets and populating mapped fields
5. Tool moves files to the destination storage / retrieval directory in media server
This embedded metadata approach served several purposes, not least populating two datasets in our system via watched folder automation. The supplier has now productised the tool, it's rather nifty.
Stephen
> On 4 Jun 2015, at 10:33, Mike Ellis <[log in to unmask]> wrote:
>
> Hi all
>
> Does anyone bother embedding museumy IPTC / EXIF data into (collections) images as part of their digitisation workflow?
>
> If so, why? I'd suspect that a "so that people knew where the image came from" reason may be one - but in reality do people actually _know_ about this data in order to get back to the source organisation? Or are tools like Google "upload an image" search or TinEye actually more used?
>
> Also - given that there is evidence that almost all social media sites strip out some or all of this data, is it still worthwhile? (http://www.controlledvocabulary.com/socialmedia/)
>
> cheers!
>
> Mike
>
>
>
> _____________________________
>
>
> *Mike Ellis *
>
> Thirty8 Digital: a small but perfectly formed digital agency:http://thirty8.co.uk <http://thirty8.co.uk/>
>
> * My book: http://heritageweb.co.uk <http://heritageweb.co.uk/> *
>
>
> ****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
> ****************************************************************
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|