LexBib bibliodata workflow overview: Difference between revisions

LexBib bibliodata workflow overview (view source)

Revision as of 00:57, 12 December 2021

149 bytes added , 2 years ago

→‎Elexifinder export

DavidL

Bureaucrats, Administrators

12,347

edits

@@ Line 66: / Line 66: @@
 ==Elexifinder export==
-* [https://github.com/elexis-eu/elexifinder/blob/master/wikibase/export-elexifinder.py elexifinder-export.py] generates a JSON export as needed for [[Elexifinder]], based on LexBib wikibase output obtained using SPARQL and API calls.
+* [https://github.com/elexis-eu/elexifinder/blob/master/wikibase/export-elexifinder.py elexifinder-export.py] generates dataset as needed for [[Elexifinder]], based on LexBib wikibase output obtained using SPARQL and API calls.
-* The Elexifinder export contains the following as disambiguated entities: authors, author locations, event locations, languages, containing items, and LexVoc terms as Elexifinder "categories". Publication title and date, links that point to the corresponding Zotero item and to a full text download access (at the publisher, or as DOI, etc.) are also exported, as well as the whole full text, which is processed for Wikification (Elexifinder "concepts").
+* The Elexifinder export contains one JSON object for each bibliographical item, with the following:
+** As disambiguated entities: authors, author locations, event locations, languages, containing items
+** LexVoc terms found in the full text, as [[LexVoc#Elexifinder_Categories|Elexifinder "categories"]].
+** Publication title and date
+** URL of the corresponding Zotero item
+** URL of a full text download access (direct download (preferred), 'landing page', or as doi.org link, etc.).
+** The whole full text body, which is in the Elexifinder architecture processed for Wikification (Elexifinder "concepts").
 =Maintenance tasks=