Object Metadata Application Profile

Action needed

(modeling step)

PropertyPredicate (formerly Elements)Sufia property, predicate, rangeRangePredicate URIsearch-able?FacetRequired/ Recommended/ Optional

multi

valued

Field Type/FormattingAuthoritySufia Display locationNotes (asdasdasdasdasdextendingthiscolumnspaceasdasd)
XTitledcterms:title

title, predicate: ::RDF::DC.title

rdfs:Literal (string or int)

http://purl.org/dc/terms/title NoneRequired*NoFree textNoneDescriptions > Title*Currently Sufia autofills this with filename.
XExternal IDdcterms:identifier

identifier, ::RDF::DC.identifier

rdfs:Literalhttp://purl.org/dc/terms/identifier NoneRequired*Yes*Free text with drop-downNoneDescriptions > IdentifierRe-label Sufia element as External ID. Different drop-down label choices depending on depositor or resource type? Object ID, Bib. #, Item #, OH Interview #, AS Ref. ID. Capture Accession # for archival collections. Store the number with a specific prefix based on drop-down choice. Opac link can be displayed by computing on this field.
XCreatordc11:creator

creator, ::RDF::DC.creator, range: "dc:Agent"

note in sufia this is the creator of the file. we are using it more at the work-level

none, move to edm:Agenthttp://purl.org/dc/elements/1.1/creator NameRequired, if availableYesAuto-complete; Label itself is drop-down optionFAST: Personal Names, Corporate Names (suggest00, suggest 10); VIAF (alternative option - API info: https://platform.worldcat.org/api-explorer/VIAF); Local data? (see notes) Allow non-authority names? Discuss NACO workflow. Should we combine Publisher here as well? Is Publisher important enough to warrant a separate facet?
XContributordc11:contributor

contributor, ::RDF::DC.contributor, range: "dc:Agent"

http://purl.org/dc/elements/1.1/contributor  
XPublisherdc11:publisher

publisher, ::RDF::DC.publisher, range: "dc:Agent"

http://purl.org/dc/elements/1.1/publisher Descriptions > Publisher
XArtistmarcrel:art http://id.loc.gov/vocabulary/relators/art  
XAuthormarcrel:aut http://id.loc.gov/vocabulary/relators/aut  
XIntervieweemarcrel:ive http://id.loc.gov/vocabulary/relators/ive  
XInterviewermarcrel:ivr http://id.loc.gov/vocabulary/relators/ivr  
XManufacturermarcrel:mfr http://id.loc.gov/vocabulary/relators/mfr  
XPhotographermarcrel:pht http://id.loc.gov/vocabulary/relators/pht  
XDate of Workdcterms:date 

edm:TimeSpan

DC range is rdfs:Literal

http://purl.org/dc/terms/date Date (Range)Required*Yes[YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY]NoneDescriptions > Date CreatedDate ranges? Circa? Undated/no date option? Date converters for Gregorian vs. Julian issues?
XDate of Publicationdcterms:issued rdfs:Literalhttp://purl.org/dc/terms/issuedRecommendedYes[YYYY-MM-DD; YYYY-MM; YYYY; circa YYYY]None Have Date Published label as a drop-down choice for main Date field.  
XPlace of Manufacturemarcrel:mfpbased_near covers all this http://id.loc.gov/vocabulary/relators/mfp        
XPlace of Publicationmarcrel:pup

based_near, ::RDF::FOAF.based_near, range: "http://xmlns.com/foaf/spec/#term_SpatialThing"

none, move to edm:Place?http://id.loc.gov/vocabulary/relators/pup Place/Location?Recommended, if availableYesAuto-complete; Label itself is drop-down optionFAST: Geographics (suggest51); VIAF (alternative option)Descriptions > LocationCurrent Sufia authority service is GeoNames. See VIAF, TGN, FAST, and GeoNames use comparisons on Basecamp.
XPlace of Interviewmarcrel:evpditto above http://id.loc.gov/vocabulary/relators/evp        
XTypedc11:type

resource_type, ::RDF::DC.type, range: "rdfs:Class"

nonehttp://purl.org/dc/elements/1.1/type TypeRequired*YesDrop-down menuSelected from DCMI TypeDescriptions > Resource typeDrop-down choices: Moving Image, Still Image, Physical Object, Sound, Text.
XGenre

http://chemheritage.org/ns/hasGenre, moving to

edm:hasType
 

none, moving to skos:Concept

edm:NonInformationResource

http://www.europeana.eu/schemas/edm/hasType GenreRequired*YesDrop-down menuSelected from FAST: Topical, Form/Genre (suggest 50, suggest 55); TGM (possible expansion for graphic materials); AAT (possible expansion for museum objects) Drop-down choices (to be finalized with curators): Photographs, Oral histories, Rare books, Manuscripts, Painting, Prints, Scientific apparatus and instruments, Artifacts?, Ephemera?
XMedium

dcterms:medium

