hbz / lobid-resources

Transformation, web frontend, and API for the hbz catalog as LOD
http://lobid.org/resources
Eclipse Public License 2.0
7 stars 7 forks source link

Enable export of Merkliste to reference managers #583

Open acka47 opened 6 years ago

acka47 commented 6 years ago

We should at least support BibTex. See also https://github.com/hbz/nwbib/issues/40.

ChristophEwertowski commented 6 years ago

Also wished for by FRL customer ZBMed, see https://jira.hbz-nrw.de/browse/FRL-366. Also, in a PDF mapping suggestions are stated. Update: The JIRA-issue refers to all resources, not only the ones saved in a Merkliste.

ChristophEwertowski commented 5 years ago

Also see https://github.com/hbz/lobid/issues/277.

acka47 commented 5 years ago

We might use Citation.js here.

acka47 commented 5 years ago

There exists a "JSON schema for CSL input data" at https://github.com/citation-style-language/schema/blob/master/csl-data.json which might be useful.

cboulanger commented 1 year ago

Please prioritize CSL-JSON, it is far superior to BibTeX in terms of data resolution and can be easily converted to BibTeX if required.

Siedlerchr commented 11 months ago

Wir von JabRef währen auch sehr interessiert an einem BibTeX exporter order konverter, wir arbeiten gerade an einer Integration der Suche.
https://github.com/JabRef/jabref/pull/10135 bzw https://github.com/koppor/jabref/issues/386

acka47 commented 9 months ago

We should:

We should plan on Monday when we will finally implement this.

acka47 commented 9 months ago

JabRef has now added the lobid fetcher, see https://github.com/koppor/jabref/issues/386. It converts lobid-resources data to BibTex, so we might reuse their mapping or so.

acka47 commented 6 months ago

DigiBib is already providing an export to BibTex and RIS:

image

@heikojansen based on which data are you providing this export? If you already created this from lobid JSON, it might make sense to reuse your solution. /cc @eschackmann

heikojansen commented 6 months ago

@acka47 - The export function in DigiBib is based on our internal, DigiBib-specific data format.

DigiBib is a front end to a bunch of different back end systems (indexes) with very different data formats. Any data we retrieve is converted to our internal format on the fly so that the portal functions only have to deal with one format.

In this case this unfortunately means that you won't be able to make use of our existing code.

acka47 commented 6 months ago

Thanks for the information, @heikojansen !