You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a content editor, I want the location field for digital edition/translations to automatically populate from an existing edition/translation on the same source, so that I can save time manually re-entering it.
#1420
Add an Edition footnote with some value in the "location" field
Add a new transcription with the transcription editor on the same source as the Edition footnote you created
In the transcription editor, create some annotation blocks on the images
On the document, there should now be a new Digital Edition footnote with the same location as the Edition footnote
Try the same with a Translation footnote with a location, adding a translation on the same source in the translation editor. The newly created Digital Translation footnote should get the same location as the Translation footnote
Try this on a document with more than one Edition footnote on the same source, each having different locations. Using the transcription editor to create a new transcription on that source should not populate the new Digital Edition footnote with a location, since it is ambiguous which Edition footnote should be used.
Requested by @mrustow over Slack. This should include:
A one-time migration to copy all Footnote.location values from edition to digital edition, and translation to digital translation, on the same Source
Logic to populate this automatically when users are creating digital content via annotations in the transcription/translation editor
The text was updated successfully, but these errors were encountered:
testing notes (qa)
In the QA admin site, navigate to a document.
Requested by @mrustow over Slack. This should include:
Footnote.location
values from edition to digital edition, and translation to digital translation, on the same SourceThe text was updated successfully, but these errors were encountered: