Metadata mapping and custom schema guide
•Als PPT, PDF herunterladen•
1 gefällt mir•4,025 views
The document discusses metadata schemas and workflows for cataloging digital assets. It provides examples of metadata schemas including Dublin Core and Photoshop XMP schemas. It also describes different organizations' processes for collecting metadata from faculty and students and integrating it into databases using tools like Photoshop and custom metadata panels. Custom metadata schemas are suggested to better fit specific needs rather than repackaging existing schemas.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ă„hnlich wie Metadata mapping and custom schema guide
Ă„hnlich wie Metadata mapping and custom schema guide (20)
Mehr von Visual Resources Association
Mehr von Visual Resources Association (20)
KĂĽrzlich hochgeladen
KĂĽrzlich hochgeladen (20)
Metadata mapping and custom schema guide
- 1. Â
- 2. Â
- 3. Â
- 4. Â
- 5. Â
- 6. Â
- 7. Â
- 8. Â
- 9. Â
- 11. Now What?
- 12. External
- 14. External
- 15. External
- 16. External
- 17. External Identify contents Identify source Express copyright Express use restrictions
- 18. External Established schemas Native input panels
- 19. Battles and Leaders of the Civil War Collection
- 20. download
- 21. Tool: Bridge CS4 download
- 22. UCSD Center for Music Experiment mp3s
- 23. Â
- 24. Â
- 25. Internal
- 29. Source & Workflow Administration UCSD PDF accession records
- 30. Tool: Acrobat Pro Source info
- 32. Tool: Photoshop CS3 Workflow
- 36. Student assistant Enters data in Photoshop/Bridge
- 37. VR curator Checks work in Excel Imports into database
- 39. Faculty member Creates images Enters data in Photoshop
- 40. VR Staff Researches work Enters data in custom panel
- 42. Tool: FileMind
- 43. Tool: FileMind
- 44. Making custom CS panels Repackage off-the-shelf schemas
- 45. Repackage off-the-shelf schemas Native XMP schemas Dublin Core Photoshop XMP Basic XMP Rights Making custom CS panels
- 46. Keywords dc:subject Description dc:description Date / Time Original photoshop:DateCreated Date / Time Digitized xmp:CreateDate Date / Time Modification xmp:ModifyDate Copyright dc:rights Creator dc:creator Location (Created) Iptc4xmpExt:LocationCreated:WorldRegion Iptc4xmpExt:LocationCreated:Country Iptc4xmpExt:LocationCreated:ProvinceState Iptc4xmpExt:LocationCreated:City Iptc4xmpExt:LocationCreated:Sublocation Location (Shown) photoshop:Country photoshop:State photoshop:City Iptc4xmpCore:Location Iptc4xmpExt:LocationShown:Country Iptc4xmpExt:LocationShown:ProvinceState Iptc4xmpExt:LocationShown:City
- 47. Keywords dc:subject Description dc:description Date / Time Original photoshop:DateCreated Date / Time Digitized xmp:CreateDate Date / Time Modification xmp:ModifyDate Copyright dc:rights Creator dc:creator Location (Created) Iptc4xmpExt:LocationCreated:WorldRegion Iptc4xmpExt:LocationCreated:Country Iptc4xmpExt:LocationCreated:ProvinceState Iptc4xmpExt:LocationCreated:City Iptc4xmpExt:LocationCreated:Sublocation Location (Shown) photoshop:Country photoshop:State photoshop:City Iptc4xmpCore:Location Iptc4xmpExt:LocationShown:Country Iptc4xmpExt:LocationShown:ProvinceState Iptc4xmpExt:LocationShown:City
- 48. Keywords dc:subject Description dc:description Date / Time Original photoshop:DateCreated Date / Time Digitized xmp:CreateDate Date / Time Modification xmp:ModifyDate Copyright dc:rights Creator dc:creator Location (Created) Iptc4xmpExt:LocationCreated:WorldRegion Iptc4xmpExt:LocationCreated:Country Iptc4xmpExt:LocationCreated:ProvinceState Iptc4xmpExt:LocationCreated:City Iptc4xmpExt:LocationCreated:Sublocation Location (Shown) photoshop:Country photoshop:State photoshop:City Iptc4xmpCore:Location Iptc4xmpExt:LocationShown:Country Iptc4xmpExt:LocationShown:ProvinceState Iptc4xmpExt:LocationShown:City
- 49. Keywords dc:subject Description dc:description Date / Time Original photoshop:DateCreated Date / Time Digitized xmp:CreateDate Date / Time Modification xmp:ModifyDate Copyright dc:rights Creator dc:creator Location (Created) Iptc4xmpExt:LocationCreated:WorldRegion Iptc4xmpExt:LocationCreated:Country Iptc4xmpExt:LocationCreated:ProvinceState Iptc4xmpExt:LocationCreated:City Iptc4xmpExt:LocationCreated:Sublocation Location (Shown) photoshop:Country photoshop:State photoshop:City Iptc4xmpCore:Location Iptc4xmpExt:LocationShown:Country Iptc4xmpExt:LocationShown:ProvinceState Iptc4xmpExt:LocationShown:City
- 50. Keywords dc:subject Description dc:description Date / Time Original photoshop:DateCreated Date / Time Digitized xmp:CreateDate Date / Time Modification xmp:ModifyDate Copyright dc:rights Creator dc:creator Location (Created) Iptc4xmpExt:LocationCreated:WorldRegion Iptc4xmpExt:LocationCreated:Country Iptc4xmpExt:LocationCreated:ProvinceState Iptc4xmpExt:LocationCreated:City Iptc4xmpExt:LocationCreated:Sublocation Location (Shown) photoshop:Country photoshop:State photoshop:City Iptc4xmpCore:Location Iptc4xmpExt:LocationShown:Country Iptc4xmpExt:LocationShown:ProvinceState Iptc4xmpExt:LocationShown:City
- 51. Making custom CS panels Repackage off-the-shelf schemas Understand the specifications
- 52. Making custom CS panels Repackage off-the-shelf schemas Understand the specifications Follow them
- 53. Making custom CS panels Repackage off-the-shelf schemas Understand the specifications Follow them Don’t force the fit - make your own schema
- 54. Making custom CS panels Repackage off-the-shelf schemas Understand the specifications Follow them Don’t force the fit - make your own schema Write a specification and publish it
- 55. Create your own schema Making custom CS panels
- 65. EMS Workflow tool Stand-alone tools Desktop Web
- 66. EMS Workflow tool Why Who What
- 67. EMS Workflow tool Why Who What collect user data
- 68. EMS Workflow tool Why Who What collect user data faculty, students
- 69. EMS Workflow tool Why Who What collect user data faculty, students field work class projects portfolios dissertations
- 70. EMS Workflow tool Why Who What track workflow
- 71. EMS Workflow tool Why Who What track workflow staff
- 72. EMS Workflow tool Why Who What track workflow staff production tracking backlog processing pre-cataloging
- 73. EMS Workflow tool Why Who What collaborate
- 74. EMS Workflow tool Why Who What collaborate staff and users
- 75. EMS Workflow tool Why Who What collaborate staff and users shared cataloging consultation tagging
- 79. Â
- 80. Â
- 81. Â
- 82. Â
- 85. Â
Hinweis der Redaktion
- An early technical drawing
- Large Hadron Collider, Geneva, Switzerland
- The basics have been covered
- External metadata - If you are releasing your images in the wild
- Internal, metadata - If you are only using embedded metadata as a means to an end – the end being a central database.
- It’s all about your users. Metadata for the masses. Your audience could be anybody. You can’t pick them out of the crowd. http://www.flickr.com/photos/usnationalarchives/4185020633/
- The embedded metadata should be readable across platforms…
- … and across applications and services
- Highest priorities: identify contents and express rights to anyone who views the image
- How is this done? Read by common tools - Established schemas – EXIF, IPTC International Press Telecommunications Council Built-in panels – most likely to be interoperable, no add-ons, plugins or special panels
- Example: Allan Kohl’s Battles and Leaders of the Civil War
- When? Perhaps at the end of the process – at the time of public release or download. UCSD plans to embed cataloging data in mp3 files so the data will display on media players. This is standard for music files, why not for image files?
- It’s all about you and your institution.
- Internal processes – administrative Intermediary data - might be deleted after it has been extracted Can be geeky – would anyone else care about it?
- Custom schema – made to match your local database Custom panel – made for your needs Not easily found – wont help identify your images
- Words of caution: If you leave internal data in the files, consider that: It can be read with right software - Don't include any secrets – consider it public Transform before making it public – use IPTC to make it readable with common tools
- UCSD accession records
- Staff use custom CS3 XMP panel
- Staff use custom CS3 XMP panel
- Staff use custom CS3 XMP panel
- Staff use custom CS3 XMP panel
- Using Bridge, staff can search the any field of the embedded data. All orders not shot, not QCed, not cataloged, by a certain staff member. When orders are complete, the data could be imported to a central database.
- California Polytechnic State University, San Luis Obispo Why? Students don’t have access to central database
- Student assistant: -Uses custom XMP panels, can work on multiple images or use a template to save time --VRC Work --VRA Image
- VR Curator: -Exports data with custom Photoshop script. -Checks work in Excel -Imports to Embark database.
- Library wants resource data and requires Dublin Core Terms VR collection wants work data and would prefer to use VRA Core
- VR cataloging data see with FileMind
- Kid in a candy store.
- Easiest way to do this is to use Photoshop and XMP. Adobe has built several schemas into XMP. If you can find the elements you need here, your work will be easier
- Repackage off-the-shelf schemas Metadata Working Group – not a schema but a reccomendation
- Dublin Core
- Photoshop schema
- XMP properties schema
- IPTC Extension
- If you can find the elements you need here, your work will be easier
- If you can find the elements you need here, your work will be easier
- If you can find the elements you need here, your work will be easier
- If you can find the elements you need here, your work will be easier
- must obey the rules for XML 1.0 namespaces might or might not actually locate a resource such as a web page.
- must obey the rules for XML 1.0 namespaces might or might not actually locate a resource such as a web page.
- must obey the rules for XML 1.0 namespaces might or might not actually locate a resource such as a web page.
- must obey the rules for XML 1.0 namespaces might or might not actually locate a resource such as a web page.
- must obey the rules for XML 1.0 namespaces might or might not actually locate a resource such as a web page.
- Should be unique
- Should be unique
- Specifications – Application Profile
- What the EMS has been working on
- We’re going shopping for elements in IPTC and PLUS If we can’t find what we need, we will create a custom Core 4 schema.
- The basics have been covered
- Get cooking