EVIADA: Hierarchical display for <spans> in structure.xml that contain <spans>

[elynema]

Description

For the purposes of EVIADA, we need to be able to provide links in the structured navigation portion of a record that can link within this hierarchy:

• event
  -- scene
  --- action

In this scenario, the timespan for the event completely encompasses the timespans for the scene and action.

I am unable to create these hierarchical spans in the way that would make since in XML using the Advanced Edit for structure; I get an error for having content with a <Span>.

I can create a flat list of spans, some of which have time boundaries that overlap or are within the time boundaries of other spans, but it just produces a flat list in the structure, which does not convey important hierarchy.

I can add a <Div> element to the structure XML to enable the timespans to be indented underneath the <scene> that contains them, but that introduces unnecessary and confusing elements into the structure

Example record being used for testing in avalon-dev: https://avalon-dev.dlib.indiana.edu/media_objects/12579s29x

Done Looks Like

• Consulted with Product Owner / Music staff to determine if it is ok to loosen restrictions against timespans overlapping in the structure
• In the Advanced Edit feature for structure, a <Span> can contain other <Div> or <Span> elements
• Avalon produces Ranges in the IIIF manifest structure that represent this hierarchy
• All of these <Span> elements should be clickable within the Ramp structure
• Determine whether any changes will be made to SME

[elynema]

The concept of item -> div -> span came from variations. It required non-overlapping time segments.

Here is how this content should be rendered in XML, but the Advanced Edit feature won't let you have a that has content within it:

We could theoretically change the underlying xsd for Advanced Edit, but it would allow users to create the overlapping time segments that have previously not been allowed.

Fairly straightforward to change the xsd and the production of the IIIF manifest structure to meet these needs. UX for changing SME to allow timespans to be the parent of other timespans would be harder, probably.

Making this change would theoretically allow us to become more in-line with IIIF standards (we now have a use case for that).

Next steps: consult with Jon Cameron - do we still need to maintain the rules around non-overlapping structure segments? What are the use cases?