hazza/DSpace
1
0
Fork 0
mirror of https://github.com/DSpace/DSpace.git synced 2025-10-18 07:23:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revisions for accuracy

Browse Source 
git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@4975 9c30dcfa-912a-0410-8fc2-9e0234be79fd
This commit is contained in:
Jeffrey Trimble
2010-05-20 15:04:23 +00:00
parent 2147904524
commit 103e5db8d2
1 changed files with 38 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
dspace/docs/docbook/sys_admin.xml
View File

@@ -233,6 +233,26 @@ archive_directory/
</para>
<para> where &apos;\t&apos; is the tab character and &apos;bundlename&apos; is replaced by the name of the bundle to which the bitstream should be added. If no bundle is specified, the bitstream will be added to the &apos;ORIGINAL&apos; bundle.</para>
</section>
<section remap="h3">
<title><anchor id="docbook-sys_admin.html-dsafvariations" xreflabel="Different Schema"/>Configuring <literal>metadata-[prefix].xml</literal> for Different Schema</title>
<para>It is possible to use other Schema such as EAD, VRA Core, etc. Make sure you have defined the new scheme in the DSpace Metada Schema Registry. <orderedlist>
<listitem>
<para>Create a separate file for the other schema named "<literal>metadata_{prefix}.xml</literal>", where the <literal>{prefix}</literal> is replaced with the schema's prefix.</para>
</listitem>
<listitem>
<para>Inside the xml file use the dame Dublin Core <emphasis>syntax</emphasis>, but on the <literal>&lt;dublin_core&gt;</literal> element include the attribute "<literal>schema={prefix}</literal>".</para>
</listitem>
<listitem>
<para>Here is an example for ETD metadata, which would be in the file "<literal>metadata_etd.xml"</literal>:</para>
<screen>&lt;xml version="1.0" encoding="UTF-8"?&gt;
&lt;dublin_core schema="etd"&gt;
&lt;dcvalue element="degree" qualifier="department"&gt;Computer Science&lt;/dcvalue&gt;
&lt;dcvalue element="degree" qualifier="level"&gt;Masters&lt;/dcvalue&gt;
&lt;dcvalue element="degree" qualifier="grantor"&gt;Texas A &amp; M&lt;/dcvalue&gt;
</screen>
</listitem>
</orderedlist></para>
</section>
<section remap="h3">
<title><anchor id="docbook-sys_admin.html-importingitems" xreflabel="ImportingItems"/>Importing Items</title>
<note>
@@ -578,7 +598,7 @@ archive_directory/
<section>
<title>CLI Examples</title>
<para><emphasis role="bold">Adding Metadata</emphasis>:</para>
<para><literal>[dspace]/bin/dspace updateitem -e joe@user.com -s [path/to/archive] -a dc.description</literal></para>
<para><literal>[dspace]/bin/dspace itemupdate -e joe@user.com -s [path/to/archive] -a dc.description</literal></para>
<para><emphasis>This will add from your archive the dc element description based on the handle from the URI (since the -i argument wasn't used).</emphasis></para>
</section>
</section>
@@ -1120,11 +1140,11 @@ Transforming DSpace Content"/>MediaFilters: Transforming DSpace Content</title>
<para>Subsequent rows in the csv file relate to items. A typical row might look like:</para>
<screen><code>350,2292,Item title,"Smith, John",2008</code></screen>
<para>If you want to store multiple values for a given metadata element, they can be separated with the double-pipe &apos;||&apos; (or another character that you defined in your <literal>dspace.cfg </literal>file. For example:</para>
<screen><code>Horses||Dogs||Cats</code></screen>
<para>Elements are stored in the database in the order that they appear in the csv file. You can use this to order elements where order may matter, such as authors, or controlled vocabulary such as Library of Congress Subject Headings.</para>
<para>When importing a csv file, the importer will <emphasis>overlay</emphasis> the data onto what is already in the repository to determine the differences. It only acts on the contents of the cvs file, rather than on the complete item metadata. This means that the CSV file that is exported can be manipulated quite substantially before being re-imported. Rows (items) or Columns (metadata elements) can be removed and will be ignored. For example, if you only want to edit item abstracts, you can remove all of the other columns and just leave the abstract column. (You do need to leave the ID column intact. This is mandatory).</para>
<para><emphasis role="bold">Editing collection membership.</emphasis> Items can be moved between collections by editing the collection handles in the 'collection' column. Multiple collections can be included. The first collection is the 'owning collection'. The owning collection is the primary collection that the item appears in. Subsequent collections (separated by the field separator) are treated as mapped collections. These are the same as using the map item functionality in the DSpace user interface. To move items between collections, or to edit which other collections they are mapped to, change the data in the collection column.</para>
<para><emphasis role="bold"
>Editing collection membership.</emphasis> Items can be moved between collections by editing the collection handles in the 'collection' column. Multiple collections can be included. The first collection is the 'owning collection'. The owning collection is the primary collection that the item appears in. Subsequent collections (separated by the field separator) are treated as mapped collections. These are the same as using the map item functionality in the DSpace user interface. To move items between collections, or to edit which other collections they are mapped to, change the data in the collection column.</para>
<para><emphasis role="bold">Adding items.</emphasis> New metadata-only items can be added to DSpace using the batch metadata importer. To do this, enter a plus sign '+' in the first 'id' column. The importer will then treat this as a new item. If you are using the command line importer, you will need to use the -e flag to specify the user email address or id of the user that is registered as submitting the items.</para>
<para><emphasis role="bold">Deleting Data.</emphasis> It is possible to perform deletes across the board of certain metadata fields from an exported file. For example, let's say you have used keywords (dc.subject) that need to be removed <emphasis>en masse</emphasis>. You would leave the column (dc.subject) intact, but remove the data in the corresponding rows.</para>
<para><emphasis role="bold">Migrating Data or Exchanging data.</emphasis> It is possible that you have data in one Dublin Core (DC) element and you wish to really have it in another. An example would be that your staff have input Library of Congress Subject Headings in the Subject field (dc.subject) instead of the LCSH field (dc.subject.lcsh). Follow these steps and your data is migrated upon import:</para>
@@ -1594,7 +1614,7 @@ checker.retention.CHECKSUM_MATCH = 8w</screen> You can use the table above for y
<tbody>
<row>
<entry>Command used:</entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace log-converter</literal></entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace stats-log-converter</literal></entry>
</row>
<row>
<entry>Java class:</entry>
@@ -1643,7 +1663,7 @@ checker.retention.CHECKSUM_MATCH = 8w</screen> You can use the table above for y
<tbody>
<row>
<entry>Command used:</entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace log-importer</literal></entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace stats-log-importer</literal></entry>
</row>
<row>
<entry>Java class:</entry>
@@ -1695,7 +1715,7 @@ checker.retention.CHECKSUM_MATCH = 8w</screen> You can use the table above for y
<tbody>
<row>
<entry>Command used:</entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace stats-utils</literal></entry>
<entry><emphasis><literal>[dspace]</literal></emphasis><literal>/bin/dspace stats-util</literal></entry>
</row>
<row>
<entry>Java class:</entry>