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):
https://en.m.wikipedia.org/wiki/Digital_asset_management

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:
https://en.m.wikipedia.org/wiki/IPTC_Information_Interchange_Model

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:
https://en.m.wikipedia.org/wiki/Extensible_Metadata_Platform

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:
http://www.digitizationguidelines.gov/

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):
http://www.digitalpreservation.gov/formats/

Sent from my iPad

On 12 Oct 2016, at 19:47, Jennifer Layton <[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."

http://www.imaging.org/ist/resources/standards/materials.cfm

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 <[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
W: www.jenlayton.rocks
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/ ****************************************************************