ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
VRA FIELDVRA Core elementIMAGES RequiredIMAGES FacetIMAGES OBLIGATIONCONTROLLED VOCABULARYNotes for ImagesHYRAX PCDM MODELHYRAX FIELDHYRAX PredicateHYRAX REQUIREDHYRAX EXPECTED VALUEHYRAX OBLIGATIONHYRAX FACETHYRAX INDEXHYRAX SHORT DISPLAYHYRAX NOTESNEXT GEN PCDM MODELNEXT GEN FIELDNEXT GEN PREDICATENEXT GEN REQUIREDNEXT GEN EXPECTED VALUENEXT GEN OBLIGATIONNEXT GEN FACETNEXT GEN INDEXNEXT GEN SHORT DISPLAYNEXT GEN VOCABNEXT GEN NOTES
2
TITLEvra:titleSet/vra:title[@pref="true"]MUSTNo{1,n}works:Work < pcdm:Object - DescriptiveTITLEdcterms:titleMUSTxsd:string{1}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectTITLEdcterms:titleMUSTxsd:string{1}NoYesYesNONE
3
ALTERNATE TITLEvra:titleSet/vra:title[@pref="false"]MAYNo{0,n}ALTERNATE TITLEdcterms:alternativeMAYxsd:string{0,n}NoYesNoNONE
4
RELATIONvra:relationSet/vra:relation[@pref="true" @type="imageOf" @relids={$PID}]MUSTNo{1}System-supplied on creation. If title is later edited, this has to be edited as well. Meant to tie "Works" together in VRAworks:Work < pcdm:ObjectNONENONEshould be for the pcdm:Object works:Work
5
CREATORvra:agentSet/vra:agent/vra:name[@type=" " @vocab=" " @refid " "]MUSTYes{1,n}ULAN, LCNAFtype=personal, corporate, family, otherworks:Work < pcdm:Object - DescriptiveCREATORdc:creatorSHOULDxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCREATORdc:creatorSHOULDxsd:string{0,n}YesYesYesULAN, LCNAF, VIAFPropose we no longer REQUIRE a CREATOR // VOCAB=ULAN,LCNAF, ideally URIs
6
CREATOR ROLEvra:agentSet/vra:agent/vra:name/vra:role[@vocab="RDA"]MAY{0,n}RDAworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCREATOR ROLEbf:roleMAYxsd:anyURI{0,n}YesYesNoMARC RELATORWill want to convert the RDA terms to MARC Relators which have URIs
7
CREATOR ATTRIBUTIONvra:agentSet/vra:agent/vra:name/vra:attributionMAY{0,n}works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCREATOR ATTRIBUTIONMAYxsd:string{0,n}YesYesNoNONEVRA RDF doesn't even bother with these. Maybe we just keep them as part of the name
8
DATE DISPLAYvra:dateSet/vra:displayMUSTYes{1,n}DATEbf:dateMAYxsd:string{0,n}NOYesNoNONEdo we convert these to edtf ranges? // have a LOT of date earliest/latest which are 0000/2012 // should these go into a dates type note instead of the display
9
DATE EARLIESTvra:dateSet/vra:date/vra:type=" "/vra:earliestDateMUSTNo{1,n}follows ISO 8601
https://www.cl.cam.ac.uk/~mgk25/iso-time.html
works:Work < pcdm:Object - DescriptiveDATE CREATEDdcterms:createdSHOULDxsd:date or xsd:dateTime{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectDATEdc:dateMUSTxsd:date{1,n}YesYesYesEDTF
should follow edtf // dc:date allows for a range of dates
10
DATE LATESTvra:dateSet/vra:date/vra:type=" "/vra:latestDateMAYNo{0,n}follows ISO 8601works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectDATEdc:dateMAYxsd:date{0,n}YesYesYesEDTFshould follow edtf
11
STYLE PERIODvra:stylePeriodSet/vr:stylePeriod[@vocab="" @refid=" "]MAYYes{0,n}AATSTYLE PERIODworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectSTYLE PERIODvra:stylePeriodMAYxsd:anyURI{0,n}YesYesNoAAT
12
TECHNIQUEvra:techniqueSet/vra:technique[@vocab="AAT" @refid=" "]MAYYes{0,n}AATworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectTECHNIQUEvra:techniqueMAYxsd:anyURI{0,n}YesYesNoAAT
13
MATERIALvra:materialSet/vra:material MAYNo{0,n}works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectPHYSICAL DESCRIPTIONbf:extentMAYxsd:string{0,n}NoYesNoAAT, RDA/MARC 33X fields
14
MEASUREMENTSvra:measurementsSet/vra:measurementsMAYNo{0,n}works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectPHYSICAL DESCRIPTIONbf:extentMAYxsd:string{0,n}NoYesNoNONE
15
SUBJECT DISPLAYvra:subjectSet/vra:display MAYNo{0,n}These are the strings in the record displayworks:Work < pcdm:Object - DescriptiveSUBJECTdc:subjectMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectSUBJECTdc:subjectMAYxsd:string{0,n}YesYesNoAAT, LCSH, LCNAF, ULAN, FAST Larger discussion needed on subject facets vs. subject strings. Also, don't currently divide our subjects into spatial, topical, and geographic. Subject strings historically not accurate. Would need a lot of cleanup to use dcterms:subject and have URIs- this can happen using OpenRefine but then how to get those corrections back into the repo is another issue // map facets and display to dc:subject // this will lead to duplication of subjects but can be reconciled and cleaned up as part of migration
16
SUBJECT FACETvra:subjectSet/vra:subject/vra:term[@type=" " vocab=" " refid=" "]MAYYes{0,n}FAST,LCSH,AATThese populate the facet. Types most used: personalName, corporateName, descriptiveTopic, otherTopic, georgraphicPlace, otherPlaceNONEdc:subjectAAT, LCSH, LCNAF, ULAN, FAST
17
DESCRIPTIONvra:descriptionSet/vra:descriptionMAYNo{0,n}Always has Job numberworks:Work < pcdm:Object - DescriptiveDESCRIPTIONdc:descriptionMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectDESCRIPTIONdc:descriptionMAYxsd:string{0,n}NoYesNoNONE
18
INSCRIPTIONvra:inscriptionSet/vra:inscription/vra:textMAYNo{0,n}used more like a captionworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCAPTIONschema:captionMAYxsd:string{0,n}NoYesNoNONEThe inscription usage is as captions.
19
LOCATION CALL NUMBERvra:locationSet/vra:location[@type="site"]/vra:name[@type"other"="Call number:"]MAYNo{0,n}Used for Call number in ALMAworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCALL NUMBERbf:shelfMarkMAYxsd:string{0,n}NoYesNoNONE
would come through as part of bib import going forward
20
LOCATION ACCESSION NUMBERvra:locationSet/vra:location/vra:refid[@source="Accession"]MUSTNo{1}
System-supplied on creation - taken from filename
works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectACCESSION NUMBERloc:localMUSTxsd:string{1}NoYesNoNONE
21
LOCATION VOYAGER NUMBERvra:locationSet/vra:location/vra:refid[@source="Voyager"] MUSTNo{1}Used for Voyager bib number from ArtDB Voyager. NO LONGER CREATEDworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectACCESSION NUMBERloc:localMUSTxsd:string{1}NoYesNoNONE
22
LOCATION ALMA BIB NUMBERvra:locationSet/vra:location/vra:refid[@source="other"]MAYNo{0,n}Used for ALMA bib numberworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCATALOG KEYowl:sameAsMAYxsd:anyURI{0,n}NoYesNoNONE
23
LOCATION OF REPOSITORYvra:locationSet/vra:location[@type='repository']/vra:name[@type='geographic']SHOULDNo{0,n}Location of repositoryworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectPROVENANCEdcterms:provenanceSHOULDxsd:string{0,n}NoYesNoTBDI need to think more about this and LOCATION NAME OF REPOSITORY. We treat NUL and its collections as repositories. Also note the physical locations in the pictures. Sometimes also museum information - can be historical. NUL items we would want at the Collection Level and then this would be for the physical locations
24
LOCATION NAME OF REPOSITORYvra:locationSet/vra:location[@type='repository']/vra:name[@type='corporate']SHOULDNo{0,n}Name of repositoryworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectPROVENANCEdcterms:provenanceSHOULDxsd:string{0,n}NoYesNoTBD
25
LOCATION COLLECTION NAMEvra:locationSet/vra:location[@type='repository']/vra:name[@type='other']SHOULDNo{0,n}Used for Collection Name when neededpcdm:CollectonCOLLECTIONdcterms:titleMUSTxsd:string{1}YesYesNoNONEShould be part of Collection/Admin Set and display as part of descriptive display
26
SOURCEvra:sourceSet/vra:source/vra:nameMAYNo{0,n}Physical work piece was digitized from (a serial, book, etc.)SOURCEdcterms:sourceworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectSOURCEdcterms:sourceMAYxsd:string{0,n}NoYesNoNONENeeds definition from HYRAX on use. Assuming this is for a physical source from which the object came // also used for bib import info? // keep mapping as is. need to see it in action in a hyax environment
27
RIGHTS TYPEvra:rightsSet/vra:rights[@type=" "]SHOULDNo{0,n}type=copyrighted, publicDomain, undetermined, otherworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectNONENONETBDNot using ; redundant ; this might be redundant or would we want to use the buttons http://rightsstatements.org/en/documentation/assets.html
28
RIGHTS HOLDERvra:rightsSet/vra:rights/vra:rightsHolderMAYNo{0,n}works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectRIGHTS HOLDERdcterms:rightsHolderMAYxsd:string{0,n}NoYesNoTBDprefer to use URIs but needs investigation
29
RIGHTS ACCESS STATEMENTvra:rightsSet/vra:rights/vra:textSHOULDNo{0,n}Used for Access statementworks:Work < pcdm:Object - DescriptiveLICENSEdcterms:rightsMAYdcterms:RightSatement (xsd:string?){0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectACCESS/USE STATEMENT/LICENSEdc:accessRightsSHOULDxsd:string{0,n}NoYesNoTBDother option dc:license or maybe both?
30
RIGHTS RIGHTSSTATEMENT.ORGvra:rightsSet/vra:rights/vra:text href="{rightsstatement.org}"SHOULDNo{0,n}
rightstatements.org
Used for Copyright link to rightsstatements.org determinationworks:Work < pcdm:Object - DescriptiveRIGHTSedm:rightsMAYdcterms:RightSatement (xsd:string?){0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectRIGHTS STATEMENTedm:rightsSHOULD
URI from Rightsstatements.org
{0,n}YesYesNorightstatement.orgAlso will have Rights at the Collection level which might not apply to every object in a collection
31
WORKTYPEvra:worktypeSet/vra:worktype[@vocab=" " @refid=" "]SHOULDYes{1}AATworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectGENREedm:hasTypeSHOULDxsd:anyURI{0,n}YesYesNoAAT
32
TEXTREFvra:textrefSet/vra:textrefMAYNo{0,n}NEEDS INVESTIGATION _ HAS THIS BEEN USED IN IMAGES? Contains the name of a related textual reference and any type of unique identifier that text assigns to a Work or Collection that is independent of any repository. Examples: catalog raisonnés, Beazley numbersworks:Work < pcdm:Object - DescriptiveCITATION
dcterms:bibliographicCItation
MAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCITATION
dcterms:bibliographicCitation
MAYxsd:string{0,n}NoYesNoNONE
33
IDENTIFIERvra:locationSet/vra:location/vra:refid[@source='DIL']MUSTNo{1}System-supplied on creationworks:Work < pcdm:Object - DescriptiveIDENTIFIERdcterms:identifierMAYxsd:stringYesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectIDENTIFIERdcterms:identifierMUSTxsd:string{1}NoYesNoNONEold PIDS = mapping to prov:DerivedFrom
34
CULTURAL CONTEXTNOT USED IN IMAGES{0,n}NONENONE
35
EDITIONNOT USED IN IMAGESNONENONE
36
works:Work < pcdm:Object - DescriptiveBASED NEARfoaf:basedNearMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectBASED NEARfoaf:basedNearMAYxsd:string{0,n}NoYesNoTBDneed more info from HYRAX as to what this is supposed to represent. Actual geographical information?
37
works:Work < pcdm:Object - DescriptiveCONTRIBUTORdc:contributorMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCONTRIBUTORdc:contributorMAYxsd:string{0,n}YesYesNoLCNAF, ULAN
38
works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectCONTRIBUTOR ROLEbf:roleMAYxsd:anyURI{0,n}YesYesNoMARC RELATORWill want to convert the RDA terms to MARC Relators which have URIs
39
works:Work < pcdm:Object - DescriptiveKEYWORDdc:relationMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectKEYWORDschema:keywordsMAYxsd:string{0,n}NoYesNoNONEthis really really really shouldn't be the HYRAX mapping of dc:relation. Not sure we need the field at all even. // being worked on as part of larger hyrax work
40
works:Work < pcdm:Object - DescriptiveLANGUAGEdc:languageMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectLANGUAGEdcterms:languageMAYxsd:anyURI{0,n}YesYesNoMARC LANGUAGE
41
works:Work < pcdm:Object - DescriptivePUBLISHERdc:publisherMAYxsd:string{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectPUBLISHERdc:publisherMAYxsd:string{0,n}NoYesNoNONE
42
works:Work < pcdm:Object - DescriptiveRELATED URLrdfs:seeAlsoMAYxsd:string OR xsd:anyURI{0,n}Yesworks:Work < pcdm:Object ; works:FileSet < pcdm:ObjectRELATED URLrdfs:seeAlsoMAYxsd:anyURI{0,n}NoYesNoNONERequired with Related URL LABEL
43
works:Work < pcdm:Object ; works:FileSet < pcdm:ObjectRELATED URL LABELrdfs:labelMAYxsd:string{0,n}NoYesNoNONERequired with Related URL
44
ABSTRACTdcterms:abstractMAYxsd:string{0,n}NoYesNoNONE
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100