Multi Med03 Ja


Published on

Published in: Technology, Art & Photos
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Multi Med03 Ja

  1. 1. York Digital Library – Images Case Study Julie Allinson, SUETr Multimedia Deposits Event 30 th March 2009
  2. 2. Overview <ul><li>A walk-through of what we did at York, </li></ul><ul><li>bearing in mind </li></ul><ul><ul><li>starting from scratch </li></ul></ul><ul><ul><li>we use ‘F’-for-flexible Fedora </li></ul></ul><ul><ul><li>and Mura front-end </li></ul></ul><ul><ul><li>short-term needs and long-term plans </li></ul></ul><ul><ul><li>not just an image library </li></ul></ul>
  3. 3. Approach <ul><li>Image Content Model </li></ul><ul><ul><li>a statement of requirements </li></ul></ul><ul><ul><li>a record of decisions </li></ul></ul><ul><ul><li>a design blueprint </li></ul></ul><ul><ul><li>[not yet] a machine-readable ‘content model’ </li></ul></ul><ul><ul><li>re-usable </li></ul></ul><ul><ul><li>possibly of wider use? </li></ul></ul><ul><li> </li></ul>
  4. 4. Considerations <ul><li>Use case(s) </li></ul><ul><li>Image types </li></ul><ul><li>Uniqueness (preservation/access) </li></ul><ul><li>Metadata for intended and potential usage </li></ul><ul><li>File formats, sizes, expected delivery mechanism </li></ul><ul><li>Access Restrictions </li></ul><ul><li>Deposit Workflow </li></ul><ul><li>Rights </li></ul>
  5. 5. Use Case(s) <ul><li>The University of York History of Art Department need digital images for teaching and research. They have no networked way of sharing image resources. They use a lot of scanned images under CLA, which need access control. They also sometimes take images and in the past got slides made of these. </li></ul>
  6. 6. But, other types of image too … <ul><li>Works of art </li></ul><ul><li>Architecture or architectural features </li></ul><ul><li>Archaeological sites, objects </li></ul><ul><li>Archival materials </li></ul><ul><li>Computer-generated images </li></ul><ul><li>Photographs taken for specific purposes </li></ul>
  7. 7. Metadata <ul><li>Requirements </li></ul><ul><li>Model </li></ul><ul><ul><li>based on VRA – image & work distinction </li></ul></ul><ul><li>Profile </li></ul><ul><ul><li>of VRA, minimal extensions </li></ul></ul><ul><li>Vocabularies </li></ul><ul><li>IDs and Labels </li></ul><ul><li>Mapping to DC </li></ul>
  8. 8. Datastreams/files <ul><li>Image formats </li></ul><ul><ul><li>accept all </li></ul></ul><ul><ul><li>Preferred: open formats </li></ul></ul><ul><ul><li>Convert to: JPEG/TIFF for delivery </li></ul></ul><ul><li>Images ‘expressions’ stored </li></ul><ul><ul><li>ARCHIVAL_IMAGE; FULL_IMAGE; PREVIEW_IMAGE; THUMBNAIL </li></ul></ul><ul><li>File sizes and resolutions </li></ul><ul><ul><li>maintain original size/resolution - guidelines available [soon] </li></ul></ul>
  9. 9. Relationships <ul><li>Important in Fedora – RELS-EXT </li></ul><ul><li>Currently stores collection membership </li></ul><ul><li>Can be exploited further, e.g. to store relationships between different objects, formal content model </li></ul><ul><li>Exploring RELS-INT for internal relationships </li></ul>
  10. 10. Workflow <ul><li>Specification of the deposit process </li></ul><ul><li>Currently fairly simple </li></ul><ul><li>Uses </li></ul><ul><ul><li>mapped drives (local deposit) </li></ul></ul><ul><ul><li>muradora </li></ul></ul><ul><ul><li>xforms </li></ul></ul><ul><li>Has user-facing and technical aspect </li></ul><ul><li>Review and publish stage </li></ul>
  11. 11. Workflow – human <ul><li>Select object type </li></ul><ul><li>Select collection </li></ul><ul><li>Drop + select file </li></ul><ul><li>Describe </li></ul><ul><li>Save </li></ul><ul><li>Review – record + data dictionary </li></ul><ul><li>Publish </li></ul>
  12. 12. Access Control <ul><li>Requirements for access control </li></ul><ul><li>Two main current use cases </li></ul><ul><ul><li>Restricted CLA </li></ul></ul><ul><ul><li>Restricted public </li></ul></ul><ul><li>This needs </li></ul><ul><ul><li>Integration with LDAP/Shibboleth </li></ul></ul><ul><ul><li>Access control filter to ‘talk’ to different systems </li></ul></ul><ul><ul><li>Roles and role mapping </li></ul></ul><ul><ul><li>RELS-INT datastream </li></ul></ul>
  13. 13. Rights <ul><li>Copyright clearance info built into VRA </li></ul><ul><li>Standard rights statements – CLA & Creative Commons built into VRA </li></ul><ul><li>Image license for accepting collections </li></ul><ul><li>Uses Creative Commons </li></ul>
  14. 14. It’s all a work in progress <ul><li>To-do </li></ul><ul><ul><li>JHOVE for technical metadata </li></ul></ul><ul><ul><li>Refining/extending workflow </li></ul></ul><ul><ul><li>Access control </li></ul></ul><ul><ul><li>Different types of images </li></ul></ul><ul><ul><li>etc. etc. </li></ul></ul>
  15. 15. Usefulness of ‘Content Model’ <ul><li>‘ checklist’ </li></ul><ul><li>m ight be too internal to be of wider use </li></ul><ul><li>w hether documented or not, each aspect of the process has be thought through (with Fedora anyhow) </li></ul><ul><li>a document helps demonstrate all the work involved </li></ul><ul><li>n eeds regular review to keep up-to-date </li></ul>
  16. 16. Experience with images <ul><li>Good starting point </li></ul><ul><ul><li>one dimensional </li></ul></ul><ul><ul><li>lots of work/advice </li></ul></ul><ul><ul><li>tools and code available </li></ul></ul><ul><ul><li>lots of content available </li></ul></ul><ul><ul><li>relatively small file sizes </li></ul></ul><ul><ul><li>easy to demonstrate </li></ul></ul>
  17. 17. That’s it <ul><li>contact [email_address] </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.