<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Riccardo,<br>
please find my comments below.<br>
<br>
On 11/12/2015 5:45 PM, riccardo del gratta wrote:<br>
</div>
<blockquote cite="mid:5644C226.6060909@ilc.cnr.it" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi devs,<br>
I'm Riccardo from ILC in Pisa. I just installed a Dspace5
out-of-the-box </blockquote>
<br>
You mean "raw" DSpace 5 (<a class="moz-txt-link-freetext" href="https://github.com/DSpace/DSpace">https://github.com/DSpace/DSpace</a>) or LINDAT
DSpace (<a class="moz-txt-link-freetext" href="https://github.com/ufal/lindat-dspace">https://github.com/ufal/lindat-dspace</a>) based on DSpace 5?<br>
<br>
<blockquote cite="mid:5644C226.6060909@ilc.cnr.it" type="cite">and
I'm wondering how to define a new metadata schema in the
repository. I mean I just created one from the user interface
pointing to the schema-http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/profiles/clarin.eu:cr1:p_1349361150622/xsd<br>
</blockquote>
<br>
I will explain how it works now in DSpace in general.<br>
<br>
# Metadata schemas (in DSpace)<br>
<br>
First of all, DSpace uses relational database to store metadata in a
key - value pair idiom.<br>
You define metadata schemas in order for DSpace to know which keys
are "known" and can be used. If I understood you correctly, you
tried to use the profile xsd url in "Namespace" of Metadata Registry
in DSpace. But that does nothing (only saves the information for
later, see crosswalks below). You must Add the schema and the
*fields* which can be used as the keys. If you try to use a key not
defined you get an error.<br>
<br>
# Inserting records (metadata)<br>
<br>
Inserting submissions to DSpace can be done in many ways but we will
focus on the the "manual way". This means filling out metadata
during submission workflow [1].<br>
Most of the steps in the submission workflow are configured in
input-forms.xml [2] e.g.,<br>
...<br>
<page number="1"><br>
...<br>
<field><br>
<dc-schema>dc</dc-schema><br>
<dc-element>title</dc-element><br>
<dc-qualifier></dc-qualifier><br>
<repeatable>false</repeatable><br>
<label>Title</label><br>
<input-type>onebox</input-type><br>
<hint>Enter the main title of the item in
English.</hint><br>
<required>You must enter a main title for
this item.</required><br>
</field><br>
<br>
In other words, the input value is mapped to a metadata schema
element. LINDAT DSpace supports also simple components without
recursion though.<br>
Note: If you are a librarian then the metadata schema in DSpace in
the context above might be ambiguous. Simply, think about it as a
list of key-value pairs that can be used.<br>
<br>
# Using metadata<br>
<br>
Now you know how the metadata are stored and from where. The
question now is how to use or "show" them.<br>
Firstly, in the lindat dspace user interface, you do it mostly from
inside xsl like this<br>
<xsl:value-of
select="dim:field[@mdschema='dc' and
@element='title'][not(@qualifier)][1]/node()"/><br>
The interesting part is how to export it to different metadata
formats like a CMDI profile. That is done dynamically using
crosswalks [3] e.g., lindat_cmdi.xsl [4]<br>
...<br>
<xsl:template match="/"><br>
<xsl:variable name="uploaded_md"
select="itemUtil:getUploadedMetadata($handle)"/><br>
<xsl:choose><br>
<xsl:when test="$uploaded_md != ''"><br>
<xsl:copy-of select="$uploaded_md"/><br>
</xsl:when><br>
<xsl:otherwise><br>
<xsl:call-template name="ConstructCMDI"/><br>
</xsl:otherwise><br>
</xsl:choose><br>
</xsl:template><br>
...<br>
<xsl:template name="ConstructCMDI"><br>
<xsl:variable name="contact"
select="/doc:metadata/doc:element[@name='local']/doc:element[@name='contact']/doc:element[@name='person']/doc:element/doc:field[@name='value']"/><br>
<xsl:variable name="profile"><br>
...<br>
<br>
Note: This snippet also shows a ""hidden"" feature - you can upload
a specific file during submission workflow which is then used
instead of the generated one. However, this was meant for very
specific needs (integration to Weblicht).<br>
<br>
# CMDI profile<br>
<br>
Let's assume you are using lindat dspace. This leaves us with a
(very good) question whether to reuse our CMDI profile or not. The
complete answer is here [5]. If you tend to store the same metadata
as we do then reuse it. Otherwise you have to do the following<br>
1. create new metadata schema<br>
2. add missing fields you plan to use in your profile<br>
3. update input forms to use the fields from 2.<br>
4. create the profile in CMDI<br>
5. update the crosswalk<br>
<br>
# Last notes<br>
<br>
If you tend to use specific fields for very important information
that you want to be used when searching or when displaying filters
(facets) you have to configure it.<br>
<br>
Do not hesitate to join us at our weekly technical meetings -
<a class="moz-txt-link-freetext" href="https://lindat.mff.cuni.cz/en/events">https://lindat.mff.cuni.cz/en/events</a>.<br>
<br>
Best,<br>
Jozef Misutka<br>
<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://lindat.mff.cuni.cz/repository/xmlui/page/deposit">https://lindat.mff.cuni.cz/repository/xmlui/page/deposit</a><br>
[2]
<a class="moz-txt-link-freetext" href="https://github.com/ufal/lindat-dspace/blob/lindat/dspace/config/input-forms.xml">https://github.com/ufal/lindat-dspace/blob/lindat/dspace/config/input-forms.xml</a><br>
[3] <a class="moz-txt-link-freetext" href="https://wiki.duraspace.org/display/DSPACE/CrosswalkPlugins">https://wiki.duraspace.org/display/DSPACE/CrosswalkPlugins</a><br>
[4]
<a class="moz-txt-link-freetext" href="https://github.com/ufal/lindat-dspace/blob/lindat/dspace/config/crosswalks/oai/metadataFormats/lindat_cmdi.xsl">https://github.com/ufal/lindat-dspace/blob/lindat/dspace/config/crosswalks/oai/metadataFormats/lindat_cmdi.xsl</a><br>
[5] <a class="moz-txt-link-freetext" href="https://lindat.mff.cuni.cz/repository/xmlui/page/metadata">https://lindat.mff.cuni.cz/repository/xmlui/page/metadata</a><br>
<br>
<blockquote cite="mid:5644C226.6060909@ilc.cnr.it" type="cite"> Is
it enough? Because according to LINDAT this seams not enough..<br>
<br>
Is there a documentation clearer than dspace's native hot to
create new schema and ingest items according to that?<br>
<br>
Thanks Riccardo<br>
<br>
<h5><br>
</h5>
</blockquote>
<br>
</body>
</html>