Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GVK search uses potentially unavailable entry types #447

Closed
stefan-kolb opened this issue Dec 2, 2015 · 7 comments
Closed

GVK search uses potentially unavailable entry types #447

stefan-kolb opened this issue Dec 2, 2015 · 7 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Milestone

Comments

@stefan-kolb
Copy link
Member

Search term examples: "Lothar Papula"

Retrieves entries that get categorized as Online. When working with Bibtex mode this entry type is not available inside the ALL_TYPES collection.

Output of Error Console:

Exception in thread "JabRef CachedThreadPool" java.lang.NullPointerException: Every BibtexEntry must have a type.
at java.util.Objects.requireNonNull(Unknown Source)
at net.sf.jabref.model.entry.BibtexEntry.setType(BibtexEntry.java:125)
at net.sf.jabref.model.entry.BibtexEntry.(BibtexEntry.java:76)
at net.sf.jabref.importer.fetcher.GVKParser.parseEntry(GVKParser.java:367)
at net.sf.jabref.importer.fetcher.GVKParser.parseEntries(GVKParser.java:63)
at net.sf.jabref.importer.fetcher.GVKParser.parseEntries(GVKParser.java:40)
at net.sf.jabref.importer.fetcher.GVKFetcher.fetchGVK(GVKFetcher.java:170)
at net.sf.jabref.importer.fetcher.GVKFetcher.processQuery(GVKFetcher.java:111)
at net.sf.jabref.importer.fetcher.GeneralFetcher$4.run(GeneralFetcher.java:288)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
@stefan-kolb stefan-kolb added the bug Confirmed bugs or reports that are very likely to be bugs label Dec 2, 2015
@stefan-kolb
Copy link
Member Author

@JabRef/developers Currently, EntryType getType() does only include valid types for the current mode. This issue is also a general problem for all fetchers that must be defined. Will we only fetch to BibTeX entry types or will we decide based on the current mode?

@koppor
Copy link
Member

koppor commented Dec 2, 2015

The GVK fetcher is optimizied for BibLaTeX. I see following options:

A. Inform the user if using BibTeX mode and refuse to fetch
B. Fallback to "Misc" at getType() when being asked for an unknown type
C. Mixture? - Warn the user and fallback.

Maybe each fetcher should be tagged what modes it supports?

@stefan-kolb
Copy link
Member Author

This is a general problem in our current architecture that's why we should discuss what to do.

@teertinker
Copy link
Contributor

I like the fallback option. In older jabref versions, gvk entries were often classified as misc. I didnt have any problems whith updating the proper type. Its a lot better than not being able to fetch at all.

@koppor
Copy link
Member

koppor commented Dec 21, 2015

For the record, a search for "667844562" returns such an entry.

@koppor
Copy link
Member

koppor commented Apr 7, 2016

I don't recall, why we closed this issue. Is it fixed or do we have to continue working on it? Refs #1069

@stefan-kolb
Copy link
Member Author

0a162b7
Temporary fix for #447 Use misc instead of online entry type

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

3 participants