Skip to content

Commit

Permalink
deploy: ed43b97
Browse files Browse the repository at this point in the history
  • Loading branch information
monotasker committed Jan 8, 2025
1 parent fb29ddc commit 7a05c51
Show file tree
Hide file tree
Showing 6 changed files with 31 additions and 22 deletions.
Binary file modified .doctrees/environment.pickle
Binary file not shown.
Binary file modified .doctrees/metadata.doctree
Binary file not shown.
14 changes: 9 additions & 5 deletions _sources/metadata.md.txt
Original file line number Diff line number Diff line change
Expand Up @@ -273,21 +273,25 @@ The FAST vocabulary is augmented in KCWorks by the Homosaurus vocabulary (https:

### Works

#### DOI
#### DOI (primary identifier)

KCWorks (and InvenioRDM) supports the DOI identifier scheme to identify works in the repository. Note that two DOIs are minted for each KCWorks record: one for the current version of the record, and one for the work as a whole (including all versions). The version-specific DOI is stored in the `pids` property of the metadata record (`pids.identifiers.doi`). The work DOI is stored in the `parent.pids.doi` property of the `parent` object.

These DOIs are minted by DataCite (https://datacite.org/) and the attached metadata is maintained automatically by KCWorks.

Additional DOIs minted elsewhere can be attached to a KCWorks record. If provided at record creation such external DOIs can be used as the record's primary identifier (in `pids.doi`). Otherwise, they can be added using the `identifiers` property of the metadata record using the scheme `alternate-doi`. In both cases, these externally minted DOIs are **not** maintained automatically by KCWorks.

#### OAI
#### OAI (secondary identifier)

KCWorks also supports the OAI identifier scheme. The OAI identifier for a KCWorks record is stored in the `pids` property of the metadata record (`pids.identifiers.oai`).

#### ISSN
#### Handle (secondary identifier)

KCWorks also supports the Handle identifier scheme (https://handle.net/). The Handle identifier for a KCWorks record is stored in the `identifiers` property of the metadata record (`identifiers[0].identifier`) using the scheme `handle`.

#### ISSN (secondary identifier)

#### ISBN
#### ISBN (secondary identifier)

### People

Expand Down Expand Up @@ -329,7 +333,7 @@ KCWorks also supports the Integrated Authority File (GND) identifier scheme (htt

#### DOI

Funders in the `metadata.funding` array can be identified using DOIs and the scheme `doi`.
Funders in the `metadata.funding` array can be identified using DOIs formed with a FundRef id and the scheme `doi`.

#### OFR

Expand Down
37 changes: 21 additions & 16 deletions metadata.html
Original file line number Diff line number Diff line change
Expand Up @@ -528,21 +528,25 @@ <h4>Creator/contributor roles<a class="headerlink" href="#creator-contributor-ro
<h2>Identifier Schemes<a class="headerlink" href="#identifier-schemes" title="Link to this heading"></a></h2>
<section id="works">
<h3>Works<a class="headerlink" href="#works" title="Link to this heading"></a></h3>
<section id="doi">
<h4>DOI<a class="headerlink" href="#doi" title="Link to this heading"></a></h4>
<section id="doi-primary-identifier">
<h4>DOI (primary identifier)<a class="headerlink" href="#doi-primary-identifier" title="Link to this heading"></a></h4>
<p>KCWorks (and InvenioRDM) supports the DOI identifier scheme to identify works in the repository. Note that two DOIs are minted for each KCWorks record: one for the current version of the record, and one for the work as a whole (including all versions). The version-specific DOI is stored in the <code class="docutils literal notranslate"><span class="pre">pids</span></code> property of the metadata record (<code class="docutils literal notranslate"><span class="pre">pids.identifiers.doi</span></code>). The work DOI is stored in the <code class="docutils literal notranslate"><span class="pre">parent.pids.doi</span></code> property of the <code class="docutils literal notranslate"><span class="pre">parent</span></code> object.</p>
<p>These DOIs are minted by DataCite (https://datacite.org/) and the attached metadata is maintained automatically by KCWorks.</p>
<p>Additional DOIs minted elsewhere can be attached to a KCWorks record. If provided at record creation such external DOIs can be used as the record’s primary identifier (in <code class="docutils literal notranslate"><span class="pre">pids.doi</span></code>). Otherwise, they can be added using the <code class="docutils literal notranslate"><span class="pre">identifiers</span></code> property of the metadata record using the scheme <code class="docutils literal notranslate"><span class="pre">alternate-doi</span></code>. In both cases, these externally minted DOIs are <strong>not</strong> maintained automatically by KCWorks.</p>
</section>
<section id="oai">
<h4>OAI<a class="headerlink" href="#oai" title="Link to this heading"></a></h4>
<section id="oai-secondary-identifier">
<h4>OAI (secondary identifier)<a class="headerlink" href="#oai-secondary-identifier" title="Link to this heading"></a></h4>
<p>KCWorks also supports the OAI identifier scheme. The OAI identifier for a KCWorks record is stored in the <code class="docutils literal notranslate"><span class="pre">pids</span></code> property of the metadata record (<code class="docutils literal notranslate"><span class="pre">pids.identifiers.oai</span></code>).</p>
</section>
<section id="issn">
<h4>ISSN<a class="headerlink" href="#issn" title="Link to this heading"></a></h4>
<section id="handle-secondary-identifier">
<h4>Handle (secondary identifier)<a class="headerlink" href="#handle-secondary-identifier" title="Link to this heading"></a></h4>
<p>KCWorks also supports the Handle identifier scheme (https://handle.net/). The Handle identifier for a KCWorks record is stored in the <code class="docutils literal notranslate"><span class="pre">identifiers</span></code> property of the metadata record (<code class="docutils literal notranslate"><span class="pre">identifiers[0].identifier</span></code>) using the scheme <code class="docutils literal notranslate"><span class="pre">handle</span></code>.</p>
</section>
<section id="isbn">
<h4>ISBN<a class="headerlink" href="#isbn" title="Link to this heading"></a></h4>
<section id="issn-secondary-identifier">
<h4>ISSN (secondary identifier)<a class="headerlink" href="#issn-secondary-identifier" title="Link to this heading"></a></h4>
</section>
<section id="isbn-secondary-identifier">
<h4>ISBN (secondary identifier)<a class="headerlink" href="#isbn-secondary-identifier" title="Link to this heading"></a></h4>
</section>
</section>
<section id="people">
Expand Down Expand Up @@ -583,9 +587,9 @@ <h4>GND<a class="headerlink" href="#id1" title="Link to this heading">¶</a></h4
</section>
<section id="funders">
<h3>Funders<a class="headerlink" href="#funders" title="Link to this heading"></a></h3>
<section id="id2">
<h4>DOI<a class="headerlink" href="#id2" title="Link to this heading"></a></h4>
<p>Funders in the <code class="docutils literal notranslate"><span class="pre">metadata.funding</span></code> array can be identified using DOIs and the scheme <code class="docutils literal notranslate"><span class="pre">doi</span></code>.</p>
<section id="doi">
<h4>DOI<a class="headerlink" href="#doi" title="Link to this heading"></a></h4>
<p>Funders in the <code class="docutils literal notranslate"><span class="pre">metadata.funding</span></code> array can be identified using DOIs formed with a FundRef id and the scheme <code class="docutils literal notranslate"><span class="pre">doi</span></code>.</p>
</section>
<section id="ofr">
<h4>OFR<a class="headerlink" href="#ofr" title="Link to this heading"></a></h4>
Expand Down Expand Up @@ -1138,10 +1142,11 @@ <h3>custom_fields.hclegacy:total_downloads<a class="headerlink" href="#custom-fi
</li>
<li><a class="reference internal" href="#identifier-schemes">Identifier Schemes</a><ul>
<li><a class="reference internal" href="#works">Works</a><ul>
<li><a class="reference internal" href="#doi">DOI</a></li>
<li><a class="reference internal" href="#oai">OAI</a></li>
<li><a class="reference internal" href="#issn">ISSN</a></li>
<li><a class="reference internal" href="#isbn">ISBN</a></li>
<li><a class="reference internal" href="#doi-primary-identifier">DOI (primary identifier)</a></li>
<li><a class="reference internal" href="#oai-secondary-identifier">OAI (secondary identifier)</a></li>
<li><a class="reference internal" href="#handle-secondary-identifier">Handle (secondary identifier)</a></li>
<li><a class="reference internal" href="#issn-secondary-identifier">ISSN (secondary identifier)</a></li>
<li><a class="reference internal" href="#isbn-secondary-identifier">ISBN (secondary identifier)</a></li>
</ul>
</li>
<li><a class="reference internal" href="#people">People</a><ul>
Expand All @@ -1158,7 +1163,7 @@ <h3>custom_fields.hclegacy:total_downloads<a class="headerlink" href="#custom-fi
</ul>
</li>
<li><a class="reference internal" href="#funders">Funders</a><ul>
<li><a class="reference internal" href="#id2">DOI</a></li>
<li><a class="reference internal" href="#doi">DOI</a></li>
<li><a class="reference internal" href="#ofr">OFR</a></li>
</ul>
</li>
Expand Down
Binary file modified objects.inv
Binary file not shown.
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

0 comments on commit 7a05c51

Please sign in to comment.