CHM Registry cataloging guide

FIELD To do Summit Page Name Summit Internal Database Name [notes about switching over to Summit schema] BRIEF DESCRIPTION LONGER DESCRIPTION RECOMMENDED FORMATTING QUESTIONS Sort of answers
TITLE FOR POST keep as is This is just the title of the film repeated to act as title of blogpost/Registry record? match title field “A word or phrase naming or describing the content.” (Summit) The registry uses the format for creating the title of a home movie from the originating archive.
MAP DATA keep as is Not in original Summit schema. How is this created? Is it different than the geographic location field? Or just the same information restated so it can be mapped? locations for map, use cities, states, etc. this is data used by the map plugin can we just use the location field to populate this data? SE – So, there’s location data which is human readable (i.e. “Madison, Wisconsin”) and there’s data that a map plugin needs (longitude, latitude). We need both – one for the map and one for searching location. This might need to be two fields – location and map data
AS: I propose changing this field title to “MAP DATA”
TITLE keep as is take from object match title for post field
SUBJECT switch to Summit term Subject(s)/Keyword(s) subjects_keywords subjects of item – determined by contributing archive “Topical headings or descriptive terms that describe the intellectual content. May include controlled vocabularies, authorities, or crowdsourced tags.” (Summit) Ideally, the Registry would use the terms from the Library of Congress Subject Headings. separate subjects with semi-colons do we have a list of subjects? No, the original Summit definition kept it open; we’ve relied on whatever the archives select. Would we want a limited selection of home movie related subject headings? Or send folks to the LCSH?
DESCRIPTION keep as is description of content in paragraph form “Describes intellectual content of item; includes summaries, abstracts, and general notes.” (Summit)
CREATOR TBD Name(s) names In the Summit Schema Name(s) covers all names and is repeatable. It recommends noting the person’s role somehow. We currently separate this field into Creator and Contributors. We have to figure out how to handle this. names of people responsible for creation of the home movie “An entity primarily responsible for making the resource. Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.” (DC) This field would include the filmmaker(s) or family responsible for the home movie. first name last name
SOURCE switch to Summit term Contributor/Submitter contributor_submitter source URL for video this should be an HTML link
DATE keep as is date of original item “Can include date created, date issued, a date range— exact or approximate. ISO 8601 primary standard notation recommended.” Ideally, dates would be recorded as YYYY-MM-DD, YYYY-MM, or YYYY. However, the Registry accepts dates however they were originally recorded. YYYY-MM-DD
RIGHTS switch to Summit term Licenses/Permission licenses_permissions rights statement as provided by contributing archive “Controlled list of licenses that indicate the permissions they allow for the object.” (Summit) “Information about rights held in and over the resource.” (DC) example:
“This item is available for reuse, please contact Northeast Historic Film”
LANGUAGE keep as is applicable if the movie has sound or titles “The chief audio or textual language.” (Summit) http://www.loc.gov/standards/iso639-2/php/code_list.php
THUMBNAIL URL keep as is Not in original version of Summit schema. We need to keep this and incorporate it officially into Summit Schema 2.0.
DURATION keep as is The running time or footage count of the film/video. HH:MM:SS
LOCATION switch to Summit term Geographic Location(s) geographic_locations Need to confirm I have this mapped correctly. see notes for map address info – these field could be combined see Map Address.
EMBEDDED VIDEO keep as is Not in original version of Summit schema. We need to keep this and incorporate it officially into Summit Schema 2.0. The HTML needed to embed a video player and the video file into a field. As HTML5 gets used more and more, this could be very simple. Right now, it’s very messy looking.
MATERIALS HELD BY TBD How is this different than Source? The organization or individual that currently has ownership of the film.
ORIGINAL FORMAT keep as is “Format of source material for object. May include controlled vocabularies.” (Summit) Examples include 16mm, Super 8, VHS, miniDV, etc. http://metadataregistry.org/concept/list/page/1/vocabulary_id/145.html
TRANSCRIPTION TBD Do we ever use this? Will we? If the film has dialogue, and if someone transcribe the dialogue, place that in this field.
COLOR/BW keep as is This was added by us in Omeka so it already meets the Summit schema rules. B&W, Color, Tinted, Toned
SOUND/SILENT keep as is This was added by us in Omeka so it already meets the Summit schema rules. sound, silent
GENRE keep as is This was added by us in Omeka so it already meets the Summit schema rules. use for amateur film Used for amateur films (home movies use tropes). “The manner or style in which the content is presented. May include controlled vocabularies.” (Summit) Ideally, the Registry will use the Library of Congress Genre Terms, but include the genres as described by the original archive. http://metadataregistry.org/concept/list/page/1/vocabulary_id/148.html we should provide a list. do we have one?
TROPES keep as is This was added by us in Omeka so it already meets the Summit schema rules. use for home movies “Common themes or devices. Could be controlled list based on developed taxonomy.” (Summit) CHM needs to develop a list of tropes for Home Movies to help describe home movies. we should provide a list. do we have one?
COLLECTION keep as is The field in the original Summit schema is called About the Collection. Do we rename it? It’s useful to keep some information about the collection itself in addition to the item and the archive/contributor. The name assigned to the collection from which the item is a part of. Use the collection name assigned by the participating archive. Once individuals begin to uploard films/videos to the Registry they can create a collection name, usually based on their own name.
ARCHIVE NAME keep as is Not in original version of Summit schema. Does the Contributor/Submitter field take care of this?
ARCHIVE LOGO keep as is Not in original version of Summit schema. But seems necessary.
ARCHIVE CONTACT keep as is Not in original version of Summit schema, which envisioned this being kept under the Contributor/Submitter field. How will this field change when we’re taking in stuff added by individuals or places that are archives?