chf:medium? (see github notes)

 

dcterms:PhysicalMedium

http://purl.org/dc/terms/medium None (maybe for Museum objects later)OptionalYesAuto-completeAAT  
XExtentdcterms:extent  http://purl.org/dc/terms/extent NoneRecommendedYesNumeric free text?None Variable extent/dimensions across collections. Set standard for measurements.
XLanguagedc11:language

language, ::RDF::DC.language, range: "dc:LinguisticSystem"

nonehttp://purl.org/dc/elements/1.1/language LanguageOptionalYesAuto-completeTBDDescriptions > LanguageWould it be useful to set default to English?
XDescriptiondcterms:description

description, ::RDF::DC.description

 http://purl.org/dc/terms/description NoneRecommendedMaybe?Free text with full HTMLNoneDescriptions > Abstract or SummaryWISYWIG editor possible? Does OH want an Abstract field in addition to Description?
newInscription

crm:E34_Inscription OR ecrm:E34_Inscription

    NoneOptionalYesFree text with full HTMLNone There are two OWL implementations of the CIDOC CRM vocabulary. I'm not sure if one is better or makes a difference? I think this field could have one larger text box for filling out inscription text, and another single-line text field for inscription location.

X

Subjectdc11:subject

subject, ::RDF::DC.subject, range: none but note that it is intended for use with non-literal

none, move to skos:Concepthttp://purl.org/dc/terms/subject Subject/TopicRecommendedYesAuto-completeFAST: All Facets (suggestall); AAT (possible expansion)Descriptions > SubjectOne search for all or dropdown with authority choices? Check with Anna for best implementation. Temporal and Spatial Coverage ("aboutness") should be cataloged here.
dcterms:source is already in use; figure out what it's doing then talk to CatDivisionchf:division or edm:currentLocation or dcterms:source pcdm:AdministrativeSet  DivisionRequired*NoDrop-down menuLocal Drop-down choices: The Museum at CHF, The Othmer Library of Chemical History, Archives?, Center for Oral History
new (split from above)Series Arrangementbf:materialHierarchicalLevel rdfs:Literalhttp://bibframe.org/vocab/materialHierarchicalLevel NoneOptional, Required for Archival materialsYesFree textNone Free text field for series/intellectual arrangement info.
changed this predicateContainer/Part Numberbf:materialOrganization rdfs:Literalhttp://bibframe.org/vocab/materialOrganization NoneOptional, Required for Archival and serialized materialsNoFour numeric free text fields?None Four numerical input fields for Box, Folder, Volume/Issue, and Part numbers.
 Related URL           Undecided if this field will auto-generate from bib numbers,
XRightsdc11:rights

rights, ::RDF::DC.rights, range: "dc:RightsStatement"

 http://purl.org/dc/elements/1.1/rights RightsRequired*NoDropdown menuCreative Commons, etc.Descriptions > Rights*DPLA, Europeana + others are working on an international standard for rights statements. Can keep an eye on progress here: https://docs.google.com/document/d/1x10JsIfi8Y74pgJJEAqMtyO5iYp0p6DO5DrOZK-5umY/edit#. Also keeping an eye on this: https://wiki.duraspace.org/display/hydra/Rights+Metadata+Recommendation. Hydra using edm:rights instead of DC.
XRights Holderchemheritage, moving to dcterms:rightsHolder none, moving to edm:Agenthttp://purl.org/dc/terms/rightsHolder NoneRequired, if availableNoTBDTBD TBD
 Credit Line     NoneOptionalYes    
XProvenancedcterms:provenance  http://purl.org/dc/terms/provenance NoneOptionalNoFree textNone Visible to staff only unless curators want info public?
 File Creator            

predicate needed

Admin Noteschf:adminNotes           
              
Fields we won't implement yet
Don't implement this yetPhysical LocationPhysical Location          I still think Physical Location details would be nice to have in Hydra, but for now manual entry wouldn't get updated effectively.
Look at how collections work by default. This is probably in there (see also part_of, in list below - same predicate)Collectiondcterms:isPartOf pcdm:Collection?http://purl.org/dc/terms/isPartOf CollectionRequired, if availableYesAuto-complete?Hydra collections controlled vocabulary?Collections > Descriptions > Title*Set reciprocal relationships with HasPart.
 Related Materialsdcterms:relation

 

pcdm:Object?http://purl.org/dc/terms/relation NoneOptionalYesAuto-complete?Hydra objects? Thought a bit more about this as curated "related materials," and I think a use case would be when there are multi-volume books that a cataloger wants to relate together. 
UnimplementAbstract (OH?)dcterms:abstract  http://purl.org/dc/terms/abstract OptionalNo?Free text with full HTML    
UnimplementTable of Contents (OH?)dcterms:tableOfContents  http://purl.org/dc/terms/tableOfContents No?List display?     
predicate neededRelated ExhibitRelated Exhibit           
              

Here is a list of other things in Sufia. we'll get these for free with default behavior: