Persistent Identifiers & Open Scholarly Infrastructure

A webinar for PKP; Getting Found, Staying Found.

Mike Nason
Open Scholarship & Publishing Librarian @ UNB Libraries
Crossref & Metadata Liaison @ Public Knowledge Project (PKP)

~40m

Overview of persistent identifiers, open scholarly infrastructure, and what researchers need to know about them.

The talk will cover DOIs, ORCID, ROR, and other players/service providers in the PID space.

Agenda

What is a persistent identifier?
What is a registration agency?
What is open scholarly infrastructure?
What PIDs should I care about?

~10m

Where you can find your PID settings and information in OJS, and how to make sure you're doing your due diligence as a journal.

Introduction(s)

I'm the open scholarship & publishing librarian (aka, I guess, "scholarly communications") at what, to most of you, would be a pretty small school in Atlantic Canada (University of New Brunswick).

I also work for PKP as a member of their publishing services team, where I am the Crossref/metadata liaison.

I stand at a pretty interesting professional intersection between publishing, authoring, and discovery.

That means I more or less never shut up about open scholarly infrastructure!

Like a lot of people who don't shut up, i look like this:

I am a [white, cis] settler from the unceded (aka, stolen) territory of the Mi'kmaq-Wolastoquey peoples just a short hop from the wolastoq river. Settlers to the region renamed this river the “Saint John River”, a testament to both their repression and lack of creativity.

Lots of people (even, to my perpetual dismay, many Canadians) do not know where New Brunswick is. It is up here, next to Maine.

It is north of Nova Scotia and west of Prince Edward Island.

I'd like for you to keep a thought on the backburner.

Persistent Identifiers are
in the drinking water of
scholarly publishing.

I'll come back to this.
Like, a lot.

Let's start small.

The DOI.

DOIs

DOIs are ubiquitous. We see them all over the place:

in references/bibliographies
on article/journal websites
in repositories
on published datasets
links on Twitter or ResearchGate or Academia dot edu or, or, or...

In the wild

In citations

Barr, S. M., White, C. E., & Pin, C. (2022). Revised stratigraphy in the eastern Meguma terrane, Nova Scotia, Canada, and variations in whole-rock chemical and Sm–Nd isotopic compositions of the Goldenville and Halifax groups. Atlantic Geoscience, 58, 193–213. https://doi.org/10.4138/atlgeo.2022.008

DOIs

And, we probably know one handy thing about them:

If you click on a DOI that looks like a link, it will take you to the thing.

DOIs

DOIs are the most prominent persistent identifier.

They are also, arguably, the most important persistent identifier.

How a DOI works

A DOI is made up of two chunks. A prefix, and a suffix.

prefix

10.4324

suffix

9780203051238-5

Together, these make the DOI 10.4324/9780203051238-5

How a DOI works

Prefixes and suffixes mean different things.

prefix

10.4324

A prefix is usually associated with a publisher or organization. DOIs for that organization will usually have the same prefix.

suffix

9780203051238-5

