Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow display of startTime/endTime as relative or absolute #526

Open
patcon opened this issue Mar 28, 2017 · 0 comments
Open

Allow display of startTime/endTime as relative or absolute #526

patcon opened this issue Mar 28, 2017 · 0 comments

Comments

@patcon
Copy link

patcon commented Mar 28, 2017

Depending on how someone is skimming the transcript, it can be more useful for speech elements to have either the clock time or the relative timecode in a recording.

Could we add a display format selector for choosing absolute or relative?

This would seem to require:

  • Allowing something like an optional recordingStartTime attribute to each debateSection element.
  • If a debateSection has this attribute, then show a dropdown on the end-user view page, allowing preference for absolute clocktime vs relative timecode
  • For debateSections with recordingStartTime, use preferred selection, falling back to absolute if a section has no recordingStartTime. (Perhaps add a little tooltip question mark on fallback to explain to end-user?)

For this to work: Is there a section-level AN attribute in the spec that corresponds to the absolute time that the event (ie. debateSection) started?* If not, could we supplement this?

Possible caveats:

  • If the recording is not real-time (but instead has cuts), and the adminstrator doesn't understand the above behaviour, then the display of a timecode might be misleading. It would look like a video timecode, but it wouldn't align with any recording timecodes after the first cut.

Thoughts on whether this is a worthwhile train of discussion? As it stands, our workaround will be to try to put a timestamp in the corner of our livestreams, so they can be matched with SayIt transcripts. But for existing videos or third-party videos where we can't realistically get them to add timestamp watermarking, all users will have is the YouTube timecode.

* (I'll admit that I feel like I don't understand how they've documented the spec, because I don't even see startTime/endTime in the spec I can find...!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant