Find unlinked files should ignore Thumbs.db etc.

[koppor]

Use case:

1. git init
2. git add library.bib
3. Have PDF files within that directory
4. Execute "find untlinked" files

Then all files .git are offered, too

• Basic implementation: Ignore a hard-coded list of files
• Advanced implementation: Read .gitignore in the root of the library path and obey it.

[koppor]

In my use-case blocked by JabRef#3626

[calixtus]

The user can choose between the options .pdf and . (All files). Imho one should get all files if one chooses all files. A clean solution for this issue would be to create an extra textfield "exclude files": ".sys;thumbs.db"...

[mariotachikawa]

I have some questions about this issue:

• when should the files be ignored (git or in jabref?)
• where should the execute "find unlinked files" be?
• should the end user of Jabref use this or is it only for development?
• besides Thumbs.db, what other files should be ignored?

In general, our university group is not sure if we understand this issue correctly. It would be helpful, if we could get some more details about the problem, if possible.

[calixtus]

Hi, sorry for the delay, just had some very stressful days. About your questions:

1. The files should be ignored when jabref is scanning for unlinked (attachable to an entry) files. Jabref should maybe read .git or .gitignore to know, which files should be ignored in a directory to scan.
2. There exists a dialog called "Find unlinked files" which already provides the scan logic etc. It should be easy to expand the logic to create a list of files to ignore
3. The end-user should be able to enable or disable some ignore option or have a list presented with files or filetypes to be ignored
4. See answer 1. Maybe be creative too.

Godspeed!

[prashant1712]

Hi, we are a group of students studying Master of Computer Science in University of Adelaide and we wanted to check if this issue is available/open for us to work on for our assignment.

[calixtus]

Since I did not hear about the other developer for months I believe this issue should be available to be solved.
Please remember to prepare your workspace according to our developer docs (especially checkstyle) so we can prevent a lot of questions and issue in the review process. Feel free to ask questions in our Gitter channel, if you don't understand something!

Have fun coding!

[prashant1712]

Thank you for your response. We'll start with the issue and we expect to submit the pull request by the first week of May 2022.

[calixtus]

Ok. The other dev thought he had to implement a completely new dialog. This is not necessary. Goal is to improve the existing one!