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

dev: use CiTO (ontology) for paper facts and citations #119

Open
geritwagner opened this issue Feb 3, 2023 · 0 comments
Open

dev: use CiTO (ontology) for paper facts and citations #119

geritwagner opened this issue Feb 3, 2023 · 0 comments
Labels
question Further information is requested

Comments

@geritwagner
Copy link
Collaborator

geritwagner commented Feb 3, 2023

CiTO provides an ontology that standardizes facts and citation types. For example, citations between papers can be stated based on record IDs, they can be qualified, and analyzed for facts (like retract status). Since these fields are not standardized in BiBTex, a separate CiTO/rdf document should be introduced. Qualifying citations would also be useful for citation searches (selection) and analyses.

Explore data structures for citation relations (between records and beyond the sample), the retrieval of structured data, the codification and collaborative editing of graph-data; define standardized fields (e.g., cited_by: number or references? cited_by_file (cited_by (number) and cited_by (backward search) write to the same field), semantic relations like “corrects paper X”, “tests paper X”, or codings like “empirical”/”meta-analysis-ready”)

Open questions:

  • Is CiTO the best option/what are the alternatives?
  • If data is added to the ontology in the search/prep operations, how do we handle potential changes in record IDs (set_ids)?
  • Should the ontology be part of curations/local_index? How can we implement provenance and correction paths?
  • Should the ontology be included by default or optional (e.g., for citation analyses)?
  • The facts could be stated based on origins.

Generally, we should avoid separate and redundant data structures. One possibility would be to add a dictionary/json to the bib file (REFERENCES/CITATIONS field).

@geritwagner geritwagner added the enhancement New feature or request label Feb 3, 2023
@geritwagner geritwagner added this to the v0.8.0 milestone Feb 3, 2023
@geritwagner geritwagner added the good first issue Good for newcomers label Feb 6, 2023
@geritwagner geritwagner removed this from the v0.8.0 milestone Feb 7, 2023
@geritwagner geritwagner mentioned this issue May 8, 2023
41 tasks
@geritwagner geritwagner added question Further information is requested and removed enhancement New feature or request good first issue Good for newcomers labels Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant