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

Rework ICAR Fetcher #8876

Closed
koppor opened this issue May 31, 2022 · 4 comments · Fixed by #8904
Closed

Rework ICAR Fetcher #8876

koppor opened this issue May 31, 2022 · 4 comments · Fixed by #8904
Labels
fetcher good first issue An issue intended for project-newcomers. Varies in difficulty.

Comments

@koppor
Copy link
Member

koppor commented May 31, 2022

Our fetcher calls the URL https://eprint.iacr.org/eprint-bin/cite.pl?entry=2022/674.

This leads to a 404:

grafik

We need to rewrite the IacrEprintFetcher to rely on https://eprint.iacr.org/ID (example: https://eprint.iacr.org/2022/674) only.

PR implementing the fetcher: #3473

@derTimme Are you still active? Could you have a look?

@koppor koppor changed the title IACR fetcher IACR fetcher relies on 404 URL May 31, 2022
@koppor koppor added the fetcher label May 31, 2022
@koppor koppor mentioned this issue May 31, 2022
6 tasks
@Siedlerchr
Copy link
Member

Siedlerchr commented May 31, 2022

In the news they state they now support this 25-Apr-2022: ePrint rewritten in Python. Features include better capture of metadata and [OAI-PMH harvesting](https://eprint.iacr.org/oai?verb=Identify).

https://eprint.iacr.org/oai?verb=ListRecords&metadataPrefix=oai_dc

https://eprint.iacr.org/rss/

We provide several ways to harvest information from eprint.iacr.org, including an RSS feed (version 2.0), an Atom feed, and OAI-PMH harvesting. All are XML formats. We can also provide other formats upon request.

@Siedlerchr Siedlerchr added the good first issue An issue intended for project-newcomers. Varies in difficulty. label May 31, 2022
@Siedlerchr Siedlerchr changed the title IACR fetcher relies on 404 URL Rework ICAR Fetcher May 31, 2022
@LIM0000
Copy link
Contributor

LIM0000 commented Jun 1, 2022

Based on previous fetcher implementation in #3473, the idea follows the feature:

  • Fetched entry is of type misc and contains:
    • Title
    • Authors
    • Url (contains the version)
    • Note with \url{https://eprint.iacr.org/} (recommended by IACR)
    • Howpublished like Cryptology ePrint Archive, Report (recommended by IACR)
    • Version (most recent)
    • Date (of the most recent version)
    • Abstract

The misc from https://eprint.iacr.org/2022/674 contains:

  • Fetched entry is of type misc and contains:
    • Authors
    • Title
    • Howpublished like Cryptology ePrint Archive, Report (recommended by IACR)
    • Year
    • Note with \url{https://eprint.iacr.org/} (recommended by IACR)
    • Url (contains the version)

111

Additional Information

I am not too sure what the version and which date should be parsed into entry field.

Date:

Should we set received date or approved date in date field?

Version:

I am not too sure what a version is. Could someone please advice me what a version is for https://eprint.iacr.org/2022/674 ?
Many thanks!

@Siedlerchr
Copy link
Member

Date: I think we should use the approved one.
Version: If you submit a paper and correct it afterwards, the version number will be increased. Just a versioning system to know which version at a specific time was available and which one did you cite (e.g, v1 might have an error or something wrong, that was then corrected in v2)
Arxiv uses such versioning as swell

@LIM0000
Copy link
Contributor

LIM0000 commented Jun 9, 2022

Thanks @Siedlerchr , I will raise a PR for this issue as soon as I am available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fetcher good first issue An issue intended for project-newcomers. Varies in difficulty.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants