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
- Describe the current use of media within your system.
- Is media stored within your CMS, or do you link to an outside repository/DAMS?
- Walk me through uploading or linking to a media asset in your current CMS
- What are your derivative requirements? (E.g. web-sized, preview, thumbnail, etc.)
- What media formats / file formats do you need to support?
- Do you currently use batch upload or image processing?
- 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?
- Do you currently use a DAMS? How, if at all, does it interact with your CMS?
- How do you search for media assets?
- What metadata do you wish to acquire from the asset on upload or link, e.g. file size, file format, etc.?
- Are there current media-related processes and workflows that just don't work, or seem time consuming/confusing?
- What are the strengths of your current system? Where are your pain points?
- Can you send some screenshots of your interface?
SMK notes
1. Describe the current use of media within your system.
...