Difference between revisions of "SANDBOX"
Jump to navigation
Jump to search
Andrea Zanni (talk | contribs) |
|||
Line 38: | Line 38: | ||
# EAGLE metadata schema (this is the proposed metadata schema agaist which to map all the content providers schemas) |
# EAGLE metadata schema (this is the proposed metadata schema agaist which to map all the content providers schemas) |
||
# EAGLE metadata comparison table (these are the proposed rules to map the content providers schemas into the EAGLE schema and the latter into EDM) |
# EAGLE metadata comparison table (these are the proposed rules to map the content providers schemas into the EAGLE schema and the latter into EDM) |
||
− | |||
− | == Types of descriptions == |
||
− | * https://docs.google.com/spreadsheet/ccc?key=0ArNdrqhsfCU-dEd6bDctV251OWhvdHhseHB2cDlVRUE#gid=1 |
||
− | |||
== Issues == |
== Issues == |
Latest revision as of 14:19, 28 August 2013
Epitafio de L. Iunius Avitus HE No. 155
CAN WE work on:
infobox type of template for new translations in which: opting out either for original or published (and consequent fields)
map the template to CIDOC CRM?
e.g.
- text = E31,
- Author = E21
and in the form put for example something like a property P14 where to imput the name?
- photoshop:Headline
- dc:title
- photoshop:DateCreated
- dc:creator
- daiImage:readable
- daiImage:responsibility
- daiImage:writable
- photoshop:City
- iptc4xmlCore:Location
- dc:type (evtl. + eigenes kontrolliertes Vokabular)
- dc:description
- daiImage:number
- dc:format (evtl. + eigenes kontrolliertes Vokabular)
Metadata schema
- EAGLE metadata schema (this is the proposed metadata schema agaist which to map all the content providers schemas)
- EAGLE metadata comparison table (these are the proposed rules to map the content providers schemas into the EAGLE schema and the latter into EDM)
Issues
- Stringa troppo corta (limite 400 caratteri).