Add handling of annotations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Annotations belong to a PDF. PDFs belong to a BibEntry.
- A click on a BibEntry
- I click on "add files"
- JabMap creates sub nodes with with all PDFs files belonging to this entry
- I click on a PDF
- I click on "add annotations"
- JabMap creates sub notes with all PDF annotations
Variants:
- "Refresh annotations" - adds new annotations (and removes non-existing ones). NOTE: JabMap remembers which annotations have been deleted by the user before and does NOT add them again
- "Refresh PDFs" - similar to "annotations"
- "Inbox", where automatically new annotations, pdf files, and BibEntries flow in
In case a PDF belongs to more than one BibEntry, handling might geht strange, but we focus on this relation kind here. (This somehow refs https://github.com/JabRef/jabref/issues/8128, which describes "proceedings", which is a complete PDF containing multiple papers)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Start by tracing the entry points for “add files” and “add annotations” and how BibEntry, PDF, and annotation nodes are represented; done means annotations can be exposed under a PDF, with the described refresh and deletion behavior accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100