Create new element for instantiationDescription with start and end times or similar

[kvanmalssen]

This may be a slightly radical idea, but I have a real world problem and no way (that I can see) to solve at the moment using PBCore:

We have timestamped transcripts for about 4000 oral histories (which range from an hour to several days in length). The issue is that the transcripts refer to time references for different instantiations for different oral histories. For example in one case the transcript times reference a VHS access copy, but for another it references the Betacam master. The duration and time starts on these are not identical, so the time references may be off by several seconds or even several minutes.

We are now digitizing these assets, with the goal of making the transcripts searchable in order to take users to a specific segment of an oral history. The problem is, the time references are all over the place and it will take intensive manual labor in order to reconcile the transcripts to the time references in the digital files.

What this scenario raises for me is that time referenced descriptions, even though they are descriptive information associated with the content, are really instantiation specific. The same could be said about any other type of start and end time references -- the start and end time of which instantiation?

I see two possible solutions to this:

1. Create a repeatable instantiationDescription element with @startTime and @endTime attributes.
2. Create an instantiationDescription container element, and recommend a markup format for the descriptions, such as Web VTT or similar.

If anyone has an idea that would use the current structure of PBCore, that would be great (maybe it's just: use extensions!), but from my review, pbcoreDescription with start and end time attributes doesn't satisfy this use case.

[awead]

I had thought this was what pbcorePart could be used for, but this won't do it. Perhaps instantiationPart with similar properties as pbcorePart ? @startTime and @endTimeare already there, but we could add additional subelements. It could also force us to deal with #64 as well.

[AllisonAnn]

When I was developing the WPR/WPT database (using pbcore as the model/basis), I had additional fields at the Instantiation level for title and description. I found both of these elements useful at the instantiation level for a number of reasons. So, I have no problem with including an instantiationDescription field. In fact, I'd recommend we also create an instantiationTitle field.

I would prefer that we start to use containers/nested elements more throughout pbcore, so that note fields can be more easily associated with specific elements. I think that many people have been using the @annotation attribute for notes about the asset, instead of notes about the element, and maybe we need to think about this dual use, and how it muddies the water. Having a nested note sibling element available to most/all pbcore elements could be useful to people, and help save the @annotation attribute for element description/use purposes.

[kvanmalssen]

I would also be in favor of an instantiationTitle field. That way people could put information on the tape label.