> For the complete documentation index, see [llms.txt](https://autoedit.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://autoedit.gitbook.io/documentation/transcriptions/papercuts.md). # Selections, Annotations, Papercuts ## Component/part description Semanticly papercuts can be selections, hilights, annotations when found in a transcription but is only as the building block of a paper-edit that we refer to them as paper-cuts. Connected to this is defining a schema for paper-edit, to make sure all components that work with this have a defined interface/specification. Same as EDL papercut/”event” object in “EDL JSON: schema from EDL composer component module from autoEdit2.
![img/sketches/Transcription%20Show%20Annotate.png](https://lh5.googleusercontent.com/y0N4t1uKFgicA73JOoMyR6U4iicJU0rqq8EGAvzMvKfOlMTVIIAtsK7HOIbkMoURp7NgCiaN1SyD6B09GWsPa202-m_pWX24uO8wdkOgdct4LiD9iFBbczH-fJgxVNK8-f0-N_Tj) ### Selections component A component that can make a selection of word objects from a transcription/hypertranscript. ### Annotations Associate a selection with a tag, a tag description and a comment. ### Tags Tags to group annotations. \-- ## Related projects. ### Annotations Need Annotation schema specification Check out recent annotation spec by W3C Combine, selection, annotation, tag, and event info/papercut for paper edit/“JSON EDL” when multiple annotations combined. With some as optional fields. Eg tags, etc.. Could use to keep annotation close to selection in trascription . And coul use bootstrap popovers \-- ## Implementations Options considered ### Selections Selections Make text selection of transcription To look into \-- ## Current implementation Paper-edit json schema specification Connected to this is defining a schema for paper-edit, to make sure all components that work with this have a defined interface/specification. Same as EDL papercut/”event” object in “EDL JSON: schema from EDL composer component module from autoEdit2. ### Selection ended up using intermediate data structure. Data is stored in html in data attribute for ease of retrieval at word level. \-- ## What needs refactoring ### → Refactoring: Words Selections How to do text selection for highlight paper cuts. Currently in transcription show it traverse the DOM to update those. Eg see selecting words function. That recognises uses selection. And this function to update the dom with selections. There might be a better way to do this? Using rangy ? ### refactoring words data Data is stored in html in data attribute for ease of retrieval at word level. this is very bulky. There might be more elegant options, using listeners and events(?) or other(?). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://autoedit.gitbook.io/documentation/transcriptions/papercuts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.