Change "runningSpeed" field name to essenceTrackFrameRate; add essenceTrackPlaybackSpeed field

[pamelajean]

essenceTrackPlaybackSpeed field

[tingletech]

I think it is a bad idea to conflate the mapping to PBCore with the field names. I'm really reluctant to change the names in the schema. I also object to putting so much of the xml path from the PB Core into the field names, it seems like it makes this harder to maintain (even if it is easier for you to map)

The other field names have consistently been at the level of the most specific part of the PBCore name or note, which did not appear to be very ambiguous when I compared it with PBCore2.

Is this a change from "runningSpeed" to "essenceTrackFrameRate"?

Also, can you help me by adding links in the tickets to specific line numbers with these types of requests? For example for this you are asking for a change to
https://github.com/tingletech/collengine/blob/master/items/models.py#L158

[pamelajean]

Why is it a bad idea to maintain PBCore field names? It's not just for my ease, but for Media Preserve's too. Otherwise I'll need to cut and paste into a "Media Preserve reader-friendly" format. I want it to be clear for MP so I won't have to go back and "fix" MP's metadata when they send it back.

Is there a way for us to have a 'display' field name vs an 'output' field name?

One of my favorite improvements of PBCore v. 2 is that instantiation is part of the element name so characteristics for the asset as a whole are distinguished, then you can add information unique for the analog and digital instantiations. There are some changes to the terminology as well, ie "runningSpeed" should be "essenceTrackFrameRate".

(I'll add line #s to my other comments)

[tingletech]

The most specific part of the field name I don't object to; it is the full path of the PBCore XML getting into the field name when it is not needed to disambiguate the field name that I object to. The names are getting ridiculously long / and the whole use case of exporting all the data early in the project to digitization vendor is a new requirement that is unique to your workflow compared with other projects we have worked on.

[pamelajean]

ok; could we shorten field name from "instantiationEssenceTrack_essenceTrackFrameRate" to simply "EssenceTrackFrameRate"? I can follow the path, and I expect MP can too.

I didn't anticipate the vendor caring about existing md until recently... so this is a new understanding for us too.

[tingletech]

"essenceTrackFrameRate" is what I will use to be consistent with the rest of the field names.

[pamelajean]

ok