...
Lee experimented with creating segment-level indexes for this single transcript at two different levels of OHMS indexing (see OHMS Indexing Levels).The first segment is indexed at Level 3; subsequent segments just have the segment title and synopsis (copied from the transcript’s table of contents), along with a partial transcript. This puts them a bit ahead of level 1, but for level 2 they would need some keywords. Next steps will include adding keywords to these segments and trying to index and edit a longer interview.
...
Title (required by OHMS)
Media Format (required by OHMS)
Accession number (use OH/RI number; decide on format)
Series ID and Name (use to categorize interviews by Project; useful on OHMS backend for workflow management; front-end can link to COH website project info)
User Notes: “can be used for notes that an institution wants communicated to the public user each time the viewer is opened. The message can be closed by clicking on the X in the right corner. The User Note will reappear each time the public user switches between the transcript and the index.” (use to help clear up possible confusion about edited transcript vs. unedited audio / multi files vs. single file / how to cite?)
Acknowledgement (could use language from project/sponsor acknowledgement page)
Possibility for batch import? See OHMS_Import_Template
For help thinking this through, see: OHMS Metadata Fields
Final decision to be made in consultation with DigColl staff.
...
What level of depth do we want to go into? See OHMS Indexing Levels
Whatever level of indexing depth we choose, this is the work- and time-intensive part of the process for COH staff.
Indexing at least to level 2 is recommended if we want to justify no longer creating back-of-the-book indexes on the basis of the discoverability/searchability boost we’re getting from implementing OHMS.
Existing table of contents gives us starting point for Title and either Keywords or Synopsis fields (both?). Simple cut-and-paste plus transcript/audio navigation to tag segment beginnings gets us to level 1 at a pretty low effort.
Level 2 adds partial transcript (low effort), either keywords (low to medium effort) or subjects (high effort) in addition to synopsis. Segment breaks at 4-6 minute intervals—probably corresponds roughly to our existing tables of contents, but may be a little more frequent. If we eschew subject headings entirely, we can pretty easily handle level 2 indexing. In 2/18 DigColl Tech check-in all parties agreed that forgoing segment-level subheadings makes sense for the foreseeable future.
Level 3 calls for a more detailed synopsis, both keywords and subjects, and the inclusion of external hyperlinks and GPS coordinates when appropriate. Segment breaks roughly every 3-6 minutes. Level 3 is aspirational at this point. We might try it out for particularly popular/interesting interviews.
...
Multipart audio files
Edited/published version of the transcript PDF, corresponding to multipart audio files but also possibly deviating from the audio considerably
Single, stitched together audio file
Transcript corresponding (both in time coding and in substance) to single, stitched together audio. This can be autogenerated as a PDF file via the OHMS viewer (including in preview mode). See Interview-export1581704695.pdf How customizable is this feature?
The developers want to create a customized viewer for deployment on the DigColl app, rather than relying on the default OHMS viewer. If we insist on the need for the viewer to include this PDF generator feature it’s more than likely that they’ll abandon plans for a custom viewer and use the standard one instead. However, we could generate the PDF using the OHMS preview feature from the backend and then manually upload that transcript to the Digital Collection ourselves as another derivative product that we make available.
Decision to be made primarily by development team, in consultation with COH.
| View file | ||
|---|---|---|
|
How do we help future patrons figure out how to use/cite the different derivative products of each interview?
...