Page History
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4372fa8debe61113-8edd2cf1-426f4876-b548b521-53ef10ec00c2b82d6e5f4453"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | | ||
Argument: short and long (if available) forms: | Description of the argument | ||
-f | Source xml file. | ||
-o | Output xml file. | ||
-e | Email of DSpace Administrator. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6bdb9d16cc7cd284-df7b1fdb-47ae4e3b-a6d082e5-0fc0432432603ad331172b7b"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | | ||
Arguments short and (long) forms: | Description | ||
| Add items to DSpace ‡ | ||
| Replace items listed in mapfile ‡ | ||
| Delete items listed in mapfile ‡ | ||
| Source of the items (directory) | ||
| Destination Collection by their Handle or database ID | ||
| Where the mapfile for items can be found (name and directory) | ||
| Email of eperson doing the importing | ||
| Send submission through collection's workflow | ||
| Kicks off the email alerting of the item(s) has(have) been imported | ||
| Test run‚ do not actually import items | ||
| Apply the collection template | ||
| Resume a failed import (Used on Add only) | ||
| Command help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ac5ad4e15e923ad6-520704f8-43904846-83be9ba3-4880af161a452c9cdae83318"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.itemexport.ItemExport | ||
Arguments short and (long) forms: | Description | ||
| Type of export. COLLECTION will inform the program you want the whole collection. ITEM will be only the specific item. (You will actually key in the keywords in all caps. See examples below.) | ||
| The ID or Handle of the Collection or Item to export. | ||
| The destination of where you want the file of items to be placed. You place the path if necessary. | ||
| Sequence number to begin export the items with. Whatever number you give, this will be the name of the first directory created for your export. The layout of the export is the same as you would set your layout for an Import. | ||
| Export the item/collection for migration. This will remove the handle and metadata that will be re-created in the new instance of DSpace. | ||
| Brief Help. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b9524581adbf6575-ac7e4e21-4591429c-941fbe9f-3c7a121e5f918c93960e5f26"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.itemimport.ItemUpdate | ||
Arguments short and (long) forms: | Description | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="daf4bb95606e7c9f-1d659a88-4d664663-ae4e8cd4-83e12d901a0dee752b5c0d9e"><ac:plain-text-body><![CDATA[ | | Repeatable for multiple elements. The metadata element should be in the form dc.x or dc.x.y. The mandatory argument indicates the metadata fields in the dublin_core.xml file to be added unless already present. However, duplicate fields will not be added to the item metadata without warning or error. | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0be8925df68c8367-6a3b1878-4d0e41ce-9fbfa66a-05944059e18f1cac1c7eb667"><ac:plain-text-body><![CDATA[ | | Repeatable for multiple elements. All metadata fields matching the element will be deleted. | ]]></ac:plain-text-body></ac:structured-macro> |
| Adds bitstreams listed in the contents file with the bistream metadata cited there. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5752e6b98f655b2c-c987816c-427a4b06-ae39a059-011d63e10a3596f54433f9f1"><ac:plain-text-body><![CDATA[ | | Not repeatable. With no argument, this operation deletes bistreams listed in the deletes_contents file. Only bitstream ids are recognized identifiers for this operatiotn. The optional filter argument is the classname of an implementation of org.dspace.app.itemdupate.BitstreamFilter class to identify files for deletion or one of the aliases (ORIGINAL, ORIGINAL_AND_DERIVATIVES, TEXT, THUMBNAIL) which reference existing filters based on membership in a bundle of that name. IN this case, the delete_contents file is not required for any item. The filter properties file will contains properties pertinent to the particular filer used. Multiple filters are not allowed. | ]]></ac:plain-text-body></ac:structured-macro> |
| Displays brief command line help. | ||
| Email address of the person or the user's database ID (Required) | ||
| Directory archive to process (Required) | ||
| Specifies an alternate metadata field (not a handle) used to hold an identifier used to match the DSpace item with that in the archive. If omitted, the item handle is expected to be located in the dc.identifier.uri field. (Optional) | ||
| Runs the process in test mode with logging but no changes applied to the DSpace instance. (Optional) | ||
| Prevents any changes to the provenance field to represent changes in the bitstream content resulting from an Add or Delete. No provenance statements are written for thumbnails or text derivative bitstreams, un keepin with the practice of MediaFilterManager. (Optional) | ||
| The filter properties files to be used by the delete bitstreams action (Optional) |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9926e3ef0ab7fae6-a007fc6b-413142c7-a69b8b27-68d2c35437e6c855e89a0acf"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.administer.CommunityFiliator | ||
Arguments short and (long) forms: | Description | ||
| Set a parent/child relationship | ||
| Remove a parent/child relationship | ||
| Child community (Handle or database ID) | ||
| Parent community (Handle or database ID | ||
| Online help. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c293ac2654791a8a-8949d7db-4c4742b7-87af9799-50f262a0cac23b0de46a2851"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataExport | ||
Arguments short and (long) forms): | Description | ||
| Required. The filename of the resulting CSV. | ||
| The Item, Collection, or Community handle or Database ID to export. If not specified, all items will be exported. | ||
| Include all the metadata fields that are not normally changed (e.g. provenance) or those fields you configured in the dspace.cfg to be ignored on export. | ||
| Display the help page. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="61475bd2daeddb46-60e6d935-479b4378-a51d9c10-f6d8547a3310139c69c645bb"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataImport | ||
Arguments short and (long) forms: | Description | ||
| Required. The filename of the CSV file to load. | ||
| Silent mode. The import function does not prompt you to make sure you wish to make the changes. | ||
| The email address of the user. This is only required when adding new items. | ||
| When adding new items, the program will queue the items up to use the Collection Workflow processes. | ||
| when adding new items using a workflow, send notification emails. | ||
| When adding new items, use the Collection template, if it exists. | ||
| Display the brief help page. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="484ddde7e3a5a94f-5f663b08-42a34bae-a9a595a6-b79e2b3477b492afc8cb87b2"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.checker.ChecksumChecker | ||
Arguments short and (long) forms): | Description | ||
| Loop continuously through the bitstreams | ||
| Specify a handle to check | ||
| Space separated list of bitstream IDs | ||
| Check count | ||
| Checking duration | ||
| Calls online help | ||
| Loop once through bitstreams | ||
| Prune old results (optionally using specified properties file for configuration | ||
| Report all processing |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ebaf5a453fa59b88-7465889a-45de4cb2-868caef7-b328ccd1913997018ea7a14f"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.checker.DailyReportEmailer | ||
Arguments short and (long) forms): | Description | ||
| Send all the results (everything specified below) | ||
| Send E-mail report for all bitstreams set as deleted for today. | ||
| Send E-mail report for all bitstreams not found in assetstore for today. | ||
| Send E-mail report for all bitstrems where checksum has been changed for today. | ||
| Send the Unchecked bitstream report. | ||
| Send E-mail report for all bitstreams set to longer be processed for today. | ||
| Help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="bd75202a3ef17899-65a4cc4d-40e842eb-8b249773-96266b5218a74d747a38f689"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.embargo.EmbargoManager | ||
Arguments short and (long) forms): | Description | ||
| ONLY check the state of embargoed Items, do NOT lift any embargoes | ||
| Process ONLY this handle identifier(s), which must be an Item. Can be repeated. | ||
| Only lift embargoes, do NOT check the state of any embargoed items. | ||
| Do no change anything in the data model, print message instead. | ||
| Print a line describing the action taken for each embargoed item found. | ||
| No output except upon error. | ||
| Display brief help screen. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c8713169eb61d9f2-ad2b5151-4387484b-9c73b17f-7f7989446ff821036c09e38f"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace index-init | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.browse.IndexBrowse | ||
Arguments short and long forms): | Description | ||
r or -rebuild | Should we rebuild all the indexes, which removes old tables and creates new ones. For use with -f. Mutually exclusive with -d | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9fd799090b7f424f-a3402863-4af34794-84f5a682-94e8a19a279fe192db7b4433"><ac:plain-text-body><![CDATA[ | s or -start | [-s <int>] _start from this index number and work upwards (mostly only useful for debugging). For use with _-t and -f | ]]></ac:plain-text-body></ac:structured-macro> |
x or -execute | Execute all the remove and create SQL against the database. For use with -t _and _-f | ||
i or -index | Actually do the indexing. Mutually exclusive with -t and -f. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2fb43fd62d080113-5115a571-46254a51-9bcaa6ee-671ccf3093f8c8f18a9e5ee1"><ac:plain-text-body><![CDATA[ | o or -out | [-o<filename>] write the remove and create SQL to the given file. For use with -t and -f | ]]></ac:plain-text-body></ac:structured-macro> |
p or -print | Write the remove and create SQL to the stdout. For use with -t and -f. | ||
t or -tables | Create the tables only, do no attempt to index. Mutually exclusive with -f and -i | ||
f or -full | Make the tables, and do the indexing. This forces -x. Mutually exclusive with -f and -i. | ||
v or -verbose | Print extra information to the stdout. If used in conjunction with -p, you cannot use the stdout to generate your database structure. | ||
d or -delete | Delete all the indexes, but do not create new ones. For use with -f. This is mutually exclusive with -r. | ||
h or -help | Show this help documentation. Overrides all other arguments. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ec7cb42c23bf48fe-6733dfe6-40cf4782-91d6ad9f-8a6fe36102e640753cc5553b"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace stats-log-converter | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.statistics.util.ClassicDSpaceLogConverter | ||
Arguments short and long forms): | Description | ||
i or -in | Input file | ||
o or -out | Output file | ||
m or -multiple | Adds a wildcard at the end of input and output, so it would mean dspace.log* would be converted. (For example, the following files would be included because of this argument: dspace.log, dspace.log.1, dspace.log.2, dspace.log.3, etc.) | ||
n or -newformat | If the log files have been created with DSpace 1.6 | ||
v or -verbose | Display verbose ouput (helpful for debugging) | ||
h or -help | Help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2ae35f127bcc1d32-76399de3-4f354ac2-a50d8b0e-2d315d9fb959425c40e28f0d"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace stats-log-importer | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.statistics.util.StatisticsImporter | ||
Arguments (short and long forms): | Description | ||
i or - | input file | ||
m or - | Adds a wildcard at the end of the input, so it would mean dspace.log* would be imported | ||
s or - | To skip the reverse DNS lookups that work out where a user is from. (The DNS lookup finds the inforamtion about the host from its IP addess, such as geographical location, etc. This can be slow, and wouldn't work on a server not connected to the internet.) | ||
v or - | Display verbose ouput (helpful for debugging) | ||
l or - | For developers: allows you to import a log file from another system, so because the handles won't exist, it looks up random items in your local system to add hits to instead. | ||
h or - | Help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d9996bdee75c3e35-175f612a-4beb4e37-807ab6db-d678c7857ec323629eee92b8"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace stats-util | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.statistics.util.StatisticsClient | ||
Arguments (short and long forms): | Description | ||
u or -update-spider-files | Update Spider IP Files from internet into /dspace/config/spiders. Downloads Spider files identified in dspace.cfg under property | ||
f or -delete-spiders-by-flag | Delete Spiders in Solr By isBot Flag. Will prune out all records that have isBot:true | ||
i or -delete-spiders-by-ip | Delete Spiders in Solr By IP Address. Will prune out all records that have IP's that match spider IPs. | ||
m or -mark-spiders | Update isBog Flag in Solr. Marks any records currently stored in statistics that have IP addresses matched in spiders files | ||
h or -help | Calls up this brief help table at CLI. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5eee2468df0879d6-e9d62bf9-4be44718-bd80ab1e-1bb11b67e130121e0c07864a"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace test-database | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.storage.rdbms.DatabaseManager | ||
Arguments (short and long forms): | Description | ||
or - | There are no arguments used at this time. |
Moving items
It is possible for administrators to move items one at a time using either the JSPUI or the XMLUI. When editing an item, on the 'Edit item' screen select the 'Move Item' option. To move the item, select the new collection for the item to appear in. When the item is moved, it will take its authorizations (who can READ / WRITE it) with it.
If you wish for the item to take on the default authorizations of the destination collection, tick the 'Inherit default policies of destination collection' checkbox. This is useful if you are moving an item from a private collection to a public collection, or from a public collection to a private collection.
- Note: When selecting the 'Inherit default policies of destination collection' option, ensure that this will not override system-managed authorizations such as those imposed by the embargo system.