A suffix is meant to be a machine-readable (not human-readable), opaque, unique string that is specific to the singular work to which it is assigned (we'll talk more about this).

How a DOI works

Throughout this presentation, I'll be digging deep on this DOI.

prefix

10.4138

This prefix is held by Crossref member, Atlantic Geoscience, a journal we host here at UNB Libraries... I'll talk more about this as we go.

suffix

atlgeol.2022.008

You can see here that their suffixes follow a pattern, and you can probably guess that pattern. This is very common, despite being both unnecessary and discouraged.

How a DOI works

If I prepend a DOI with https://doi.org/, it turns into a URL.

https://doi.org/10.4138/atlgeol.2022.008

Clicking this will redirect me to the publication this DOI is associated with. The process of a DOI redirecting you to a publication is called resolution.

What's "resolution"?

How DOI resolution works

DOIs aren't just like a bit.ly link or tiny.url. If you're not familiar with these services, they will swap out a very large and unwieldy link so you can share something that isn't enormous.

For example: https://bit.ly/48fy2pZ
This 👆 is a bit.ly link for this talk.

The actual URL for this talk is: https://slides.com/ahemnason/pids-ojs /

bit.ly and tiny.url are both basic redirects.

How DOI resolution works

But, plenty of people treat DOIs this way, or assume it's their only real function. Or, they make some sort of wild assumption that DOIs are some sort of certification.

How DOI resolution works

A DOI, though, is a lot more than a redirect. A DOI is a reference to an entire publication record. That publication record is full of metadata.

And, one of these metadata elements is the publication's URL.

When you resolve a DOI by clicking on it:

the record is accessed,
the stored URL is retrieved,
you are sent to the stored URL.

The URL can be updated by the publisher. The DOI stays the same.

<?xml version="1.0" encoding="UTF-8"?>
<crossref_result version="3.0" xsi:schemaLocation="http://www.crossref.org/qrschema/3.0 http://www.crossref.org/schemas/crossref_query_output3.0.xsd">
  <query_result>
    <head>
      <doi_batch_id>none</doi_batch_id>
    </head>
    <body>
      <query status="resolved">
        <doi type="book_content">10.4324/9780203051238-5</doi>
        <crm-item name="publisher-name" type="string">Informa UK Limited</crm-item>
        <crm-item name="prefix-name" type="string">Informa UK (Routledge)</crm-item>
        <crm-item name="member-id" type="number">301</crm-item>
        <crm-item name="citation-id" type="number">122425695</crm-item>
        <crm-item name="book-id" type="number">1477192</crm-item>
        <crm-item name="deposit-timestamp" type="number">2020122110554080199</crm-item>
        <crm-item name="owner-prefix" type="string">10.4324</crm-item>
        <crm-item name="last-update" type="date">2020-12-21T15:07:00Z</crm-item>
        <crm-item name="created" type="date">2020-12-21T15:06:59Z</crm-item>
        <crm-item name="citedby-count" type="number">0</crm-item>
        <doi_record>
          <crossref xsi:schemaLocation="http://www.crossref.org/xschema/1.1 http://doi.crossref.org/schemas/unixref1.1.xsd">
            <book book_type="other">
              <book_metadata language="en">
                <contributors>
                  <person_name sequence="first" contributor_role="author">
                    <given_name>Richard</given_name>
                    <surname>Smiraglia</surname>
                  </person_name>
                </contributors>
                <titles>
                  <title>Metadata</title>
                  <subtitle>A Cataloger's Primer</subtitle>
                </titles>
                <edition_number>0</edition_number>
                <publication_date media_type="online">
                  <month>11</month>
                  <day>12</day>
                  <year>2012</year>
                </publication_date>
                <isbn media_type="electronic">9780203051238</isbn>
                <publisher>
                  <publisher_name>Routledge</publisher_name>
                </publisher>
                <doi_data>
                  <doi>10.4324/9780203051238</doi>
                  <timestamp>2020122110554078499</timestamp>
                  <resource>https://www.taylorfrancis.com/books/9781136435843</resource>
                </doi_data>
              </book_metadata>
              <content_item component_type="chapter" publication_type="full_text" language="en">
                <titles>
                  <title>Understanding Metadata and Metadata Schemes</title>
                </titles>
                <publication_date>
                  <year>2012</year>
                  <month>11</month>
                  <day>12</day>
                </publication_date>
                <pages>
                  <first_page>25</first_page>
                  <last_page>44</last_page>
                </pages>
                <doi_data>
                  <doi>10.4324/9780203051238-5</doi>
                  <timestamp>2020122110554080199</timestamp>
                  <resource>https://www.taylorfrancis.com/books/9781136435843/chapters/10.4324/9780203051238-5</resource>
                </doi_data>
              </content_item>
            </book>
          </crossref>
        </doi_record>
      </query>
    </body>
  </query_result>
</crossref_result>

I'm sorry to do this to you.

There's a lot of information here:

publisher
deposit and update timestamp
book type
contributors (first, role=author)
title and subtitle
publication date
doi for the book
link for the book
chapter title
doi for the chapter
link for the chapter

<doi_data>
  <doi>10.4324/9780203051238</doi>
  <timestamp>2020122110554078499</timestamp>
  <resource>https://www.taylorfrancis.com/books/9781136435843</resource>
</doi_data>
</book_metadata>
<content_item component_type="chapter" publication_type="full_text" language="en">
  <titles>
    <title>Understanding Metadata and Metadata Schemes</title>
  </titles>
  <publication_date>
    <year>2012</year>
    <month>11</month>
    <day>12</day>
  </publication_date>
  <pages>
    <first_page>25</first_page>
    <last_page>44</last_page>
  </pages>
  <doi_data>
    <doi>10.4324/9780203051238-5</doi>
    <timestamp>2020122110554080199</timestamp>
    <resource>https://www.taylorfrancis.com/books/9781136435843/chapters/10.4324/9780203051238-5</resource>
  </doi_data>
  

<!-- urls are part of the metadata of a doi. -->
<!-- when you change the location of content, you update your doi with the new location. everyone who uses the doi gets to the content no matter where you put it, so long as that doi is updated. this means, the doi is persistent.-->

Neat!

It is.

Surely, there is more to it?

🤔🤔🤔

Yeah, buddy!

Let's review

DOIs are persistent identifiers.
They are made up of prefixes and suffixes, each with their own meaning.
Clicking on a DOI that is formatted as a URL will take me to the URL stored in that DOI's metadata record.
A DOIs metadata record has heaps of information.
DOIs are not just redirecting links.

Congratulations, you now know more about DOIs than a frankly surprising number of people.

And, by extension, you now know more about PIDs than a frankly surprising number of people.

**Let's step back a bit to talk about persistent identifiers in general.**

Persistent Identifiers (PIDs)

An identifier // A unique string of characters assigned to something, someplace, or someone that can be used to identify it.

Persistent // Long-lasting.

DOIs are identifiers!

DOI is an acronym for:

Digital
Object
Identifier

DOIs are used for articles, datasets, issues, journals, galleys, preprints, theses, proceedings, monographs, reports, standards... "publications", basically (they can be used on basically, anything though).

Identifiers

An identifier is a unique string of characters assigned to something, someplace, or someone that can be used to identify it:

social insurance number,
driver's license number,
medicare number,
license plate number,
student number.

We are assigned identifiers all the time. We (ideally) carry "ID".

Identifiers

Identifiers typically refer to physical objects and are often created/managed locally. They're useful for record-keeping and data retrieval/searchability. They're useful for disambiguation, too!

UNB student ID is only a useful label for UNB students.
Social insurance numbers are provided federally.
Medicare numbers are provided provincially.
A license plate is only a label for a current, registered car.

There is more than one Mike Nason in Canada, but only one of them has my social insurance number (I hope).

PIDs, obviously, share the same benefits. A DOI is good for disambiguation, data retrieval, searchability in the same way that a social insurance number is. Like if, uhh, every article published had its own little tiny registration with a government.

We've scratched the surface a bit on what a DOI does, but URL storage and redirection is just one benefit for one kind of PID.

Identifiers

**Ok, so what about persistence?**

Persistent identifiers

Persistent identifiers most frequently refer to digital things. Traditionally, we share or locate digital things using a link (a URL).

URL // uniform resource locator
(https://www.example.com/index.html)

We know that urls break all the time, for lots of different reasons.

Persistent identifiers

A URL can tell you where something was when you read it (or, when you cited it). If you bookmark that URL or put it in print, you're assuming that link will still work later. This is not guaranteed!

But, as we discussed earlier, using DOIs I can update the location if the content moves. I can provide a persistent link to a record that contains a URL. As long as someone has the DOI, and the work registered metadata is up-to-date, I can get to the content.

The ID is persistent. Where it directs me may change.
A DOI is persistent. Where the DOI resolves may change.

An example

Imagine finding the citation for this work in a bibliography... which of these two will be more useful if the content moves from the website it is currently on?

Smiraglia, R. (2005). Metadata: A Cataloger's Primer (1st ed.). Routledge. https://www.taylorfrancis.com/books/mono/10.4324/9780203051238/metadata-richard-smiraglia

Smiraglia, R. (2005). Metadata: A Cataloger's Primer (1st ed.). Routledge. https://doi.org/10.4324/9780203051238

If I move my journal to a new web domain, I don't want every citation that exists to have an old URL.

**Instead, the DOI works as a stand-in that, if updated, will not only resolve to the new location but also contain all it's metadata.**

So long as the service persists, any item with a DOI should be locatable.

What about PIDs for things that aren't publications?

ORCiD!

ORCiD

ORCiD stands for "Open Researcher and Contributor ID"

ORCiD is also the name of the not-for-profit organization that provides ORCiD IDs, maintains the service, and develops the website and API.

If you're the kind of person who is bothered when people say "pin number", you'll hate ORCiD. No one says "ORC IDs".

What is an ORCiD?

We typically call them "ORCiD ids" or "ORCiDs"

ORCiD IDs

ORCiD IDs are another kind of persistent identifier.

ORCiD IDs

First and foremost, ORCiD IDs help consistently and properly identify the authors of works, no matter what their name is, was, or will be.

Nearly every publisher can take an ORCiD ID as metadata associated with a publication.

And! ORCiDs are included as metadata in DOIs! This means your identity in publication metadata can be unambiguous.

For example

I might write my own name as:

Mike Nason
Michael Nason
Michael Thomas William Nason
M. Nason
mnason
ahemnason

And! There may be more than one of any of these! The more variations and folks with the same name there are, the harder it is to find the stuff I've done. A PID for people would make attribution and discovery easier.

This for sure is not me.

Indulge me for a second and think about some rules we might assume about names.

For example, many folks would be likely to assume that everyone has a "first name" and a "last name".

Are those presumptions accurate?

Here's some presumptions!

People have exactly one canonical full name.
People have exactly one full name which they go by.
People’s names fit within a certain defined amount of space.
People’s names do not change.
People’s names change, but only at a certain enumerated set of events.

People’s names are written in ASCII.
People’s names are written in any single character set.
People’s names are case-sensitive.
People’s names are case-insensitive.
People’s names sometimes have prefixes or suffixes, but you can safely ignore those.

McKenzie, P. (n.d.). Falsehoods Programmers Believe About Names | Kalzumeus Software. Retrieved February 13, 2024, from https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/

Here's some presumptions!

People’s names are globally unique.
People’s names are almost globally unique.
Alright alright but surely people’s names are diverse enough such that no million people share the same name.
My system will never have to deal with names from China.
Or Japan. Or Korea.

Two different systems containing data about the same person will use the same name for that person.
Two different data entry operators, given a person’s name, will by necessity enter bitwise equivalent strings on any single system, if the system is well-designed.

McKenzie, P. (n.d.). Falsehoods Programmers Believe About Names | Kalzumeus Software. Retrieved February 13, 2024, from https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/

Names are cool and all. But they're not super useful to identify someone in a crowd. When I went to high school, people would yell, "hey, Mike", and no less than 8 guys would turn around.

And this is with a name that, broadly, fits western naming conventions that match expectations by major publishers.

And, Mike Nason is a pretty straightforward name!

Now, imagine my name was:
Alejandro Casas Niño de Rivera

Mike Nason
Michael Nason
Michael Thomas William Nason
M. Nason
mnason
ahemnason

https://orcid.org/0000-0001-5527-8489

👈

If information about me changes, my ORCiD will still be the same. It doesn't matter where I work, how my identity might change, what differences exist culturally in the places I might publish...

Think of an ORCiD as a more feature-rich version of a "student ID" but for your entire academic career.

ORCiD also provides users with what's known as an ORCiD profile. These function as a sort of online CV where your employment, education, funding, works, and service are listed.

When you hear someone talk about a scholar profile or a researcher profile, they are probably talking about either ORCiD, Scopus ID, Researcher ID, or Google Scholar (but they might be talking about something else entirely).

We're going to come back to ORCiD in a bit, but while we're here I'll provide some links to a few other talks I've done about this.

AND

UNB Libraries Research Booster 1

video | deck

(bonus) CRKN PIDs Series: Object Identifiers: Use Cases for Librarians and Data Professionals

video | deck

And so...

Persistent identifiers

Pids make things easier to find, track, share, and access!

If my ORCiD ID is present as metadata in the DOIs of the work I publish, I can pull my publication record easily and add it to my ORCiD profile.

If my articles have DOIs, I can provide persistent links to their most recent location, which will ensure ease of access and citation.

If a funding agency can pull metadata from my ORCiD profile, they can acquire all of my publication metadata without me having to fill out a pile of forms.

Persistent identifiers

PIDs are unique, unchanging, identifiers representing objects (digital or otherwise) that can direct a user, unambiguously, to that object's current location or status, and provide additional information/metadata.

But, a PID cannot just do this unilaterally.

No PID is an island!

**PIDs require a third party**

Often, folks use the phrase "minting a DOI" to describe the assignment of a DOI to a work. I see this a lot; a journal editor might say to me, "I made all these DOIs, but they don't work! I just get an error!"

A publisher can "mint" PIDs and provide them to you, but they need a third party to be at all useful.

To work, a PID needs to be registered with a PID registration agency.

What is a registration agency?

Registration agencies

Persistent identifiers are managed by registration agencies (typically international not-for-profits) that store records/metadata, facilitate resolution requests, and may or may not offer other services based on membership. They do much of this through APIs.

There are a lot of registration agencies!

Registration agencies

It's important to know that registration agencies differ in mandate, governance, scope, service, supported objects, membership terms, and feature set.

They also, often, work together and share data.

Let's review the field!

PIDs for scholarly works

Crossref (DOI)

Most scholarly publishers are Crossref members. At the time I wrote this (Feb 13th), Crossref had 155,639,301 DOIs registered with their service.

Crossref are a big deal.

articles
proceedings
monographs
*datasets
funding agencies
grants
reports
standards
preprints

PIDs for scholarly works

Datacite (DOI)

While some scholarly publishers use Datacite for article DOIs, it is much more commonly used in data/institutional/disciplinary repositories. DataCite and Crossref work together to connect research data to publications.

software
datasets
collections
audio/visual
event
model
*publications

PIDs for researchers

ORCID (ISNE)
Scopus ID
WoS Researcher ID

ORCiD are the go-to here, with Scopus and WoS offerings both restricted to publications present on those platforms. However, these services can share data between them.

researchers

PIDs for organizations

ROR
GRID
ISNE

There are good odds you'll never need to know what the ROR ID for UNB is. The predominant use-case for organizational IDs is in strengthening connections between records and institutions.

organizations

A quick example re: ROR

We write UNB as:

UNB
University of New Brunswick
UNBF / UNBSJ
UNB Fredericton
University of New Brunswick Saint John

https://ror.org/05nkf0n29

Registration agencies

Registration agencies provide metadata schema through which users can describe the objects they are registering PIDs for.

As you can imagine, you'd describe a person differently than you'd describe a dataset, or a journal article, or an organization. Even when agencies use the same type of PID (like the DOI), the schema they use may vary.

For example

Let's look at the registered metadata (in XML format) for a DOI:
10.4138/atlgeo.2022.008

<crossref_result version="3.0" xsi:schemaLocation="http://www.crossref.org/qrschema/3.0 http://www.crossref.org/schemas/crossref_query_output3.0.xsd">
<query_result>
<head>
</head>
<body>
<query status="resolved">
<doi type="journal_article">10.4138/atlgeo.2022.008</doi>
<crm-item name="publisher-name" type="string">University of New Brunswick Libraries - UNB</crm-item>
<crm-item name="prefix-name" type="string">Atlantic Geology</crm-item>
<crm-item name="member-id" type="number">12607</crm-item>
<crm-item name="citation-id" type="number">140103075</crm-item>
<crm-item name="journal-id" type="number">466310</crm-item>
<crm-item name="deposit-timestamp" type="number">1661345059</crm-item>
<crm-item name="owner-prefix" type="string">10.4138</crm-item>
<crm-item name="last-update" type="date">2022-08-24T12:44:54Z</crm-item>
<crm-item name="created" type="date">2022-08-24T12:44:21Z</crm-item>
<crm-item name="citedby-count" type="number">5</crm-item>
<doi_record>
<crossref xsi:schemaLocation="http://www.crossref.org/xschema/1.1 http://doi.crossref.org/schemas/unixref1.1.xsd">
<journal>
<journal_metadata>
<full_title>Atlantic Geoscience</full_title>
<abbrev_title>atlgeo</abbrev_title>
<issn media_type="electronic">2564-2987</issn>
</journal_metadata>
<journal_issue>
<publication_date media_type="online">
<month>03</month>
<day>30</day>
<year>2022</year>
</publication_date>
<journal_volume>
<volume>58</volume>
</journal_volume>
</journal_issue>
<journal_article publication_type="full_text" metadata_distribution_opts="any">
<titles>
<title>
Revised stratigraphy in the eastern Meguma terrane, Nova Scotia, Canada, and variations in whole-rock chemical and Sm–Nd isotopic compositions of the Goldenville and Halifax groups
</title>
</titles>
<contributors>
<person_name contributor_role="author" sequence="first" language="en">
<given_name>Sandra M.</given_name>
<surname>Barr</surname>
<alt-name>
<name language="fr">
<surname>Barr</surname>
<given_name>Sandra M.</given_name>
</name>
</alt-name>
</person_name>
<person_name contributor_role="author" sequence="additional" language="en">
<given_name>Chris E.</given_name>
<surname>White</surname>
<alt-name>
<name language="fr">
<surname>White</surname>
<given_name>Chris E.</given_name>
</name>
</alt-name>
</person_name>
<person_name contributor_role="author" sequence="additional" language="en">
<given_name>Christian</given_name>
<surname>Pin</surname>
<alt-name>
<name language="fr">
<surname>Pin</surname>
<given_name>Christian</given_name>
</name>
</alt-name>
</person_name>
</contributors>
<jats:abstract>
<jats:p>
As a result of new geological mapping, the Goldenville and Halifax groups in the eastern Meguma terrane have been divided into formations. They have a total stratigraphic thickness of about 7750 m and correspond to only the upper half of the Goldenville Group and lower half of the Halifax Group in the northwestern and southeastern areas of the terrane. The revised stratigraphy combined with compiled and new whole-rock major and trace element and Sm–Nd isotopic analyses enable more detailed documentation of the chemical changes with stratigraphy that were demonstrated in previous studies. Based on chemical compositions, the protolith compositions of the analysed samples range from lithic arenite to wacke to shale. Major and trace element characteristics are consistent with deposition in an active continental margin, basins associated with island arcs, or most likely at a passive continental margin with volcanic rocks in the source area. Chemical compositions show a scattered but overall increasing abundance of lithophile elements such as La and Th with stratigraphic position. Epsilon Nd(t) values become increasingly negative up-section, and depleted mantle model ages become increasingly older. The data are consistent with increased mixing between sediments  derived from Mesoproterozoic upper crustal sources and sediments derived from a magmatic arc. These data are consistent with published detrital zircon patterns which show increasing amounts of ca. 2 Ga zircon with decreasing age, and with a source area comprising a Pan-African (800–540 Ma) volcanic arc and/or active margin magmatism and mainly Eburnean crust, most likely in the West African craton.
</jats:p>
</jats:abstract>
<publication_date media_type="online">
<month>07</month>
<day>01</day>
<year>2022</year>
</publication_date>
<pages>
<first_page>193</first_page>
<last_page>213</last_page>
</pages>
<fr:program name="fundref"/>
<doi_data>
<doi>10.4138/atlgeo.2022.008</doi>
<resource>
https://journals.lib.unb.ca/index.php/ag/article/view/32794
</resource>
<collection property="crawler-based">
<item crawler="iParadigms">
<resource>
https://journals.lib.unb.ca/index.php/ag/article/download/32794/1882528218
</resource>
</item>
</collection>
<collection property="text-mining">
<item>
<resource mime_type="application/pdf">
https://journals.lib.unb.ca/index.php/ag/article/download/32794/1882528218
</resource>
</item>
<item>
<resource mime_type="application/vnd.openxmlformats-officedocument.spreadsheetml.sheet">
https://journals.lib.unb.ca/index.php/ag/article/download/32794/1882528216
</resource>
</item>
</collection>
</doi_data>
<citation_list>
<citation key="16815">
<unstructured_citation>
Arizona Laser Chroncenter 2010. Excel based tools: normalized age probability plots (2010). URL <https://sites.google.com/laserchron.org/arizonalaserchroncenter/home>, 20 February 2022.
</unstructured_citation>
</citation>
<citation key="16816">
<doi provider="crossref">10.1130/0091-7613(1987)15<893:UAAOCA>2.0.CO;2</doi>
<unstructured_citation>
Arndt, N.T. and Goldstein, S.L. 1987. Use and abuse of crust-formation ages. Geology 15, pp. 893–895. https://doi.org/10.1130/0091-7613(1987)15<893:UAAOCA>2.0.CO;2
</unstructured_citation>
</citation>
<citation key="16817">
<doi provider="crossref">10.1139/e11-070</doi>
<unstructured_citation>
Barr, S.M., Hamilton, M.A., Samson, S.D., Satkoski, A., and White, C.E. 2012. Provenance variations in northern Appalachian Avalonia based on detrital zircon age patterns in Ediacaran and Cambrian sedimentary rocks, New Brunswick and Nova Scotia, Canada. Canadian Journal of Earth Sciences, 49, pp. 533–546. https://doi.org/10.1139/e11-070
</unstructured_citation>
</citation>
<citation key="16818">
<doi provider="crossref">10.1007/BF00375292</doi>
<unstructured_citation>
Bhatia, M.R. and Crook, K.A.W. 1986. Trace element characteristics of graywackes and tectonic setting discrimination of sedimentary basins. Contributions to Mineralogy and Petrology, 92, pp. 181–193. https://doi.org/10.1007/BF00375292
</unstructured_citation>
</citation>
<citation key="16819">
<doi provider="crossref">10.1139/cjes-2021-0097</doi>
<unstructured_citation>
Bickerton, L., Kontak, D.J., Murphy, J.B., Kellett, D.A., Samson, I.M., Marsh, J.H., Dunning, G., and Stern, R. 2022. Petrochronology constrains the generation and assembly of the South Mountain Batholith, Nova Scotia, Canada: Implications for metallogenic inheritance. Canadian Journal of Earth Sciences. Preprint. https://doi.org/10.1139/cjes-2021-0097
</unstructured_citation>
</citation>
<citation key="16820">
<unstructured_citation>
Boggs, S., Jr., 2001, Principles of Sedimentology and Stratigraphy (3rd edition): Upper Saddle River, New Jersey, Prentice Hall, 726p.
</unstructured_citation>
</citation>
<citation key="16821">
<doi provider="crossref">10.1139/e85-008</doi>
<unstructured_citation>
Clarke, D.B. and Halliday, A.N. 1985. Sm/Nd isotopic investigation of the age and origin of the Meguma Zone metasedimentary rocks. Canadian Journal of Earth Sciences, 22, pp.102–107. https://doi.org/10.1139/e85-008
</unstructured_citation>
</citation>
<citation key="16822">
<doi provider="crossref">10.1016/0168-9622(88)90018-8</doi>
<unstructured_citation>
Clarke, D.B., Halliday, A.N., and Hamilton, P.J. 1988. Neodymium and strontium isotopic constraints on the origin of the peraluminous granitoids of the South Mountain Batholith, Nova Scotia, Canada. Chemical Geology. Isotope Geoscience Section, 73, pp.15–24. https://doi.org/10.1016/0168-9622(88)90018-8
</unstructured_citation>
</citation>
<citation key="16823">
<doi provider="crossref">10.1139/e93-033</doi>
<unstructured_citation>
Clarke, D. B., Chatterjee, A. K., and Giles, P. S. 1993. Petrochemistry, tectonic history, and Sr-Nd systematics of the Liscomb Complex, Meguma Lithotectonic Zone, Nova Scotia. Canadian Journal of Earth Sciences, 30, pp. 449–464. https://doi.org/10.1139/e93-033
</unstructured_citation>
</citation>
<citation key="16824">
<doi provider="crossref">10.1130/0-8137-1191-6.107</doi>
<unstructured_citation>
Clarke, D.B., MacDonald, M.A., and Tate, M.C. 1997. Late Devonian mafic-felsic magmatism in the Meguma Zone, Nova Scotia. In The nature of magmatism in the Appalachian orogen. Edited by A.K. Sinha, J.F. Whalen, and J.P. Hogan. Geological Society of America Memoir, 191, pp. 107–127. https://doi.org/10.1130/0-8137-1191-6.107
</unstructured_citation>
</citation>
<citation key="16825">
<doi provider="crossref">10.1139/e99-124</doi>
<unstructured_citation>
Clarke, D.B., Fallon, R., and Heaman, L.M. 2000. Interaction among upper crustal, lower crustal, and mantle materials in the Port Mouton pluton, Meguma Lithotectonic Zone, southwest Nova Scotia. Canadian Journal of Earth Sciences, 37, pp. 579–600. https://doi.org/10.1139/e99-124
</unstructured_citation>
</citation>
<citation key="16826">
<doi provider="crossref">10.1029/2004TC001752</doi>
<unstructured_citation>
Culshaw, N.G. and Lee, S.K.Y. 2006. The Acadian Fold Belt in the Meguma Terrane, Nova Scotia: Cross sections, fold mechanisms and tectonic implications. Tectonics, 25. https://doi.org/10.1029/2004TC001752
</unstructured_citation>
</citation>
<citation key="16827">
<doi provider="crossref">10.1139/e17-068</doi>
<unstructured_citation>
Culshaw, N. and Liesa, M. 1997. Alleghanian reactivation of the Acadian fold belt, Meguma Zone, southwest Nova Scotia. Canadian Journal of Earth Sciences, 34, pp. 833–847. https://doi.org/10.1139/e17-068
</unstructured_citation>
</citation>
<citation key="16828">
<doi provider="crossref">10.1139/e17-069</doi>
<unstructured_citation>
Culshaw, N. and Reynolds, P. 1997. 40Ar/39Ar age of shear zones in the southwest Meguma Zone between Yarmouth and Meteghan, Nova Scotia. Canadian Journal of Earth Sciences, 34, 848–853. https://doi.org/10.1139/e17-069
</unstructured_citation>
</citation>
<citation key="16829">
<doi provider="crossref">10.4095/120057</doi>
<unstructured_citation>
Cumming, L.M. 1985. A Halifax slate graptolite locality, Nova Scotia. Geological Survey of Canada, Current Research, part A., Paper 85-1A, pp. 215–221. https://doi.org/10.4095/120057
</unstructured_citation>
</citation>
<citation key="16830">
<doi provider="crossref">10.1016/S0024-4937(98)00051-6</doi>
<unstructured_citation>
Currie, K.L., Whalen, J.B., Davis, W.J., Longstaffe, F.J., and Cousens, B.L. 1998. Geochemical evolution of peraluminous plutons in southern Nova Scotia, Canada – a pegmatite-poor suite; Lithos, 44, pp. 117–140. https://doi.org/10.1016/S0024-4937(98)00051-6
</unstructured_citation>
</citation>
<citation key="16831">
<doi provider="crossref">10.1038/291193a0</doi>
<unstructured_citation>
DePaolo, D. J. 1981. Neodymium isotopes in the Colorado Front Range and crust-mantle evolution in the Proterozoic. Nature, 291, pp. 193–196. https://doi.org/10.1038/291193a0
</unstructured_citation>
</citation>
<citation key="16832">
<doi provider="crossref">10.1029/90JB02219</doi>
<unstructured_citation>
DePaolo, D. J., Linn, A. M., and Schubert, G. 1991. The continental crustal age distribution: Methods of determining mantle separation ages from Sm–Nd isotopic data and application to the southwestern United States: Journal of Geophysical Research, 96, pp. 2071–2088. https://doi.org/10.1029/90JB02219
</unstructured_citation>
</citation>
<citation key="16833">
<doi provider="crossref">10.1139/E10-086</doi>
<unstructured_citation>
Gingras, M.K., Waldron, J.W.F., White, C.E., and Barr, S.M. 2011. The evolutionary significance of a lower Cambrian trace fossil assemblage from the Meguma terrane, Nova Scotia. Canadian Journal of Earth Sciences, 48, pp. 71–85. https://doi.org/10.1139/E10-086
</unstructured_citation>
</citation>
<citation key="16834">
<unstructured_citation>
Henderson, B.J. 2016. What do epsilon hafnium isotopic arrays tell us about Wilson cycle tectonics? Implications for the type area in the Appalachian-Variscan Orogen. Unpublished Ph.D. thesis, Geology and Geophysics, School of Physical Sciences, University of Adelaide, Australia, 332p.
</unstructured_citation>
</citation>
<citation key="16835">
<doi provider="crossref">10.4095/120535</doi>
<unstructured_citation>
Henderson, J. R. 1986. Geology, Ecum Secum area, Nova Scotia; Geological Survey of Canada, "A" Series Map 1648A, scale 1:50 000. https://doi.org/10.4095/120535
</unstructured_citation>
</citation>
<citation key="16836">
<doi provider="crossref">10.1306/212F8E77-2B24-11D7-8648000102C1865D</doi>
<unstructured_citation>
Herron, M.M. 1988, Geochemical classification of terrigenous sands from core or log data. Journal of Sedimentary Petrology, 58, pp. 820–829. https://doi.org/10.1306/212F8E77-2B24-11D7-8648000102C1865D
</unstructured_citation>
</citation>
<citation key="16837">
<doi provider="crossref">10.4095/221912</doi>
<unstructured_citation>
Hibbard, J.P., van Staal, C.R., Rankin, D., and Williams H. 2006. Lithotectonic map of the Appalachian orogen (north), Canada-United States of America. Geological Survey of Canada Map 02041A, 1 sheet, scale 1:1 500 000. https://doi.org/10.4095/221912
</unstructured_citation>
</citation>
<citation key="16838">
<doi provider="crossref">10.1130/2007.2433(14)</doi>
<unstructured_citation>
Hibbard, J.P., van Staal, C.R., and Miller, B.V. 2007. Links between Carolinia, Avalonia and Ganderia in the Appalachian peri-Gondwanan realm. In Whence the Mountains? Inquiries into the Evolution of Orogenic Systems: A Volume in Honor of Raymond A. Price. Edited by J.W. Sears, T.A. Harms, C.A. and Evenchick. Geological Society of America Special Paper 433, pp. 291–311. https://doi.org/10.1130/2007.2433(14)
</unstructured_citation>
</citation>
<citation key="16839">
<doi provider="crossref">10.1139/e98-081</doi>
<unstructured_citation>
Hicks, R.J., Jamieson, R.A., and Reynolds, P.H. 1999. Detrital and metamorphic 40Ar/39Ar ages from muscovite and whole-rock samples, Meguma Supergroup, southern Nova Scotia. Canadian Journal of Earth Sciences, 36, pp. 23–32. https://doi.org/10.1139/e98-081
</unstructured_citation>
</citation>
<citation key="16840">
<doi provider="crossref">10.4095/131924</doi>
<unstructured_citation>
Hill, J.D. 1991. Geology of the Forest Hill area; in Petrology, tectonic setting, and economic potential of peraluminous granitoid plutons in the Canso and Forest Hill areas, eastern Meguma Terrane, Nova Scotia. Geological Survey of Canada, Bulletin 383, 96p (includes 2 1:50 000-scale maps). https://doi.org/10.4095/131924
</unstructured_citation>
</citation>
<citation key="16841">
<unstructured_citation>
Horne, R.J. and Pelley, D. 2007. Geological transect of the Meguma terrane from Centre Musquodoboit to Tangier. In Mineral Resources Branch, Report of Activities 2006. Edited by D.R. MacDonald. Nova Scotia Department of Natural Resources, Report ME 2007-1, pp. 71–89.
</unstructured_citation>
</citation>
<citation key="16842">
<doi provider="crossref">10.1016/0040-1951(90)90287-I</doi>
<unstructured_citation>
Krogh, T.E. and Keppie, J.D. 1990. Age of detrital zircon and titanite in the Meguma Group, southern Nova Scotia, Canada: Clues to the origin of the Meguma Terrane. Tectonophysics, 177, pp. 307–323. https://doi.org/10.1016/0040-1951(90)90287-I
</unstructured_citation>
</citation>
<citation key="16843">
<doi provider="crossref">10.1111/j.1751-908X.2002.tb00884.x</doi>
<unstructured_citation>
Le Fèvre, B. and Pin, C. 2002. Determination of Zr, Hf, Th and U by isotope dilution and inductively coupled plasmaquadrupole mass spectrometry after concomitant separation using extraction chromatography. Geostandards and Geoanalytical Research, 26, pp. 161–70. https://doi.org/10.1111/j.1751-908X.2002.tb00884.x
</unstructured_citation>
</citation>
<citation key="16844">
<doi provider="crossref">10.1139/cjes-2017-0086</doi>
<unstructured_citation>
Letsch, D., El Houicha, M., von Quadt, A., and Winkler, W. 2018. A missing link in the peri-Gondwanan terrane collage: the Precambrian basement of the Moroccan Meseta and its lower Paleozoic cover. Canadian Journal of Earth Sciences, 55, pp. 33–51. https://doi.org/10.1139/cjes-2017-0086
</unstructured_citation>
</citation>
<citation key="16845">
<doi provider="crossref">10.2475/02.2010.03</doi>
<unstructured_citation>
Li, C. and Yang, S. 2010. Is Chemical Index of Alteration (CIA) a reliable proxy for chemical weathering in global drainage basins? American Journal of Science, 310, pp. 111–127. https://doi.org/10.2475/02.2010.03
</unstructured_citation>
</citation>
<citation key="16846">
<doi provider="crossref">10.1016/j.precamres.2013.08.007</doi>
<unstructured_citation>
Linnemann, U., Gerdes, A., Hofmann, M., and Marko, L. 2014. The Cadomian orogen: Neoproterozoic to Early Cambrian crustal growth and orogenic zoning along the periphery of the West African Craton—constraints from U–Pb zircon ages and Hf isotopes (Schwarzburg Antiform, Germany). Precambrian Research, 244, pp. 236–278. https://doi.org/10.1016/j.precamres.2013.08.007
</unstructured_citation>
</citation>
<citation key="16847">
<doi provider="crossref">10.1139/e01-074</doi>
<unstructured_citation>
MacDonald, L.A., Barr, S.M., White, C.E., and Ketchum, J.W.F. 2002. Petrology, age, and tectonic setting of the White Rock Formation, Meguma terrane, Nova Scotia: evidence for Silurian continental rifting. Canadian Journal of Earth Sciences, 39, pp. 259–277. https://doi.org/10.1139/e01-074
</unstructured_citation>
</citation>
<citation key="16848">
<unstructured_citation>
Mahoney, K.L. 1996. The contact metamorphic aureole of the South Mountain Batholith, Nova Scotia. Unpublished M.Sc. thesis, Acadia University, Wolfville, Nova Scotia, 153 p.
</unstructured_citation>
</citation>
<citation key="16849">
<doi provider="crossref">10.1086/648222</doi>
<unstructured_citation>
McLennan, S. M. 1993, Weathering and global denudation: The Journal of Geology, 101, pp. 295–303. https://doi.org/10.1086/648222
</unstructured_citation>
</citation>
<citation key="16850">
<doi provider="crossref">10.1016/0016-7037(90)90269-Q</doi>
<unstructured_citation>
McLennan, S.M., Taylor, S.R., McCulloch, M.T., and Maynard, J.B. 1990. Geochemical and Nd-Sr isotopic composition of deep-sea turbidites: Crustal evolution and plate tectonic associations. Geochimica et Cosmochimica Acta, 54, pp. 2015–2050. https://doi.org/10.1016/0016-7037(90)90269-Q
</unstructured_citation>
</citation>
<citation key="16851">
<doi provider="crossref">10.1016/0168-9622(88)90013-9</doi>
<unstructured_citation>
Muecke, G.K., Elias, P., and Reynolds, P.H. 1988. Hercynian/Alleghanian overprinting of an Acadian Terrane: 40Ar/39Ar studies in the Meguma Zone, Nova Scotia, Canada. Chemical Geology, 73, pp. 153–167. https://doi.org/10.1016/0168-9622(88)90013-9
</unstructured_citation>
</citation>
<citation key="16852">
<doi provider="crossref">10.1130/G20351.1</doi>
<unstructured_citation>
Murphy, J.B., Fernández-Suárez, J., Keppie, J.D., and Jeffries, T.E. 2004. Contiguous rather than discrete Paleozoic histories for the Avalon and Meguma Terranes based on detrital zircon data: Geology, 32, pp. 585–588. https://doi.org/10.1130/G20351.1
</unstructured_citation>
</citation>
<citation key="16853">
<doi provider="crossref">10.1016/j.jsg.2010.11.012</doi>
<unstructured_citation>
Murphy, J. B., Waldron, J. W. F., Kontak, D. J., Pe-Piper, G., and Piper, D. J. W. 2011. Minas fault zone: Late Paleozoic history of an intra-continental orogenic transform fault in the Canadian Appalachians. Journal of Structural Geology, 33, pp. 312–328. https://doi.org/10.1016/j.jsg.2010.11.012
</unstructured_citation>
</citation>
<citation key="16854">
<doi provider="crossref">10.1016/j.gr.2009.08.001</doi>
<unstructured_citation>
Nance R.D., Gutiérrez-Alonso G., Keppie J.D., Linnemann U., Murphy J.B., Quesada C., Strachan R.A., and Woodcock N.H. 2010. Evolution of the Rheic Ocean. Gondwana Research, 17, pp. 194–222. https://doi.org/10.1016/j.gr.2009.08.001
</unstructured_citation>
</citation>
<citation key="16855">
<doi provider="crossref">10.1038/299715a0</doi>
<unstructured_citation>
Nesbitt, H.W. and Young, G.M. 1982. Early Proterozoic climates and plate motions inferred from major element chemistry of lutites. Nature, 299, pp. 715–717. https://doi.org/10.1038/299715a0
</unstructured_citation>
</citation>
<citation key="16856">
<doi provider="crossref">10.1016/S0003-2670(96)00499-0</doi>
<unstructured_citation>
Pin C. and Santos J. F. 1997. Sequential separation of light rare-earth elements, thorium and uranium by miniaturized extraction chromatography: application to isotopic analyses of silicate rocks. Analytica Chimica Acta, 339, pp. 79–89. https://doi.org/10.1016/S0003-2670(96)00499-0
</unstructured_citation>
</citation>
<citation key="16857">
<doi provider="crossref">10.4138/atlgeol.2015.003</doi>
<unstructured_citation>
Pothier, H.D., Waldron, J.W.F., White, C.E., Dufrane, A.S., and Jamieson, R.A. 2015. Stratigraphy, provenance and tectonic setting of the Lumsden Dam and Bluestone Quarry formations (Lower Ordovician), Halifax Group, Nova Scotia, Canada. Atlantic Geology, 51, pp. 51–83. https://doi.org/10.4138/atlgeol.2015.003
</unstructured_citation>
</citation>
<citation key="16858">
<doi provider="crossref">10.1139/e91-164</doi>
<unstructured_citation>
Pratt, B.R. and Waldron, J.W.F. 1991. A Middle Cambrian trilobite faunule from the Meguma Group of Nova Scotia. Canadian Journal of Earth Sciences, 28, pp. 1843–1853. https://doi.org/10.1139/e91-164
</unstructured_citation>
</citation>
<citation key="16859">
<unstructured_citation>
Raeside, R.P. and Jamieson, R.A. 1992. Low-pressure metamorphism of the Meguma terrane, Nova Scotia. Field excursion C-5, GAC-MAC field trip guide, 25 p.
</unstructured_citation>
</citation>
<citation key="16860">
<doi provider="crossref">10.1139/e2012-022</doi>
<unstructured_citation>
Reynolds, P.H., White, C.E., Barr, S.M., and Muir, C.M. 2012. 40Ar/39Ar ages for detrital white mica in Meguma terrane, Nova Scotia, Canada: implications for provenance of the Goldenville and Halifax groups. Canadian Journal of Earth Sciences, 49, pp. 781–795. https://doi.org/10.1139/e2012-022
</unstructured_citation>
</citation>
<citation key="16861">
<doi provider="crossref">10.1080/11035899801202119</doi>
<unstructured_citation>
Robinson, P., Tucker, R.D., Bradley, D., Berry IV, H.N., and Osberg, P.H. 1998. Paleozoic orogens in New England, USA. GFF, 120, pp. 119–148. https://doi.org/10.1080/11035899801202119
</unstructured_citation>
</citation>
<citation key="16862">
<doi provider="crossref">10.1139/e10-092</doi>
<unstructured_citation>
Romer, R.L., Kirsch, M., and Kroner, U. 2011. Geochemical signature of Ordovician Mn-rich sedimentary rocks on the Avalonian shelf: Canadian Journal of Earth Sciences, 48, pp. 703–718. https://doi.org/10.1139/e10-092
</unstructured_citation>
</citation>
<citation key="16863">
<doi provider="crossref">10.1086/629071</doi>
<unstructured_citation>
Roser, B.P. and Korsch, R.J. 1986. Determination of tectonic setting of sandstone-mudstone suites using SiO2 content and K2O/Na2O ratio. Journal of Geology, 94, pp. 635–650. https://doi.org/10.1086/629071
</unstructured_citation>
</citation>
<citation key="16864">
<unstructured_citation>
Ryan, R.J., Fox, D., Horne, R.J., Corey, M.C., and Smith, P.K. 1996. Preliminary stratigraphy of the Meguma Group in central Nova Scotia. In Minerals and Energy Branch Report of Activities 1995. Edited by D.R. MacDonald. Nova Scotia Department of Natural Resources Report ME 1996-001, pp. 27–34.
</unstructured_citation>
</citation>
<citation key="16865">
<doi provider="crossref">10.1016/j.precamres.2008.06.009</doi>
<unstructured_citation>
Santos, J.O.S., Rizzotto, G.J., Potter, P.E., McNaughton, N.J., Matos, R.S., Hartmann, L.A., Chemale, F., Jr.; and Quadros, M.E.S. 2008. Age and autochthonous evolution of the Sunsas Orogen in West Amazon Craton based on mapping and U–Pb geochronology. Precambrian Research, 165, pp. 120–152. https://doi.org/10.1016/j.precamres.2008.06.009
</unstructured_citation>
</citation>
<citation key="16866">
<doi provider="crossref">10.1086/649818</doi>
<unstructured_citation>
Satkoski, A.M., Barr, S.M., and Samson, S.D. 2010. Provenance of late Neoproterozoic and Cambrian sediments in Avalonia: Constraints from detrital zircon ages and Sm–Nd isotopic compositions in southern New Brunswick, Canada. Journal of Geology, 118, pp. 187–200. https://doi.org/10.1086/649818
</unstructured_citation>
</citation>
<citation key="16867">
<doi provider="crossref">10.1139/e71-113</doi>
<unstructured_citation>
Schenk, P.E. 1971. Southern Atlantic Canada, northwestern Africa and continental drift. Canadian Journal of Earth Sciences, 8, pp. 1218–1251. https://doi.org/10.1139/e71-113
</unstructured_citation>
</citation>
<citation key="16868">
<unstructured_citation>
Schenk, P.E. 1981. The Meguma Zone of Nova Scotia – a remnant of Western Europe, South America, or Africa? In Geology of North Atlantic borderlands. Edited by J.M. Kerr, A.J. Ferguson, and L.C. Machan. Canadian Society of Petroleum Geologists Memoir, 7, pp.119–148.
</unstructured_citation>
</citation>
<citation key="16869">
<doi provider="crossref">10.1130/0016-7606(1991)103<0512:EASLCO>2.3.CO;2</doi>
<unstructured_citation>
Schenk, P.E. 1991. Events and sea level changes on Gondwana's margin: the Meguma Zone (Cambrian to Devonian) of Nova Scotia, Canada. Geological Society of America Bulletin, 103, pp. 512–521. https://doi.org/10.1130/0016-7606(1991)103<0512:EASLCO>2.3.CO;2
</unstructured_citation>
</citation>
<citation key="16870">
<unstructured_citation>
Schenk, P.E. 1995. Meguma Zone. In Geology of the Appalachian-Caledonian Orogen in Canada and Greenland. Edited by H. Williams. Geological Survey of Canada, Geology of Canada, 6, pp. 261–277.
</unstructured_citation>
</citation>
<citation key="16871">
<doi provider="crossref">10.1130/0016-7606(1997)109<0395:SSAPOG>2.3.CO;2</doi>
<unstructured_citation>
Schenk, P.E. 1997. Sequence stratigraphy and provenance on Gondwana’s margin: the Meguma Zone (Cambrian to Devonian) of Nova Scotia, Canada: Geological Society of America Bulletin, 109, pp. 395–409. https://doi.org/10.1130/0016-7606(1997)109<0395:SSAPOG>2.3.CO;2
</unstructured_citation>
</citation>
<citation key="16872">
<doi provider="crossref">10.1016/S0009-2541(00)00198-4</doi>
<unstructured_citation>
Tanaka, T., Togashi, S., Kamioka, H., Amakawa, H., Kagami, H., Hamamoto, T., Yuhara, M., Orihashi, Y.,Yoneda, S., Shimizu, H.,Kunimaru, T., Takahashi, K.,Yanagi, T.,Nakano, T., Fujimaki, H., Shinjo, R.,Asahara,Y.,Tanimizu,M. and Dragusanu, C. 2000. JNdi-1: a neodymium isotopic reference in consistency with LaJolla neodymium. Chemical Geology, 168, pp. 279–281. https://doi.org/10.1016/S0009-2541(00)00198-4
</unstructured_citation>
</citation>
<citation key="16873">
<doi provider="crossref">10.1130/GES01525.1</doi>
<unstructured_citation>
Thomas, W.A., Gehrels, G.E., Greb, S.F., Nadon, G.C., Satkoski, A.M., and Romero, M.C. 2017. Detrital zircons and sediment dispersal in the Appalachian foreland: Geosphere, 13, pp. 2206–2230. https://doi.org/10.1130/GES01525.1
</unstructured_citation>
</citation>
<citation key="16874">
<doi provider="crossref">10.1016/S0301-9268(00)00149-2</doi>
<unstructured_citation>
Toteu, S. F., Van Schmus, W. R., Penaye, J., and Michard, A. 2001. New U–Pb and Sm–Nd data from northcentral Cameroon and its bearing on the pre-Pan African history of central Africa. Precambrian Research, 108, pp. 45–73. https://doi.org/10.1016/S0301-9268(00)00149-2
</unstructured_citation>
</citation>
<citation key="16875">
<doi provider="crossref">10.1016/S0016-7037(03)00027-9</doi>
<unstructured_citation>
Ugidos, J.M., Valladares, M.I., Barba P., and Ellam R.M. 2003. The Upper Neoproterozoic-Lower Cambrian of the Central Iberian Zone, Spain: chemical and isotopic (Sm–Nd) evidence that the sedimentary succession records an inverted stratigraphy of its source. Geochimica et Cosmochimica Acta, 67, pp. 2615–2629. https://doi.org/10.1016/S0016-7037(03)00027-9
</unstructured_citation>
</citation>
<citation key="16876">
<doi provider="crossref">10.1130/2010.2466(01)</doi>
<unstructured_citation>
van Staal, C.R. and Hatcher, R.D. Jr. 2010. Global setting of Ordovician orogenesis. In The Ordovician Earth System. Edited by S.C. Finney and W.B.N. Berry. Geological Society of America, Special Paper 466, pp. 1–11. https://doi.org/10.1130/2010.2466(01)
</unstructured_citation>
</citation>
<citation key="16877">
<unstructured_citation>
van Staal, C.R. and Barr, S.M. 2012. Lithospheric architecture and tectonic evolution of the Canadian Appalachians. In Tectonic Styles in Canada Revisited: the LITHOPROBE perspective. Edited by J.A. Percival, F.A. Cook, and R.M. Clowes. Geological Association of Canada Special Paper 49, pp. 41–95.
</unstructured_citation>
</citation>
<citation key="16878">
<doi provider="crossref">10.1144/SP503-2020-23</doi>
<unstructured_citation>
van Staal, C.R., Barr, S.M., McCausland, P.J.A., Thompson, M.D., and White, C.E., 2021a, Tonian-Ediacaran tectonomagmatic evolution of West Avalonia and its Ediacaran-Early Cambrian interactions with Ganderia: An example of complex terrane transfer due to arc-arc collision? Geological Society of London Special Publication 503, pp. 143–167. https://doi.org/10.1144/SP503-2020-23
</unstructured_citation>
</citation>
<citation key="16879">
<doi provider="crossref">10.1016/j.gr.2021.05.025</doi>
<unstructured_citation>
van Staal, C.R., Barr, S.M., Waldron, J.W.F., Schofield, D.I., Zagorevski, A., and White, C.E. 2021b. Provenance and Paleozoic tectonic evolution of Ganderia and its relationships with Avalonia and Megumia in the Appalachian-Caledonide orogen. Gondwana Research, 98, pp. 212–243. https://doi.org/10.1016/j.gr.2021.05.025
</unstructured_citation>
</citation>
<citation key="16880">
<doi provider="crossref">10.1139/e92-087</doi>
<unstructured_citation>
Waldron, J.W.F. 1992. The Goldenville–Halifax transition, Mahone Bay, Nova Scotia: relative sea-level change in the Meguma source terrane. Canadian Journal of Earth Sciences, 29, pp. 1091–1105. https://doi.org/10.1139/e92-087
</unstructured_citation>
</citation>
<citation key="16881">
<doi provider="crossref">10.4095/120314</doi>
<unstructured_citation>
Waldron, J.W.F. and Jensen, L.R. 1985. Sedimentology of the Goldenville Formation, Eastern Shore, Nova Scotia. Geological Survey of Canada Paper 85-15, 31 p. https://doi.org/10.4095/120314
</unstructured_citation>
</citation>
<citation key="16882">
<doi provider="crossref">10.1139/E09-004</doi>
<unstructured_citation>
Waldron, J.W.F., White, C.E., Barr, S.M., Simonetti, A., and Heaman, L.M. 2009. Provenance of the Meguma terrane, Nova Scotia: rifted margin of early Paleozoic Gondwana. Canadian Journal of Earth Sciences, 46, pp. 1–8. https://doi.org/10.1139/E09-004
</unstructured_citation>
</citation>
<citation key="16883">
<doi provider="crossref">10.1144/0016-76492010-068</doi>
<unstructured_citation>
Waldron, J.W.F., Schofield, D.I., White, C.E., and Barr, S.M., 2011. Cambrian successions of the Meguma Terrane, Nova Scotia, and Harlech Dome, North Wales: dispersed fragments of a peri-Gondwanan basin? Journal of the Geological Society, London, 168, pp. 83–98. https://doi.org/10.1144/0016-76492010-068
</unstructured_citation>
</citation>
<citation key="16884">
<doi provider="crossref">10.1139/cjes-2020-0089</doi>
<unstructured_citation>
Warsame, H, McCausland, P, White, C.E., Barr, S.M., Dunning, G.R., and Waldron, J. 2021. Meguma terrane orocline: U–Pb age and paleomagnetism of the Silurian Mavillette gabbro, Nova Scotia, Canada. Canadian Journal of Earth Sciences, 58, pp. 315–331. https://doi.org/10.1139/cjes-2020-0089
</unstructured_citation>
</citation>
<citation key="16885">
<doi provider="crossref">10.4138/atlgeol.2010.008</doi>
<unstructured_citation>
White, C.E. 2010. Stratigraphy of the Lower Paleozoic Goldenville and Halifax groups in southwestern Nova Scotia. Atlantic Geology, 46, pp. 136–154. https://doi.org/10.4138/atlgeol.2010.008
</unstructured_citation>
</citation>
<citation key="16886">
<unstructured_citation>
White, C.E., 2013. Overview geological map of southwestern Nova Scotia. Nova Scotia. Department of Natural Resources, Mineral Resources Branch, Open File Map ME2012-1, scale 1:100 000.
</unstructured_citation>
</citation>
<citation key="16887">
<unstructured_citation>
White, C.E. 2019. Bedrock geology map of the central Annapolis Valley area, Nova Scotia. Nova Scotia Department of Energy and Mines, Geoscience and Mines Branch, Open File Map ME 2019-006, scale 1:50 000.
</unstructured_citation>
</citation>
<citation key="16888">
<doi provider="crossref">10.1130/2010.1206(15)</doi>
<unstructured_citation>
White, C.E. and Barr, S.M. 2010. Lithochemistry of the Lower Paleozoic Goldenville and Halifax groups, southwestern Nova Scotia, Canada: Implications for stratigraphy, provenance, and tectonic setting of Meguma. In From Rodinia to Pangea: The Lithotectonic Record of the Appalachian Region. Edited by R.P. Tollo, M.J. Bartholomew, M.J., J.P. Hibbard, and P.M. Karabinos. Geological Society of America Memoir, 206, pp. 347–366. https://doi.org/10.1130/2010.1206(15)
</unstructured_citation>
</citation>
<citation key="16889">
<unstructured_citation>
White, C.E. and Barr, S.M. 2012a. Meguma terrane revisited: stratigraphy, metamorphism, paleontology, and provenance: GAC-MAC 2012 St. John’s post meeting field guide summary. Geoscience Canada 39, pp. 8–12.
</unstructured_citation>
</citation>
<citation key="16890">
<unstructured_citation>
White, C.E. and Barr, S.M. 2012b. The new Meguma: stratigraphy, metamorphism, paleontology, and provenance. Field Trip Guidebook B5, prepared for St. John’s 2012 GAC-MAC Joint Annual Meeting, 68 p.
</unstructured_citation>
</citation>
<citation key="16891">
<doi provider="crossref">10.4138/atlgeol.2017.015</doi>
<unstructured_citation>
White, C.E. and Barr, S.M. 2017. Stratigraphy and depositional setting of the Silurian–Devonian Rockville Notch Group, Meguma terrane, Nova Scotia, Canada. Atlantic Geology, 53, pp. 337–365. https://doi.org/10.4138/atlgeol.2017.015
</unstructured_citation>
</citation>
<citation key="16892">
<unstructured_citation>
White, C. E. and Nickerson, S. J. 2021. Working towards a new bedrock geology map of the Meguma terrane, eastern shore of Nova Scotia: Building a stratigraphy. In Geoscience and Mines Branch, Report of Activities 2020-2021. Edited by E.W. MacDonald and D.R. MacDonald. Nova Scotia Department of Natural Resources and Renewables, Report ME 2021-002, pp. 73–78.
</unstructured_citation>
</citation>
<citation key="16893">
<unstructured_citation>
White, C.E. and Scallion, K-L.2011. Bedrock geology map of the Governor Lake area, part of NTS sheets 21E/01, 02, 07, and 08, Colchester, Guysborough, Halifax, and Pictou counties, Nova Scotia. Nova Scotia Department of Natural Resources, Mineral Resources Branch, Open File Map ME 2011-013, scale 1:50 000.
</unstructured_citation>
</citation>
<citation key="16894">
<unstructured_citation>
White, C.E. and Vaccaro, M. 2019. Bedrock mapping in the Meguma terrane: a long-awaited return to the Eastern Shore of Nova Scotia. In Geoscience and Mines Branch, Report of Activities 2018-2019. Edited by E.W. MacDonald and D.R. MacDonald. Nova Scotia Department of Energy and Mines, Report ME 2019-002, pp. 77–79.
</unstructured_citation>
</citation>
<citation key="16895">
<unstructured_citation>
White, C.E. and Vaccaro, M. 2020. Meguma terrane bedrock mapping project, Eastern Shore of Nova Scotia: a progress report. In Geoscience and Mines Branch, Report of Activities 2019-2020. Edited by D.R. MacDonald and E.W. MacDonald. Nova Scotia Department of Energy and Mines, Report ME 2020-002, pp. 137-140.
</unstructured_citation>
</citation>
<citation key="16896">
<doi provider="crossref">10.1130/B30638.1</doi>
<unstructured_citation>
White, C.E., Palacios, T., Jensen, S, and Barr, S.M. 2012. Cambrian–Ordovician acritarchs in the Meguma terrane, Nova Scotia, Canada: resolution of Early Paleozoic stratigraphy and implications for paleogeography. Geological Society of America Bulletin, 124, pp. 1773–1792. https://doi.org/10.1130/B30638.1
</unstructured_citation>
</citation>
<citation key="16897">
<doi provider="crossref">10.1139/cjes-2017-0196</doi>
<unstructured_citation>
White, C.E., Barr, S.M., and Linnemann, U. 2018. U–Pb (zircon) ages and provenance of the White Rock Formation of the Rockville Notch Group, Meguma terrane, Nova Scotia, Canada: Evidence for the “Sardian gap” and West African origin. Canadian Journal of Earth Sciences, 55:(6), pp. 589–603. https://doi.org/10.1139/cjes-2017-0196
</unstructured_citation>
</citation>
</citation_list>
</journal_article>
</journal>
</crossref>
</doi_record>
</query>
</body>
</query_result>
</crossref_result>

**Metadata is hugely useful**

Unlike publications themselves, metadata is typically free. And, we can learn a lot from it. Crossref, for example, can store the following things as publicly accessible metadata:

title
subtitle
authors
orcids
affiliation
copyright license

funder/grant ids
languages
ror
references
resource location
version

publisher
journal
volume/issue
related dois
dates
abstracts

Crossref makes this metadata available through a public API.

More examplin'

Let's look at the same registered metadata (in JSON format) for a DOI using the Crossref public API: 10.4138/atlgeo.2022.008

More examplin'

Similarly, we can also look at the title level metadata and information (in JSON format) using the Crossref public API: 10.4138

And for kicks...

Here's some other potential queries with that same API.

Article titles on this prefix https://api.crossref.org/prefixes/10.4138/works?select=DOI,title
All works registered with a specific ORCID iD
https://api.crossref.org/works?filter=orcid:0000-0001-5527-8489
Grant registrations by organization in Crossref metadata
https://api.crossref.org/types/grant/works?rows=0&facet=funder-name:*
List of top 10 most-cited DOIs for this prefix (results limited to DOI, title, and citation count) https://api.crossref.org/prefixes/10.4138/works?sort=is-referenced-by-count&select=DOI,title,is-referenced-by-count&order=desc&rows=10

Is it time for you to tell me what an API is?

APIs

API stands for

Application
Programming
Interface

An API is, basically, a set of rules for interacting with software.

Think of it as being a little like a translator working as an intermediary between two people who don't speak the same language

APIs

APIs are everywhere. When my calendar app tells me today's forecast, it's accessing that information using the Accuweather API. When my watch vibrates because I got a text message, that's because Garmin's API is communicating with Apple's notifications API.

APIs are how disparate systems, built by different people, using different languages and definitions, find common ground and share information.

APIs

This network of APIs is like a municipal water system (get it?). It is, increasingly, infrastructure relied upon by researchers and institutions whether or not they are really aware of it.

When I'm talking about "open scholarly infrastructure" this is what I mean. A network of open APIs with free/open metadata and metrics, capable of delivering information, metrics, context, and content.

Almost all open scholarly infrastructure is based around APIs.

Open scholarly infrastructure!

Open scholarly infrastructure

Open scholarly infrastructure is a network of scholarly-research-focused open-source platforms, service providers, and APIs that work in concert to share data, illuminate relationships, and make research more discoverable.

https://openscholarlyinfrastructure.org/

Example one // ORCiD

I am setting up my ORCiD account.

Let's pretend:

Example one // ORCiD

Within ORCiD, I can check against the Crossref and DataCite APIs for any publications matching my name.

I want to add my publications!

Example one // ORCiD

It will take me a while to do this the first time, and it’ll only work if my articles have DOIs.

Most publications register dois

Example one // ORCiD

for all my publications I know are mine (and have DOIs) the metadata is automatically pulled into my ORCiD account.

ORCiD pulls that metadata from the Crossref API.

But...

👆

Example one // ORCiD

now that I have an ORCiD, that metadata (ideally) is included in the DOI when I publish.

Crossref will say to ORCiD, "we know this work belongs to this scholar because their ORCiD is in the metadata. We'll just push this new publication to their record automatically."

And...!

Example two // Funders and ORCiD

I've applied for funding from an agency that has an ORCiD account or integration.

Let’s pretend:

Example two // Funders and ORCiD

funding id
grant id
datasets
articles
service

That agency can push new data to my ORCiD account.

👆

Example two // Funders and ORCiD

the next time I apply for funding, I just push my ORCiD to the agency, and they can pull my work without me filling out the same form again.

And, ideally...

Open scholarly infrastructure ties the room together!

crossref

datacite

orcid

elsevier

t&f

sage

ror

github

dataverse

zenodo

arxiv

mendelay

zotero

cris systems

funders

openaire

google scholar

unpaywall

share your paper

plos

...

Open scholarly infrastructure

Without the Crossref API, all of these examples kind of fall apart.

Publications that aren’t using DOIs are, essentially, “off the grid.”

The absence of these connections results in a lot of folks entering the same metadata into systems, over and over, by hand. Or, hiring graduate students to do this for them.

That's an excellent use of everyone's time, definitely.

Persistent identifiers

In concert with open scholarly infrastructure, PIDs allow us to see the big picture through these connections and interactions. It can expose relationships between data and research or institutions and outcomes. It can make research outcomes more discoverable.

When we talk about PIDs, we’re talking about supporting open infrastructure and free exchange of metadata.

A word, though, on metadata

The metadata we get out of these systems, and its utility, is very much dependent on its quality.

We have a general expression in the metadata universe. that's "garbage in, garbage out."

Metadata is kind of everyone's responsibility. Researchers, librarians, publishers, registration agencies... everyone has a stake in accurate, usable metadata.

Metadata is a very complicated topic I could talk about for twice the length of this talk. Any time! Let me know! I'll do it.

I understand that this is a lot to take in.

What I'm hoping you'll come away with today is a little perspective.

PIDs aren't

just links to things
academic bit.ly
status symbols
permanent
magic

PIDs are

potentially huge time savers
useful for finding research
interconnected between services
the backbone of open scholarly infrastructure

Now that you've got a better understanding of PIDs, let's talk about using them in OJS.

Open Journal Systems

Out of the box, Open Journal Systems is hugely supportive of open scholarly infrastructure. In fact, OJS is an example of open scholarly infrastructure.

Things will vary a bit depending on the version of OJS you're running. I'll try to cover both the long-term support version (LTS), 3.3.x, and the current release, 3.4.x.

If you're leveraging PIDs and other connections to open infrastructure, it's likely best to stay updated to, at least, the latest LTS version.

Open Journal Systems

I'll also note that everything we'll be going over in this section can be found in more detail in the PKP docs hub or in the readme.txt files for any individual plugin in the plugin gallery.

DOI Plugin
Crossref Manual (Datacite works basically the same way)
ORCiD Plugin Guide
ROR Plugin Guide
Crossref Reference Linking Plugin
Crossref Cited By (external)
MedDRA Plugin
ORCiD Profile Plugin
QuickSubmit Plugin and DOIs

A quick word on installing plugins.

Plugins

You can view your plugins from the Dashboard by clicking on Website under the "Settings" header on the left sidebar.

Plugins

You can view your plugins from the Dashboard by clicking on Website under the "Settings" header on the left sidebar.

Then, on the main screen of the Dashboard, click the Plugins tab.

"Installed Plugins" shows you all the plugins installed by default or added for your journal. All other compatible plugins are viewable in the gallery.

Installing Plugins

From the plugin gallery, click on the name of the plugin you want to install. This will open a window with information about the plugin (including the GitHub repo that houses the source code).

Clicking on the "install" button in the top right of this window will install the plugin.

Enabling Plugins

Once your plugins are installed, you can enable them from the "Installed Plugins" tab.

There's a checkbox on the right showing enabled status.

grey checkboxes are default plugins you cannot disable
blue checkboxes are enabled plugins
empty boxes are disabled plugins

Plugin Settings

Some plugins have settings. To see your options for any individual plugin, click on the arrow to the left of the plugin name to expand.

You can also update plugins the same way.

Assigning DOIs

A gentle reminder that assigning DOIs and registering DOIs are two different things.

DOIs in OJS 3.3.X (LTS)

No matter which DOI registration agency you have a membership with, the process of assigning DOIs is the same.

In 3.3.x, you will need to start by configuring your DOI plugin. You can find the DOI plugin and it's settings under Installed Plugins and the sub-heading "Public Identifier Plugins".

DOIs in OJS 3.3.X (LTS)

There's a space to put your prefix here. You'll be given a prefix by your registration agency or by your parent organization/publisher.

You can also choose which things to assign DOIs to. You might be tempted to click all of them. I recommend just assigning DOIs to Articles.

DOIs in OJS 3.3.X (LTS)

Next, are the suffixes. If you recall, I more or less begged you to not think of these as meaning anything to readers or users.

I recommend either using the default patterns here and just ignoring what they say, or creating a custom pattern with the bottom option that is even more simple than the default.

DOIs in OJS 3.3.X (LTS)

You cannot correct or change a DOI after it has been registered. If you register a DOI with a typo in it, that isn't a solvable problem.

You can edit registered metadata. You cannot edit the DOI itself.

Take typos right out of the equation!

%j.%Y.%a is a great custom option.

DOIs in OJS 3.3.X (LTS)

These are the final two options. They should be treated with caution.

Reassign DOIs will unassign all DOIs for your journal and reassign DOIs based on whatever your prefix settings are. If you've registered anything, do not click this.

Assign DOIs will assign a DOI to anything in your journal that does not already have one.

DOIs in OJS 3.3.X (LTS)

Lastly, you can make sure a DOI will be assigned at the article level. In the Publication tab for any submission, you can click on "Identifiers" in the sidebar and see DOI information.

You'll see an "assign" button to automatically generate a DOI based on your prefix settings. You can modify a DOI here until it is published.

DOIs in OJS 3.4.X

In OJS 3.4, DOI management has been overhauled.

You can now find your DOI plugin settings in the left sidebar under the option Distribution.

You can set your prefixes, suffix patterns (now with opaque string generation), as well as choose your registration agency from a dropdown menu.

DOIs in OJS 3.4.X

You will also need to enable the plugin for the registration agency to which you are a member.

Registering DOIs

In 3.3.x, you can find the registration options in the left sidebar of the dashboard, at the bottom, by clicking on the Tools link.

From here, choose either the Crossref or Datacite Export/Registration plugins.

They both operate very similarly!

DOIs in OJS 3.3.X (LTS)

Each plugin starts with a settings page with a few options and your credentials for your membership. These credentials will always be your login credentials for Datacite or Crossref, not for this OJS install.

DOIs in OJS 3.3.X (LTS)

Each plugin has the same registration menu under the tab labelled "Articles". It shows you the article ID, author/title, issue, DOI to be registered, and a status.

"Active" means a DOI has been registered and is resolving.

If your plugin is set to automatic, you can basically ignore this. It will register for you within a few hours.

DOIs in OJS 3.3.X (LTS)

In OJS 3.4, all DOI management and registration can be accessed from the DOIs menu on the sidebar, in the top left.

DOIs in OJS 3.4.X

This DOI manager has significantly more features, including flags for DOIs that need updating (when their metadata has changed). You can also assign DOIs per article here if you wish, without having to navigate to an individual publication.

You can also cue up bulk updates or bulk registrations.

DOIs in OJS 3.4.X

DOI value adds if you're using Crossref.

Additional Plugins

If you have a Crossref membership, there are a few additional plugins you can use to supplement your experience and deposited metadata.

Reference Linking adds your references to your deposits. Funder data adds funders to your deposits using an open registry maintained by Crossref.

All of these improve the value of the metadata you deposit to Crossref and help form clearer connections between researchers, funders, and research output.

Please remember to update your DOI registration after you make metadata changes!

ROR

ROR in OJS 3.3.X (LTS)

You can find the ROR plugin in the gallery with the name: Research Organization Registry (ROR) Plugin.

This plugin will allow for autocomplete against the ROR API within the "affiliation" metadata element for submissions.

It will also display ROR links on article landing pages.

Navigate to the plugin gallery and install the ROR plugin.
Navigate to your installed plugins and enable the ROR plugin.

End of list!

Currently, ROR metadata is only added to Datacite deposits. ROR metadata in Crossref is flagged for a future release of the 3.3.

ROR in OJS 3.4.X

Unfortunately, the ROR plugin has yet to be ported to OJS 3.4.

ORCID

ORCiD has two different APIs.

Public API

ORCiD's public API allows any journal to pull public metadata from ORCiD. In OJS, the public API option fascilitates:

Authors can connect their ORCiD ID with their publications.
ORCiDs recorded as metadata will be deposited in DOI registrations with Crossref and Datacite.
Author ORCiDs will be linked on article landing pages.

ORCiD's member API allows journals to push metadata to ORCiD. The member API allows for all of the capability of the public, and also:

Peer-review activity can be pushed to author's ORCiD profile.
Article records can be pushed directly to ORCiD profiles.

Member API

It is totally fine to use the public API, and you'll still get a significant interaction with ORCiD this way.

The most important piece for authors here is the link to their profile. If you're using DOIs and profiles are configured for automatic addition, works will still be added to their ORCiD automatically.

The member API's strongest asset is the ability to push peer review work to ORCiD.

Memberships to ORCiD tend to be institutional and aren't cheap. If you aren't concerned about automatic population of peer-review work to ORCiD, the public API will meet your needs plenty.

In the Interest of Brevity

I recommend you read the ORCiD plugin documentation.

The plugin is pretty straightforward to set up if you are a single journal.

However, if you are installing on a shared, multi-journal instance of OJS you will need access to your config file. You may require technical assistance for this, depending on your comfort level.

https://docs.pkp.sfu.ca/orcid/

You'll need an ORCiD account and will need to procure at least a public API key (this is free). Of the three PID integrations, this one has the most steps.

It is, however, very much worth the time to support your authors!

Bonus Round

I finished this deck and started thinking about, like... you know all of this documentation exists, and now you have these slides, and maybe I don't need to go clean through it all step by step. Maybe, instead, I can talk a bit about why PIDs and metadata are so important in modern publishing. Is that cool?

Forgive me...

for being presumptive, but there is a general expectation that you want people to see the products of your hard work.

You want your work to be known and discoverable; accessible to the folks who might benefit from it.

I would think (hope).

And, you'd probably like it to be attributed to you, since you did the work and also since the implications of its value will have some impact on your career or the career of your authors.

It's possible...

this may seem weird because, depending on where you are in your career, you are maybe not used to doing this.

After all, most of the experience of dissemination as a student (for example) is submitting papers to one person who grades them.

It is certainly fine if this is the case. It's very normal. Fun fact, plenty of established researchers don't really think too hard about where and how their work is shared, either.

For students, this is what "disseminating your research" mostly looks like.

https://science.gc.ca/site/science/en/open-science

Submitting your work as a modern academic kicks off an enormous Rube Goldberg machine of scholarly publishing infrastructure. We're talking data, articles, preprints, presentations, proceedings, and countless other things.

Your work is going to end up in a lot of places, often without you even really being aware of it.

Where do the products of research go?

The perception

I suspect a lot of folks don't really think too much about how publishing works. Generally, we know a few things happen.

Let's say I'm talking to researchers.

you submit articles to a journal
articles undergo peer review
works are published
the people who want to read those works can read them
things will get cited
number of citations is very important
number of citations is directly correlated with where you publish
OA might be required, somehow

The perception

This isn't wrong, per se, but it's definitely not the whole story.

you submit articles to a journal
articles undergo peer review
works are published
the people who want to read those works can read them
things will get cited
number of citations is very important
number of citations is directly correlated with where you publish
OA might be required, somehow

journal

vor

peer-review

journal

ir datacite

vor

peer-review

self-archiving

The reality

Publishing is more iterative (and tied to a wider range of accessible outputs) than it's ever been.

submission still happens, but users might post their work on a preprint server before peer review
a funder mandate might require open access or, at least, an open access version of the work
if you're publishing in a major subscription journal, lots of people cannot read your work
data management might require publication of a data set

arxiv

ir datacite

webpage

journal

ir crossref

ir handle

preprint

pubmed

ir datacite

zenodo

dataset

vor

shareyourpaper

openaire

zenodo

dataverse

THESE ARE ALL PLACES YOUR METADATA CAN/WILL GO!

If you jam, "Editors, The" into the name field for something that doesn't have an actual author, guess where that will end up.

If you manage a journal, you are standing at the nozzle of a metadata firehose.

This is important stuff for both a journal and for authors.

Authors will know what they worked on, for example, but people (researchers, funders) looking for their work might not.

Maybe they share a name with another researcher and their results are always co-mingled. Or their field only uses first name initials in metadata.

Or, maybe they changed their name, and it's painful or unpleasant that all their old publications require others to know it.

Unless your name is wildly unique, I'm here to tell you that accurate, reliable attribution can definitely be a problem.

Citation styles like APA are not equipped to deal with the varieties in both human identity and how modern research is shared.

Even this required a student id number.

All researchers need to talk about the work they've done. Often. Repeatedly. And, all researchers benefit from clear, unambiguous attribution.

Persistent identifiers – and the connections they expose – aid dramatically the discovery, dissemination, and attribution of all these disparate products of research.

I cannot believe you are still talking.

This has been, frankly, an astounding amount of content. I'd like to congratulate you for enduring it.

Please remember that PIDs are definitely worth the effort and, once they're set up, more or less handle themselves.

I would love to answer questions if we have time, but I assume as I'm writing this that we are definitely over time.

It's ok! I am comfortable with myself, please refer to this deck whenever you need to! Please also read our documentation!

Thanks!

Getting Found, Staying Found: Persistent Identifiers & Their Value

By Mike Nason

Getting Found, Staying Found: Persistent Identifiers & Their Value

Persistent Identifiers, commonly referred to as PIDs, play a pivotal role in fostering trust within scholarly publications while concurrently enhancing publication discoverability and accessibility. Join this session to learn about the multifaceted value of PIDs at different levels, including authors, articles, and journals. The second part of this webinar will explore practical skills around PIDs, plugins, integrations, and interoperability for Open Journal Systems (OJS) users. Join this webinar and learn to think more maximally about metadata in your OJS publications!

Mike Nason PRO

Open Scholarship and Publishing Librarian @ UNB Libraries // Metadata Nag and DOI Wrangler @ PKP // General Loudmouth and Malcontent

ahemnason

Persistent Identifiers & Open Scholarly Infrastructure

~40m

Agenda

~10m

Introduction(s)

I'd like for you to keep a thought on the backburner.

Persistent Identifiers are in the drinking water of scholarly publishing.

I'll come back to this. Like, a lot.

Let's start small.

The DOI.

DOIs

In the wild

In the wild

In citations

DOIs

DOIs

How a DOI works

How a DOI works

How a DOI works

How a DOI works

What's "resolution"?

How DOI resolution works

How DOI resolution works

How DOI resolution works

Neat!

Surely, there is more to it?

🤔🤔🤔

Yeah, buddy!

Let's review

Let's step back a bit to talk about persistent identifiers in general.

Persistent Identifiers (PIDs)

DOIs are identifiers!

Identifiers

Identifiers

Identifiers

Ok, so what about persistence?

Persistent identifiers

Persistent identifiers

An example

If I move my journal to a new web domain, I don't want every citation that exists to have an old URL.

Instead, the DOI works as a stand-in that, if updated, will not only resolve to the new location but also contain all it's metadata.

So long as the service persists, any item with a DOI should be locatable.

What about PIDs for things that aren't publications?

ORCiD!

ORCiD

What is an ORCiD?

ORCiD IDs

ORCiD IDs

For example

Here's some presumptions!

Here's some presumptions!

AND

And so...

Persistent identifiers

Persistent identifiers

PIDs require a third party

What is a registration agency?

Registration agencies

Registration agencies

Let's review the field!

PIDs for scholarly works

PIDs for scholarly works

PIDs for researchers

PIDs for organizations

A quick example re: ROR

Registration agencies

For example

Metadata is hugely useful

More examplin'

More examplin'

And for kicks...

Is it time for you to tell me what an API is?

APIs

APIs

APIs

Open scholarly infrastructure!

Open scholarly infrastructure

Example one // ORCiD

Example one // ORCiD

Example one // ORCiD

Persistent Identifiers are
in the drinking water of
scholarly publishing.

I'll come back to this.
Like, a lot.

**Let's step back a bit to talk about persistent identifiers in general.**

**Ok, so what about persistence?**

**Instead, the DOI works as a stand-in that, if updated, will not only resolve to the new location but also contain all it's metadata.**

**PIDs require a third party**

**Metadata is hugely useful**