|Line 1:||Line 1:|
Revision as of 08:33, 25 June 2009
Often tiff/wave files do note have a one to one match with transcript files or vice-versa.
Below are three scenarios and the naming rules devised on 6/19/09 to allow the file names themselves to denote a correlation between different file types that point to the same information (i.e. an audio interview and a transcript of that interview).
Situation 1: One to Many (One media file to many text files)
ex: 1 .wav file and 3 .txt transcript files
Situation 2: Many to One (Many media files to one text file)
ex: 3 .wav files and 1 .txt transcript file
Situation 3: One to One (One media file to one text file)
ex: 1 .wav file and 1 .txt transcript file
- What if you have 2 .wav files and 3 pages of transcripts? That is, what happens when a transcript page contains the transcription for part of each of the 2 .wav files?
In that case you might have a scenario like this: _0001.wav goes with _0001_001.txt and _0001_002.txt while _0002.wav goes with _0002_001.txt and _0001_002.txt. In this case, _0001_002.txt and _0002_001.txt are the SAME document, simply existing twice with different file names. This still allows people to know what transcripts correspond to what media items based simply on the file name.
We understand that this calls for more storage space to be used (given that an analog item exists as two distinct files), but the greater concern is the removal of confusion regarding relation of items to one another.
- What about a scenario in which there are 2 tiffs (of original analog materials) and 1 transcript file (in tiff format) which contains the transcription for both original tiffs? How will someone know what part of the transcription tiff matches with the respective portion of the scans of the analog materials?
They won't know exactly, but they'll be in the right ballpark, and will only have to peruse one transcript page to find the information that corresponds to each scan of the analog materials. Perhaps, in the future we can incorporate X/Y axes of the transcription files in the metadata.