Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Orlando: "While it would be good to have Large TIFF images on ResearchHub and have high derivatives copied to CDN, it's important to have very clear the issue about the cost implications as well as workflows implications.  I would really like to see a front-end DAM system using Amazon Web Services as the back-end."

Grace: "As Orlando advises, our current intention is to store high/full-resolution jpg derivatives on the CDN and allow drupal to create it's own derivatives for public consumption."

Q: What are you attaching image metadata to -- TIFFs, Jpegs, all of the above?

...

Michael: "To answer part of your question, for the art collection images we are using a Java script that Andrew wrote to embded metadata drawn from our filemaker database. The script writes to XMP fields in the Dublin Core namespace. If you need a specific list I can get you our mapping tomorrow, just let me know. This applies only to master TIFFs and those derivatives already created in-house and stored on Research Hub, and only to the art collection images."

Michael: "I added an excerpt from our metadata mapping as a comment on the wiki page. It shows the filemaker data that Andrew's program pulls as well as the XMP fields that it writes to the images. To clarify a bit, some of the tags include text prefixes that we use in Research Hub, especially in the DESCRIPTION tag, where we concatenate lots of data. Rick, last year we came up with new mappings to replace the ones that Rick Rinehart had developed. There's more here than RH can handle yet, so the data is richer...."