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

Add 070 #1

Open
essepuntato opened this issue Feb 22, 2018 · 7 comments
Open

Add 070 #1

essepuntato opened this issue Feb 22, 2018 · 7 comments

Comments

@essepuntato
Copy link
Member

070,JST,https://www.jst.go.jp/EN/

@cm3
Copy link

cm3 commented Jan 29, 2020

Thank you for mentioning the Japanese RA.
JST is one of the institutes contributing to the Japanese RA, JaLC.

"JaLC is the only Japanese organization authorized by the IDF as a Registration Agency (RA) for DOI."
"The board member includes main contents holders such as National Institute for Materials Science (NIMS), National Institute of Informatics (NII), National Diet Library (NDL) and Japan Science and Technology Agency (JST)."
https://japanlinkcenter.org/top/english.html

so,
070,JaLC,https://japanlinkcenter.org/top/english.html

@essepuntato
Copy link
Member Author

essepuntato commented Feb 23, 2020

Hi @cm3,

In order to add JaLC to the list, JaLC needs to provide in some way -- e.g. by means of your REST API -- citation data, i.e. a representation of the link between a citing entity and a cited entity. See https://doi.org/10.6084/m9.figshare.6683855 for more information about what are the requirements that characterise a citation as an open citation.

Do you have a mechanism like the one described above in place? In case you don't have it, it is impossible for us to include JaLC data into our OCI resolver.

Since there was no news on this front in the past year, we are already using the prefix "070" for one of our projects – even if it is not yet fully advertised online - thus we need to provide you with another prefix, which is not an issue of course.

Please don't hesitate to write to me for further clarifications and questions.
Have a nice day :-)

@zuphilip
Copy link

The bibliographic data from JaLC can be requested by content negotiation, e.g.

$ curl -LH "Accept: appliation/vnd.crossref.unixref+xml, application/vnd.datacite.datacite+json, application/vnd.citationstyles.csl+json" https://doi.org/10.1241/johokanri.60.845
{
        "DOI":"10.1241/johokanri.60.845",
        "URL":"https://doi.org/10.1241/johokanri.60.845",
        "language":"ja",
        "title":"「芸術のDNA」を模写する復元技術:高精度「クローン文化財」制作",
        "author":[
                {
                        "given":"正明",
                        "family":"宮廻"
                }
        ],
        "publisher":"国立研究開発法人 科学技術振興機構",
        "issued":{
                "date-parts":
                        [
                                [2018]
                        ]
        },
        "volume":"60",
        "number":"12",
        "page":"845-854",
        "ISSN":
                ["00217298","13471597"],
        "container-title":"情報管理"
}

But I don't know if there is also a format which contains the references, or whether JaLC allows to save the references for a registered content at all.

@cm3
Copy link

cm3 commented Feb 27, 2020

Thank you @essepuntato and @zuphilip,

  • About "it MUST be possible by resolving their identifiers to obtain the basic metadata of both the entities, sufficient to create or retrieve textual bibliographic references for each of them.", as @zuphilip has already posted (thank you), it is possible to retrieve computer-readable basic information.
  • About reference information of each article, I'm asking those who should know more about it. I'll forward the information. Maybe there isn't.
  • Background of finding this issue: I added an article information to Wikidata (e.g. https://www.wikidata.org/wiki/Q83630590) to create OCI compliant citation information. Then, I noticed many articles I wanted to import to Wikidata have JaLC DOI and wondered if I can use JaLC DOI directly.
  • About "070", yes, it is not an issue. I just didn't know it has already assigned for OpenCitations Citations in Context Corpus

@essepuntato
Copy link
Member Author

Hi @cm3

Let me answer your points:

  • Indeed, for the "metadata" thing, JaLC is already compliant since it is releasing the metadata via REST, as @zuphilip said. It would be important that such metadata are #CC0 or public domain though, something I did not find explicitly stated anywhere.
  • This is the "issue" right now, i.e. the fact that the metadata returned by calling the JaLC API do not return information about the references, and thus it is pretty impossible to obtain the citation link as required.
  • If the data are in WIkidata, we can use the "010" prefix for their citations, but we cannot build a proxy service for JaLC DOIs with a new prefix. The point is that citation information (and, in particular, the citation links) must be available on the particular database (i.e. JaLC) for having a prefix assigned, and that cannot be derived from other databases.
  • OK, happy that is not an issue.

@cm3
Copy link

cm3 commented Feb 28, 2020

Hi @essepuntato

( PDFs below are written in Japanese, just for reference)

@cm3
Copy link

cm3 commented Mar 1, 2020

Correction: Last year, the licence has changed to CC0 (https://japanlinkcenter.org/top/doc/190207_m_jalcupdate.pdf), but as you have pointed out, it is not explicitly stated appropriately. I'll report that point to JaLC .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants