217 Matching Annotations
  1. Nov 2023
  2. Oct 2023
  3. Sep 2023
  4. Aug 2023
  5. Jul 2023
  6. Jun 2023
  7. May 2023
  8. Apr 2023
  9. Feb 2023
  10. Jan 2023
    1. Annotating an in-text reference pointer with a citation function

      ```turtle @prefix : http://www.sparontologies.net/example/ . @prefix cito: http://purl.org/spar/cito/ . @prefix c4o: http://purl.org/spar/c4o/ . @prefix oa: http://www.w3.org/ns/oa# . @prefix per: http://data.semanticweb.org/person/ .

      :annotation a oa:Annotation ; oa:hasBody :citation ; oa:hasTarget :in-text-ref-pointer ; oa:annotatedBy per:silvio-peroni .

      :citation a cito:Citation; cito:hasCitingEntity :paper-a ; cito:hasCitationEvent cito:extends ; cito:hasCitedEntity :paper-b .

      :in-text-ref-pointer a c4o:InTextReferencePointer ; c4o:hasContent "[6]" . ```

    2. Annotating a citation with an additional text-defined citation function

      ```turtle @prefix : http://www.sparontologies.net/example/ . @prefix cito: http://purl.org/spar/cito . @prefix cnt: http://www.w3.org/2011/content# . @prefix oa: http://www.w3.org/ns/oa# .

      :annotation a oa:Annotation; oa:motivatedBy oa:commenting ; oa:hasBody :comment ; oa:hasTarget :citation .

      :comment a cnt:ContentAsText ; cnt:chars "I'm citing that paper because it initiated this whole new field of research." .

      :citation a cito:Citation; cito:hasCitingEntity :paper-a ; cito:hasCitationCharacterization cito:cites ; cito:hasCitedEntity :paper-b . ```

    1. console $ curl -LH "Accept: application/vnd.schemaorg.ld+json" https://doi.org/10.5438/4K3M-NYVG { "@context": "http://schema.org", "@type": "ScholarlyArticle", "@id": "https://doi.org/10.5438/4k3m-nyvg", "url": "https://blog.datacite.org/eating-your-own-dog-food/", "additionalType": "BlogPosting", "name": "Eating your own Dog Food", "author": { "name": "Martin Fenner", "givenName": "Martin", "familyName": "Fenner", "@id": "https://orcid.org/0000-0003-1419-2405" }, "description": "Eating your own dog food is a slang term to describe that an organization should itself use the products and services it provides. For DataCite this means that we should use DOIs with appropriate metadata and strategies for long-term preservation for...", "license": "https://creativecommons.org/licenses/by/4.0/legalcode", "version": "1.0", "keywords": "datacite, doi, metadata, FOS: Computer and information sciences", "inLanguage": "en", "dateCreated": "2016-12-20", "datePublished": "2016-12-20", "dateModified": "2016-12-20", "isPartOf": { "@id": "https://doi.org/10.5438/0000-00ss", "@type": "CreativeWork" }, "citation": [ { "@id": "https://doi.org/10.5438/0012", "@type": "CreativeWork" }, { "@id": "https://doi.org/10.5438/55e5-t5c0", "@type": "CreativeWork" } ], "schemaVersion": "http://datacite.org/schema/kernel-4", "periodical": { "@type": "Series", "identifier": "10.5438/0000-00SS", "identifierType": "DOI" }, "publisher": { "@type": "Organization", "name": "DataCite" }, "provider": { "@type": "Organization", "name": "datacite" } }

  11. Nov 2022
  12. Oct 2022
  13. Sep 2022
  14. May 2022
    1. Exemplar output (in JSON)

      json [ { "oci": "02001010806360107050663080702026306630509-0200101080636102703040309", "citing": "10.1186/1756-8722-6-59", "cited": "10.1186/ar3439", "creation": "2013", "timespan": "P2Y", "journal_sc": "no", "author_sc": "no" }, { "oci": "02001010806360107050663080702026306630509-0200101080636102704000806", "citing": "10.1186/1756-8722-6-59", "cited": "10.1186/ar4086", "creation": "2013", "timespan": "P1Y", "journal_sc": "no", "author_sc": "no" }, { "oci": "02001010806360107050663080702026306630509-020010200003619122437020001023704023707090006", "citing": "10.1186/1756-8722-6-59", "cited": "10.1200/jco.2012.42.7906", "creation": "2013", "timespan": "P0Y", "journal_sc": "no", "author_sc": "no" }, { "oci": "02001010806360107050663080702026306630509-02003010009360008080300010805370200010237060604070907", "citing": "10.1186/1756-8722-6-59", "cited": "10.3109/08830185.2012.664797", "creation": "2013", "timespan": "P0Y", "journal_sc": "no", "author_sc": "no" }

    1. COCI, the OpenCitations Index of Crossref open DOI-to-DOI citations

      COCI, the OpenCitations Index of Crossref open DOI-to-DOI citations, is an RDF dataset containing details of all the citations that are specified by the open references to DOI-identified works present in Crossref, as of the latest COCI update*


      Open Citation Identifiers

      Each Open Citation Identifier [[OCI]] has a simple structure: the lower-case letters "oci" followed by a colon, followed by two numbers separated by a dash (e.g. https://w3id.org/oc/index/coci/ci/02001010806360107050663080702026306630509-02001010806360107050663080702026305630301), in which the first number identifies the citing work and the second number identifies the cited work.

    1. Key to DataCite service is the concept of a long-term or persistent identifier. A persistent identifier is an association between a character string and a resource. Resources can be files, parts of files, persons, organisations, abstractions, etc. DataCite uses Digital Object Identifiers (DOIs)(2) at the present time and is considering the use of other identifier schemes in the future.
    1. You might see (or inherit responsibility for) older DOIs which contain other characters, and require special treatment in a URL: Encode hash or pound sign # as %23 Do not encode left bracket (or less than) < as &lt; and right bracket (or greater than) > as &gt; when resolving DOIs or retrieving metadata from our REST API to retrieve the metadata (see below) Do not encode forward slash / when resolving DOIs or retrieving metadata from our REST API
      • EXCEPTIONS to DOI rules
    1. First, a few rules Rules are shared by all DOI registration agencies. Each DOI must be unique Only use approved characters: DOI suffixes can be any alphanumeric string that includes combinations the following approved characters: Letters of the Roman alphabet, A-Z (see below on case insensitivity) Numbers, 0-9 -._;()/ (hyphen, period, underscore, semicolon, parentheses, forward slash). Note that em and en dashes are not approved characters. Note, some older (pre-2008) DOIs which contain other characters. Learn more about suffixes containing special characters. Suffixes are case insensitive, so 10.1006/abc is the same in the system as 10.1006/ABC. Note that using lowercase is better for accessibility.
      • DOIs RULES
  15. Mar 2022
  16. Feb 2022
    1. Publishers are also encouraged to follow DOI best practices defined by Crossref, notably: A distinct DOI should be created for each version of a title deposited with CrossRef. Any title changes requiring a new ISSN should result in a new title-level DOI as well in order to ensure consistency between CrossRef and ISSN Registries. A title-level DOI should resolve to a response page that displays the same title and ISSN recorded in the ISSN Registry and in CrossRef database. Once assigned, a title-level DOI should be maintained. Responsibility for maintaining a title-level DOI transfers to the new owner when title ownership is transferred.
      • DOI
    2. Among official DOI registration agencies, CrossRef specializes in scholarly and professional publications and it assigns DOI prefixes to publishers. The latter can thus identify articles or book chapters with DOIs. They are also strongly encouraged to create DOIs for journal titles
      • Crossref
    1. https://www.zotero.org/save?type=

      URL for adding URL, ISBN, DOI, PMID, or arXiv IDs to one's Zotero account.

      I've created a mobile shortcut using the URL Forwarder app to accomplish this with a share functionality after highlighting an ISBN.

      Might also try using https://play.google.com/store/apps/details?id=com.srowen.bs.android&hl=en with the added custom search query custom search URL https://www.zotero.org/save?q=%s to see if that might work as well. This should allow using a scanner to get ISBN barcodes into the system as well. Useful for browsing at the bookstore.

      I should also create a javascript bookmarklet for this pattern as well.

      See also: - https://forums.zotero.org/discussion/77178/barcode-scanner - https://forums.zotero.org/discussion/76471/scanning-isbn-barcode-to-input-books-to-zotero-library

      Alternate URL paths for this: - https://www.zotero.org/save?type=isbn - https://www.zotero.org/save?q=

  17. Jan 2022
    1. Here’s an even more magical trick. Download that PDF to your file system, load it into a third tab, and annotate again. Now you’ll see all three annotations in all three tabs!

      Since Hypothesis doesn’t know that the local copy of the PDF came from http://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0168597&type=printable, or that it’s related to http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0168597, how is that possible?

      The answer is that the PDF standard defines a unique identifier, or “fingerprint,” that authoring tools encode into the PDFs they create. When you use the Hypothesis client to annotate web-hosted PDF, it captures the fingerprint and sends it to the server.

    2. It was already the case that you could search Hypothesis for the DOI, like so:

    3. First, here’s a magic trick you might not realize Hypothesis has up its sleeve. Consider this PLOS One article. Annotate it in one tab, then open a second tab and annotate the PDF version there. You’ll see both annotations in both tabs. How is that possible?

      The answer is that when scholarly publishers provide HTML versions of articles, they typically include metadata that points to PDF versions of the same articles. Here’s one way that happens:

      <meta name=”citation_pdf_url” content=”http://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0168597&type=printable”>

      Hypothesis remembers the correspondence between the HTML and PDF versions, and coalesces annotations across them.

    1. adamsmith October 15, 2018 Add Item by Identifier will work for any DOI registered in Crossref or a half-dozen other DOI registrars Really? I thought we currently "just" covered CrossRef, DataCite, and Airiti? - which does still mean it almost always works; that's probably 95%+ of active DOIs, but if there's code already that covers others, that'd be good to know as I was just going to put some work towards that. dstillman October 15, 2018 We also have DOI translators for EIDR and mEDRA.
      • DOI agencies
      • Zotero probes them, when search for a DOI
    1. Each case-insensitive DOI is first normalized to lower case letters
    1. DOI registration agencies such as Crossref, DataCite and mEDRA collect bibliographic metadata about the works they link to.
      • DOI agencies
      • 2022-01: zotero field DOI: WITHOUT https, NOR URL
    1. More recently, there has been a strong movement to move the web over from HTTP to the more secure HTTPS protocol. Technical changes also made it possible to link DOIs via the shorter doi.org instead of dx.doi.org. Together, this let Crossref change its recommended format to https://doi.org/10.1037/rmh0000008.
    2. As Crossref explains in their guidelines, the original concise doi:10.1037/rmh0000008 format was recommended with the hope that web browsers would one day automatically recognize and hyperlink these DOIs.
      • CONCISE format
    3. Effective March 2017, Crossref, an influential DOI registration agency, now recommends the following format: https://doi.org/10.1037/rmh0000008 Note the use of “https” instead of “http”, and “doi.org” instead of “dx.doi.org”.
    1. _re_id["doi"] = re.compile(r"\b10\.\d{4,}(?:\.\d+)*\/(?:(?!['\"&<>])\S)+\b") _re_id["bibcode"] = re.compile(r"\b\d{4}\D\S{13}[A-Z.:]\b") _re_id["arxiv"] = re.compile(r"\b(?:\d{4}\.\d{4,5}|[a-z-]+(?:\.[A-Za-z-]+)?\/\d{7})\b")
      • REGEX
  18. Dec 2021
    1. The redirection is functionally equivalent to the way the DOI system uses a proxy server, doi.org (or dx.doi.org, an earlier syntax which continues to be supported), which re-interprets DOI name queries into http

      dx.doi.org is EARLY syntax

    1. There are interfaces for people (to look up small numbers of DOIs): Metadata Search, and Simple Text Query.

      2 ways

    2. Here is a comparison of the metadata retrieval options


    1. ShortDOIs are great for sharing a quick link over email or for display on presentation slides, but they shouldn’t be used in publications (eg, this may interfere with citation cross-linking, which relies on matching DOIs)

      Well, don't use them! better the compatible way

    2. I would not be surprised if the service were shut down at some point.

      hahaha. changes for the worse!

    3. You should not use shortDOI in references


    1. The reason for overly long DOIs are the local provisions to prevent collision of automatically generated DOIs