Expanding Cultural Heritage Photo Metadata Survey
(IPTC and SCREM)
Your Details
This will help us to know who you are and what your perspective is. If you prefer not to share your name, please include any other information that gives context to your input.
Name
Your answer
Job Title
Your answer
Organization
Your answer
1. IPTC fields
DEFINITION:
Additional heritage fields to be added to the IPTC schema

PURPOSE:
For information about cultural objects and their images which can be associated with image files for general use.

EXAMPLE USE CASES:
Covers images sent electronically or downloaded from websites
- Images delivered to publishers for licensed use
- Images downloaded by picture researchers onto their desktops
- Images downloaded from the internet for educational use

Do you agree with the purpose for the IPTC fields?
Comment on purpose for the IPTC fields:
Your answer
Do you think the use cases covered by the above are sufficient?
If you have other use cases which should be mentioned please add them here:
Your answer
2. SCREM (Schema for Rich Embedded Metadata for Media Files)
DEFINITION:
A schema with a rich set of fields to enable interchange of heritage metadata between and within heritage organisations, which could be supported by a custom XMP panel.

PURPOSE: For information about cultural objects and their images for interchange between departments and organisations wiorking in the cultural sector. This schema includes more detailed information about the objects, but stops short of being a full collections management schema.

EXAMPLE USE CASES:
- Interdepartmental transfer of images within a heritage organisation eg. from collections management to picture library
- Exchange of data between organisations
- Upload to portal sites

More details on the background to the project are available at:
http://electriclane.blogspot.co.uk/2013/08/heritage-metadata-at-iptc.html

Do you agree it is useful to create SCREM for embedded data interchange between heritage organisations?
Comment on usefulness of SCREM:
Your answer
Do you agree with the purpose for the SCREM fields?
Comment on purpose of SCREM fields:
Your answer
Do you agree with the use cases for SCREM fields?
If you have other use cases which should be mentioned please add them here:
Your answer
3. The criteria for selecting fields
Criteria for IPTC Heritage fields:
These include fields which:
- hold information about the digital image
- identify source, creator and copyright of artwork
- provide links to more granular data on the web
- provide descriptive data about the artwork/object for the general end user
- are useful for image retrieval


Criteria for SCREM fields:
Includes fields in IPTC Heritage Subset above plus fields which:
- hold more detailed data on the object and its provenance
- are more specific to institutions holding the work and not needed by general users
- can be mapped to institutional databases without loss of meaning

Fields NOT included in SCREM or IPTC, but which are found in collections management schemas.
These include fields which are:
- about movement, condition, exhibition of work
- specific to institution holding the work and not needed by other users or organisations
- about detailed provenance (former owners etc)
- about monetary value or insurance of work

Do you agree with the criteria we have set out for additional IPTC fields?
Comment on criteria for IPTC fields:
Your answer
Do you agree with the criteria we have set out for SCREM fields?
Comment on criteria for SCREM Fields:
Your answer
4. Fields
This is an initial selection of fields with tentative semantics, simply to get the discussion started:
https://sites.google.com/site/culturalheritagemetadata/
Do you feel this is generally a good approach?
We will make specific field selections and definitions in the next phase.
Comment on approach:
Your answer
Do you have any other comments about the project?
Your answer
Would you like to be part of an active working group?
Please provide your email:
Email
Your answer
Submit
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service