Citation key generator and Linked files
A tabular construct similar to "Key patterns" is sometimes required for "Linked files (Filename format pattern)".
Some examples:
- Book file names are not always long enough and can be fully described in the "title" including also the date and first author:
2024_Medium-length_book_title_ (author's_last_name)
- When considering a “PhD thesis” since titles can be quite long, you can limit yourself to the first few words of the “title” and add a note that this is a [PhD thesis], like here:
2024_A_few_words_from_the_title_...[PhD_thesis](author's_last_name)
For the examples discussed above, it is necessary to change the “Filename format pattern” pattern each time, although there is no such problem for “Key patterns” due to the tabular design.
Thanks for the suggestion, indeed: Just adding some context for others who want to work on this:
Preferences -> Linked Files currently looks like this:
It should have a similar UI:
Code hints:
Create new Preferences, similar to CitationKeyPatternPreferences with a list of Patterns. Take a look at. AbstractCitationKeyPatterns
FileUtil.createFileNameFromPattern - Current method for generating the filename based on a pattern.
HInt, create a method simliar to the citattion key generat to get the pattern:
CitationKeyPattern citationKeyPattern = citeKeyPattern.getValue(entryType);
Hello, my name is Nathan, and I’m a student at the Australian National University. As part of my semester course, my team of five has been tasked with contributing to an open-source software project. I would like to take on this issue and contribute to the project. Could you please assign me to it?
👋 Hey @priyanshu16095, thank you for your interest in this issue! 🎉
We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.
In case you encounter failing tests during development, please check our developer FAQs!
Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.
Happy coding! 🚀
⏳ Please note, you will be automatically unassigned if the issue isn't closed within 90 days (by 22 May 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.
/unassign-me
/unassign-me
👋 Hey @priyanshu16095, you've been automatically unassigned from this issue due to inactivity.
[!NOTE] If you'd like to be re-assigned, just leave another comment or ask a maintainer to assign you again. If you're still actively working on the issue, let us know by commenting, and we can pin it to prevent automatic unassignment.
/assign-me
👋 Hey @priyanshu16095, thank you for your interest in this issue! 🎉
We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.
In case you encounter failing tests during development, please check our developer FAQs!
Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.
Happy coding! 🚀
⏳ Please note, you will be automatically unassigned if the issue isn't closed within 45 days (by 16 April 2025). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment.
📋 Assignment Update
Hi @priyanshu16095, you are no longer assigned to this issue.
Next steps
If you still want to work on this:
- Comment with
/assign-meto request reassignment - Ask a maintainer to assign you again
- If you're making progress, a maintainer can add the pin label to prevent future automatic unassignment
/assign-me
⚠️ Reassignment Blocked
Hi @priyanshu16095, you cannot assign yourself to this issue again.
[!NOTE] Since you were previously unassigned from this issue, a maintainer needs to approve your reassignment.
Please ask a maintainer to assign you if you'd like to continue working on this issue.
/assign @priyanshu16095
👋 Hey @priyanshu16095, thank you for your interest in this issue! 🎉
We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.
In case you encounter failing tests during development, please check our developer FAQs!
Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.
Happy coding! 🚀
⏳ Please note, you will be automatically unassigned if there is not a (draft) pull request within 14 days (by 31 March 2025).
/assign-me
👋 Hey @sobinovskymatus, thank you for your interest in this issue! 🎉
We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.
For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.
In case you encounter failing tests during development, please check our developer FAQs!
Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.
Happy coding! 🚀
/unassign-me
📋 Assignment Update
Hi @sobinovskymatus, you are no longer assigned to this issue.
Next steps
If you still want to work on this:
- Comment with
/assign-meto request reassignment - Ask a maintainer to assign you again
- If you're making progress, a maintainer can add the 📌 Pinned label to prevent future automatic unassignment