Print

Print


I think you cannot rely on my schema to be correct, especially if the ISO recommends something else, they may decide upon Dublin Core or VRA or something new. :-(

...a baseline approach might be to just start entering this stuff in Adobe Bridge (other editors are available, Media Pro for example), because if and when you get a DAMS this embedded metadata in JPEGs and TIFFs will be able to be read. A lot of it can already can be read at an OS level.

It's a heck of a lot easier than entering it retrospectively.
Tony

cid:image001.png@01CF86F9.22C2BC80

Tony Harris 
Digital Media & Photography Officer
Government Art Collection
tony.harris @culture.gov.uk | 020 7211 2426
cid:image002.jpg@01CF86F9.22C2BC80@govartcol  cid:image003.jpg@01CF86F9.22C2BC80 /governmentartcollection | www.gac.culture.gov.uk



On 13 October 2016 at 20:23, Michael Hall <[log in to unmask]> wrote:
Hi Tony
The digital dustbin is an apt analogy, something I've thought to myself as I've scoured the ever growing heap off un regulated media for my lost ring!
Your schema will be an invaluable asset for current or future DAM ingest.
I wonder also if thought had been put into organisations without a DAM and how they can, at the very least futureproof themselves and or what those tools and approaches might be?
Regards 
Michael


Sent from my red apple

On 13/10/2016, at 6:37 PM, Tony Harris <[log in to unmask]> wrote:

Hi Michael, In a word yes, the schema I sent earlier is actually for digital photographs taken by GAC staff. These are not objects but an important reference tools for us and so need to be found easily, which is why they are going into the DAMS with as much metadata in them as we can stuff into them. I am now testing the search criteria and looking to create a standardised vocabulary for staff to use when entering metadata. The system politely forces them to enter information because, no metadata, no ingestion. A DAMS with no metadata is just a virtual bin liner full of JPEGs waiting for the digital dustman, is the message we are trying to convey to staff.

Ironically the schema for objects has less fields because we are not using the location fields, events etc.
Regards
Tony

cid:image001.png@01CF86F9.22C2BC80

Tony Harris 
Digital Media & Photography Officer
Government Art Collection
tony.harris @culture.gov.uk | 020 7211 2426
cid:image002.jpg@01CF86F9.22C2BC80@govartcol  cid:image003.jpg@01CF86F9.22C2BC80 /governmentartcollection | www.gac.culture.gov.uk



On 13 October 2016 at 18:20, Michael Hall <[log in to unmask]> wrote:
Hi Stephen
I think there's an interesting metadata conversation to be had around non-collection related Imagery and ephemera.
This kind of material often relates to the day to day running of a cultural institution, the events, staff, collecting trips etc.
Over time some of this material becomes an important part of the collections, creating a narrative weave as it where between the collections and the day to day. A kind of looking at ourselves.
Observationally material like this which is only 10-20 years old seems to be of interest to the wider public and staff.
Where I was working at Te Papa, NZ, the imaging team had long been struggling with how to get visibility for this kind of media and how best to enter appropriate metadata. The work was often commissioned with short term objectives in mind, and the onus for metadata input invariably fell on us.
We experimented with Adobe Bridge, creating shared metadata templates with pre-populated keywords and smart filters for pre populating folders with images that met a certain metadata criteria. I believe adobe Drive allows integration between Bridge and DAM systems although I have heard it can be quite laggy something we found with working across servers.
With a DAM on its way some of these questions will be answered and metadata will be entered as a matter of course.
The questions I would have for the group are,
Do people think this non collection material needs the same care as collections?
How do you ensure standards are adhered to in what can be quite complex material often made by people who are unaware of things like metadata?
Is there anyway to rate the importance of material, and therefore how much time should be spent with it?

Michael



Sent from my red apple

On 13/10/2016, at 8:20 AM, Stephen McConnachie <000008d6dc4651a2-dmarc-reques[log in to unmask]> wrote:

Sorry Jennifer, you're absolutely right. Here's some detail:

DAMs is Digital Asset Management system, sometimes also called Media Asset Management (MAM) where the system is content-aware. Essentially a DAM is the system which controls ingest, storage and retrieval of digital assets (often cultural heritage collections, but also banks, oil and gas, media organisations, anywhere large numbers of digital files are stored and retrieved):

IPTC IIM is the Information Interchange Model (essentially, a standard and protocol for embedding descriptive metadata file headers) the International Press Telecommunications Council, a consortium of media organisations:

XMP is the Extensible Metadata Platform, originally by Adobe but now an ISO standard (International Organisation for Standardisation), also an embedded metadata standard, slightly complicated in that IPTC IIM describes some of its attributes within an XMP schema. It might be accurate to say that XMP can embed some but not all IPTC attributes:

FADGI is the US Federal Agencies Digitisation Guidelines Initiative, probably the most influential best practice framework for digital preservation, with two main focus groups, one for images and one for audio-visual:

The Library of Congress and FADGI publish lots of excellent resources on file formats, criteria for selection, etc. It's my first stop for any considerations around digital asset (other resources are available...  e.g. TNA aka The National Archives, Presto Centre, Digital Preservation Coalition):

Sent from my iPad

On 12 Oct 2016, at 19:47, Jennifer Layton <000008122cbf19f4-dmarc-reques[log in to unmask]> wrote:

I would be really helpful if we could at least include a glossary for the acronyms we are using on the list when we post. Industry jargon can be a real barrier to understanding when you are trying to learn/

This subject is of huge interest to me and I haven;t got the first ides what a DAMS or IPTC, or FADGI for that matter :D

Thanks!

On Wed, 12 Oct 2016 at 17:15 Tony Harris <[log in to unmask]> wrote:
Hi Stephen,
We took the decision to have a combined CMS & DAMS and use IPTC. Once an image is ingested the user is forced to enter metadata about the creator/rights and then because part of the filename matches the object record the CMS auto populates the IPTC Artist info post ingestion. The metadata is then checked by an admin and the image appears.

We take the view that rights, creator and artist info are the minimum standard, however, as I mentioned last week the forthcoming ISO standard on digitisation should clear up recommendations about what data goes into an image, so you can look forward to having all this resolved and you may even be able to say you are ISO certified.

"This will ensure the accurate capture, encoding, and long-term preservation of digital representations of these cultural heritage materials."


Best regards
Tony

cid:image001.png@01CF86F9.22C2BC80

Tony Harris 
Digital Media & Photography Officer
Government Art Collection
tony.harris @culture.gov.uk | 020 7211 2426
cid:image002.jpg@01CF86F9.22C2BC80@govartcol  cid:image003.jpg@01CF86F9.22C2BC80 /governmentartcollection | www.gac.culture.gov.uk



On 12 October 2016 at 16:56, Stephen McConnachie <000008d6dc4651a2-dmarc-reques[log in to unmask]> wrote:
Hello MCG,

I know there has been substantial (and brilliantly useful) discussion in the MCG list of embedding and managing metadata in image file headers, IPTC, XMP, social media stripping, and many other areas.

I'm interested in learning what collecting organisations are doing in real terms when they digitise their image or indeed text collections, both in-house and outsourced.

At the BFI we have approached this at various points on the spectrum in various projects, from most ambitious (digitisation supplier will embed descriptive metadata in XMP / IPTC, and we will auto-create CMS records from those, by watching a folder and automating extraction / posting to db) to least (generic creator and generic rights statement only).

I'm interested in developing a model which accepts both extremes, and defines a minimum set and an ideal set, for use in digitisation project scoping and planning. I'd like to benchmark what people are doing in real projects, from ambitious to barely there, and refer to the obvious documents, and come up with a framework within which to select, per project, based on budget, timescale, nature of the collection being digitised, access or preservation as driver, etc

I've digested the obvious documentation, eg the FADGI Still Image Working Group stuff:
http://www.digitizationguidelines.gov/guidelines/digitize-core_embedded_metadata.html
and
http://www.digitizationguidelines.gov/guidelines/digitize-core_embedded_metadata.html

And TNA:
https://nationalarchives.gov.uk/documents/information-management/digitisation-at-the-national-archives.pdf

But I'd love to hear what you're doing within this spectrum of all-known-data-goes-in, to creator-and-rights-only. Do you bounce btween these extremes, based on budget? Do you sit somewhere in the middle as a consistent policy?

Apologies if this has happened very neatly somewhere and I have missed it - please redirect me?!

All the best,
Stephen

****************************************************************
       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/ ****************************************************************
--
Best

Jenn Layton

M: 07948 554 136
T: @jenn__layton
**************************************************************** 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/ ****************************************************************
**************************************************************** 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/ ****************************************************************
**************************************************************** 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/ ****************************************************************