JabRef / JabRef/user-documentation
Custom import: outdated?
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 54
- Forks
- 142
- Avg merge
- 23h 56m
- Merged PRs (30d)
- 12
Description
The help page about custom import filters (http://help.jabref.org/en/CustomImports) has a section dedicated to Creating an import filter. It seems (partly ?) outdated:
- The example is given for JabRef 2.0 and JSDK 1.4 .
- Another procedure is described here https://github.com/JabRef/custom-imports
Additionally, the first sentence ("For examples and some helpful files on how to build your own importer, please check our download page") is about an unspecified download page...
Contributor guide
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
Start with the “Creating an import filter” section on the CustomImports help page and compare its procedure with the linked github.com/JabRef/custom-imports repository. Update the outdated JabRef 2.0 and JSDK 1.4 references and clarify the unspecified download-page link; done means the section matches the current procedure and its links are specific.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100