Media Handling Inquiries for Release 1.6

Overview of requirements

The management of digital objects and the management of media that support object, procedural, and organizational records in the system. The system should:

  • Allow users to create media support records with distinct technical, administrative, and descriptive metadata
  • Allow users to relate media support records to procedural records (e.g. intake, cataloging, or loan), object records, and organizational records (e.g. authorities and storage locations).
  • Allow users to create media support records from a variety of file types, including image (e.g. jpg and tiff), video (e.g. avi and mov), audio (e.g. wav and mp3), documents (e.g. doc and pdf), etc.
  • Allow users to relate the same media support record to more than one procedural, object, or organizational record.
  • Allow users to view, search, and report on media support records

Questions

  1. Describe the current use of media within your system.
  2. Is media stored within your CMS, or do you link to an outside repository/DAMS?
  3. Walk me through uploading or linking to a media asset in your current CMS
  4. What are your derivative requirements? (E.g. web-sized, preview, thumbnail, etc.)
  5. What media formats / file formats do you need to support?
  6. Do you currently use batch upload or image processing?
  7. How do you relate media assets to records? Can a record have more than one media asset? Can a media asset relate to more than one record?
  8. Do you currently use a DAMS? How, if at all, does it interact with your CMS?
  9. How do you search for media assets?
  10. What metadata do you wish to acquire from the asset on upload or link, e.g. file size, file format, etc.?
  11. Are there current media-related processes and workflows that just don’t work, or seem time consuming/confusing?
  12. What are the strengths of your current system? Where are your pain points?
  13. Can you send some screenshots of your interface?

SMK notes

   1. Describe the current use of media within your system.

a. All kind of documents/all formats can be related to a works of art. (.doc, .pdf, .tiff, .jpeg, .bmp, x-ray, IR, moving images, audio)

b. One picture in .jpeg format is uploaded from the system PhotoStation Pro and related to each works of art.

   2. Is media stored within your CMS, or do you link to an outside repository/DAMS?

a. Some documents in different formats is stored within our current system, same as a) above.

b. In the system PhotoStation Pro (index server) all pictures are stored.

   3. Walk me through uploading or linking to a media asset in your current CMS
a. word document with 2 screen shots
b. IT manager upload from PhotoStation Pro= makes a path from the system to PhotoStation Pro.

   4. What are your derivative requirements? (E.g. web-sized, preview, thumbnail, etc.)
"Nice to have" a picture scaled based upon some selected related collection object dimensions, so that a collection of images could be produced that are scaled correctly relative to their actual size (and thereby each other).
Users need not to know how to map i.e. know where the files is stored.

   5. What media formats / file formats do you need to support?
doc, tiff, pdf, jpg, .gif, png, bmp, jpeg + wmf, avi, mpeg4, mov, 3gp, swf og flv

   6. Do you currently use batch upload or image processing?
like 3 b

   7. How do you relate media assets to records? Can a record have more than one media asset? Can a media asset relate to more than one record?
Inventory number and tag

   8. Do you currently use a DAMS? How, if at all, does it interact with your CMS?
We have no DAMS, in the future we will try to get one.

   9. How do you search for media assets?
Search the work of art (number, artist name, title, ...)

   10. What metadata do you wish to acquire from the asset on upload or link, e.g. file size, file format, etc.?
Number and link to where it is stored. Metadata in the DAM system

   11. Are there current media-related processes and work flows that just don’t work, or seem time consuming/confusing?
Problems with right viewers for different formats
We upload manual, should be automatically
If numbers is incorrect the relations is incorrect (fail message)
Not always the newest picture (need version control)

   12. What are the strengths of your current system? Where are your pain points?
Too expensive
Not access for all (we want an imagebank = DAMS)

   13. Can you send some screen-shots of your interface?
Word document