74 Matching Annotations
  1. Jul 2019
  2. Jun 2019
  3. May 2019
    1. Require DOI?: Set this to true in order to generate a permanent identifier for this collection (Please set this to true for collections related to publications).
  4. Apr 2019
  5. Mar 2019
    1. Super cool. The difference between annotating the web, and annotating academic scholarship / science.

  6. Feb 2019
  7. Dec 2018
  8. Nov 2018
  9. Oct 2018
  10. Aug 2018
  11. Jul 2018
  12. Jun 2018
    1. The most up-to-date version of the open-source package NPTFit may be found at https://github.com/bsafdi/NPTFit and the latest documentation at http://nptfit.readthedocs.io. In addition, the version used in this paper has been archived at https://zenodo.org/record/380469#.WN_pSFPyvMV.

      This is an example of incorrect software citation per the AAS Journal's policy. The Zenodo metadata should have been added to the reference list as a 1st class citation.

      It is also an example of an incorrectly typeset URL. URLs that come from DOIs should be typeset using the DOI string not the resolved URL. It should have read, "version used in this paper has been archived at https://doi.org/10.5281/zenodo.380469"

    2. Foreman-Mackey D., Vousden W., Price-Whelan A. et al 2016 corner.py: corner.py v2.0.0, doi:10.5281/zenodo.53155

      corner.py is one of the more interesting examples of software citations. there are at least 3 different formal references in the wild:

      https://doi.org/10.5281/zenodo.11020 https://doi.org/10.5281/zenodo.53155 https://doi.org/10.21105/joss.00024

      with different versions and author lists.

    1. Barbary K. 2014 sncosmo Zenodo, 10.5281/zenodo.11938

      This software citation losts its version information. We will have to work on our typsetting and production rules, as well as develop formal JATS/NLM XML schema to contain versioning information.

    2. https://doi.org/10.5281/zenodo.11938

      This DOI software archive is also in the Reference list per our Journal's software policy.

    3. The catalog of fakes used to generate the efficiency grids in Section 3 are available in a persistent directory: doi:10.5258/SOTON/D0030.

      This is the dataset related to this article. It contains reproducibility and reusable data for readers.

      Our "article data" tab is suppose to show this entry, but the article data tab is currently linked to the wrong DOI (the Zenodo one highlighted below).

      We do not yet submit this type of data citation as CrossRef metadata. We are still discussing how data citations should appear and be acknowledged in the text.

  13. Mar 2018
  14. Jan 2018
      • audience consensus: little discussion necessary about whether blogs should have DOIs, concrete implementations needed
      • manual DOI registration possible, but of little use
      • API call better, but integration from blogging software necessary
      • SEO also requires exposing metadata => interests align
      • schema.org/BlogPosting suggested
      • https://blog.datacite.org/ uses JSON-LD
      • https://wordpress.org/plugins/schema/
      • sitemap needed so that indexer can find the posts to then extract metadata
      • beta testers from institutions that already register DOIs welcome
  15. Nov 2017
    1. ADS shares those matches with us via its API, and we use that information to populate DOI and JREF fields on arXiv papers.

      I've always wondered if this were true. I continue to wonder if arXiv uses other sources of eprint-DOI matches to corroborate or append to those from ADS.

    1. if cross-format identifiers like DOIs are used, annotations made in one format (eg, EPUB) can be seen in the same document published in other formats (eg, HTML, PDF) and in other locations.

      Whaa..? This sounds seriously hard. But remarkably clever.

  16. Jul 2017
    1. The proxy service (both doi.org and the earlier but no longer preferred dx.doi.org)
  17. Jun 2017
    1. Hypothesis now uses DOIs to join variants of the same document in the same way it uses PDF fingerprints. Both pieces of metadata — the DOI, and the PDF URL — are typically included in HTML metadata.

      This is really cool! Thanks for the great explanation!

  18. May 2017
    1. Each item added to the repository will be assigned a DOI, which means you can trust they will be persistently resolvable.  In our exemplar role, we will ultimately be connecting the DOI to the creator’ ORCID iDs

      on DOIs and ORCIDs in websites

  19. Nov 2016
  20. Jul 2015