Page History
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1cbea54008a175de-fb41becd-48b44999-986eb968-be7f439ea7ec668b49dd5225"><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="5c647aec7a9a9634-f40c4cb3-41f44dc3-97ea99f3-52f0a789b94d6450053ea50f"><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 run‚ do not actually import items | ||
| Apply the collection template | ||
| Resume a failed import (Used on Add only) | ||
| Command help |
...
- eperson
- Collection ID (either Handle (e.g. 123456789/14) or Database ID (e.g. 2)
- Source directory where the items reside
- Mapfile. Since you don't have one, you need to determine where it will be (e.g. /Import/Col_14/mapfile)
At the command line:
| Code Block |
|---|
[dspace]/bin/dspace import --add --eperson=joe@user.com --collection=CollectionID --source=items_dir --mapfile=mapfile |
or by using the short form:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
-a |
...
-e joe@user.com |
...
-c CollectionID |
...
-s items_dir |
...
-m mapfile |
...
The above command would cycle through the archive directory's items, import them, and then generate a map file which stores the mapping of item directories to item handles. SAVE THIS MAP FILE. Using the map file you can use it for replacing or deleting (unimporting) the file.
Testing. You can add --test (or -t) to the command to simulate the entire import process without actually doing the import. This is extremely useful for verifying your import files before doing the actual import.
...
Replacing existing items is relatively easy. Remember that mapfile you were supposed to save? Now you will use it. The command (in short form):Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
-r |
...
-e joe@user.com |
...
-c collectionID |
...
-s items_dir |
...
-m mapfile |
...
Long form:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
--replace |
...
--eperson=joe@user.com |
...
--collection=collectionID |
...
--source=items_dire |
...
--mapfile=mapfile |
...
Deleting or Unimporting Items in a Collection
You are able to unimport or delete items provided you have the mapfile. Remember that mapfile you were supposed to save? The command is (in short form):Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
-d |
...
-m mapfile |
...
In long form:Wiki Markup
| Code Block |
|---|
[dspace]/bin/dspace import |
...
--delete |
...
--mapfile mapfile |
...
...
Other Options
- Workflow. The importer usually bypasses any workflow assigned to a collection. But add the
--workflow
...
- (
-w
...
- ) argument will route the imported items through the workflow system.
- Templates. If you have templates that have constant data and you wish to apply that data during batch importing, add the
--template
...
- (
-p
...
- ) argument.
- Resume. If, during importing, you have an error and the import is aborted, you can use the
--resume
...
- (
-R
...
- ) flag that you can try to resume the import where you left off after you fix the error.
Exporting Items
The item exporter can export a single item or a collection of items, and creates a DSpace simple archive for each item to be exported.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e838a471a7319c70-030d680e-4c554824-a05f8871-6a8497ae18f68b3690a6c4d4"><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. |
Exporting a Collection
To export a collection's items you type at the CLI:unmigrated-wiki-markup
| Code Block |
|---|
...
[dspace |
...
]/bin/dspace export |
...
--type=COLLECTION |
...
--id=collID |
...
--dest=dest_dir |
...
--number=seq_num |
Short form:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace export |
...
-t COLLECTION |
...
-d CollID or Handle |
...
-d /path/to/destination |
...
-n Some_number |
...
Exporting a Single Item
The keyword COLLECTION means that you intend to export an entire collection. The ID can either be the database ID or the handle. The exporter will begin numbering the simple archives with the sequence number that you supply. To export a single item use the keyword ITEM and give the item ID as an argument:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace export |
...
--type=ITEM |
...
--id=itemID |
...
--dest=dest_dir |
...
--number=seq_num |
...
Short form:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace export |
...
-t ITEM |
...
-i itemID or Handle |
...
-d /path/to/destination |
...
-n some_ |
...
number |
Each exported item will have an additional file in its directory, named 'handle'. This will contain the handle that was assigned to the item, and this file will be read by the importer so that items exported and then imported to another machine will retain the item's original handle.
The -m Arugment Argument
Using the -m argument will export the item/collection and also perform the migration step. It will perform the same process that the next section Transferring Items Between DSpace Instances performs. We recommend that the next section be read in conjunction with this flag being used.
Transferring Items Between DSpace Instances
Migration of Data
Where items are to be moved between DSpace instances (for example from a test DSpace into a production DSpace) the item exporter and item importer can be used in conjunction with a script to assist in this process.
...
- date.accessioned
- date.available
- date.issued
- description.provenance
- format.extent
- format.mimetype
- identifier.uri
In order to avoid duplication of this metadata, run
| Code Block |
|---|
[dspace]/bin/dspace_migrate </path/to/exported item directory> |
prior to running the item importer. This will remove the above metadata items, except for date.issued - if the item has been published or publicly distributed before and identifier.uri - if it is not the handle, from the dublin_core.xml file and remove all handle files. It will then be safe to run the item exporter.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6e30d7443abefc67-7fd11cbe-40554e0e-be168a29-6c67b290a52a5fd36dac3cef"><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="c8264b2d1ddb0d77-25b13bbc-40c541c8-a34e90ef-76204141f515365c4b8ea385"><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="926b01cf1da44871-572be22a-4ad94b74-8a108d6e-e440a346908577a147608a71"><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="31cf45cb00656076-ff00c102-47014eeb-96c19ffd-dcb2e67c182af244a9046bee"><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) |
...
CLI Examples
Adding Metadata:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace itemupdate |
...
-e joe@user.com |
...
-s |
...
[path/to/archive |
...
] |
...
-a dc.description |
...
This will add from your archive the dc element description based on the handle from the URI (since the -i argument wasn't used).
Registering (Not Importing) Bitstreams
...
The command line for registration is just like the one for regular import:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
-a |
...
-e joe@user.com |
...
-c collectionID |
...
-s items_dir |
...
-m mapfile |
...
(or by using the long form)Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace import |
...
--add |
...
--eperson=joe@user.com |
...
--collection=collectionID |
...
--source=items_dir |
...
--map=mapfile |
...
The --workflow and --test flags will function as described in Importing Items.
The --delete flag will function as described in Importing Items but the registered content files will not be removed from storage. See Deleting Registered Items.
The --replace flag will function as described in Importing Items but care should be taken to consider different cases and implications. With old items and new items being registered or ingested normally, there are four combinations or cases to consider. Foremost, an old registered item deleted from DSpace using --replace will not be removed from the storage. See Deleting Registered Items. where is resides. A new item added to DSpace using --replace will be ingested normally or will be registered depending on whether or not it is marked in the contents files with the -r.
Internal Identification and Retrieval of Registered Items
...
The Export Tool
This tool is obsolete, and does not export a complete AIP. It's . Its use is strongly deprecated.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d68bf597926d7e44-cefca4ae-45aa41fa-8b71bd2f-dd0170b02d4a5951808fa84f"><ac:plain-text-body><![CDATA[ | Command used: | _ | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.mets.METSExport | ||
Arguments short and (long) forms: | Description | ||
| Export all items in the archive. | ||
| Handle of the collection to export. | ||
| Destination directory. | ||
| Handle of the item to export. | ||
| Help |
The following are examples of the types of process the METS tool can provide.
Exporting an individual item. From the CLI:Wiki Markup
| Code Block |
|---|
[dspace |
...
] |
...
/bin/dspace mets-export |
...
-i |
...
[handle |
...
] |
...
-d /path/to/destination |
...
Exporting a collection. From the CLI:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace mets-export |
...
-c |
...
[handle |
...
] |
...
-d /path/to/destination |
...
Exporting all the items in DSpace. From the CLI:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace mets-export |
...
-a |
...
-d /path/to/destination |
...
The AIP Format
Note that this tool is deprecated, and the output format is not a true AIP
...
DSpace can apply filters to content/bitstreams, creating new content. Filters are included that extract text for full-text searching, and create thumbnails for items that contain images. The media filters are controlled by the MediaFilterManager which traverses the asset store, invoking the MediaFilter or FormatFilter classes on bitstreams. The media filter plugin configuration filter.plugins in dspace.cfg contains a list of all enabled media/format filter plugins (see Configuring Media Filters for more information). The media filter system is intended to be run from the command line (or regularly as a cron task):
| Code Block |
|---|
[dspace]/bin/dspace filter-media |
With no options, this traverses the asset store, applying media filters to bitstreams, and skipping bitstreams that have already been filtered.
...
DSpace provides an administrative tool‚Äîtool‚ 'CommunityFiliator'‚Äîfor ‚ for managing community sub-structure. Normally this structure seldom changes, but prior to the 1.2 release sub-communities were not supported, so this tool could be used to place existing pre-1.2 communities into a hierarchy. It has two operations, either establishing a community to sub-community relationship, or dis-establishing an existing relationship.
The familiar parent/child metaphor can be used to explain how it works. Every community in DSpace can be either a 'parent' community‚Äîmeaning community‚ meaning it has at least one sub-community, or a 'child' community‚Äîmeaning community‚ meaning it is a sub-community of another community, or both or neither. In these terms, an 'orphan' is a community that lacks a parent (although it can be a parent); 'orphans' are referred to as 'top-level' communities in the DSpace user-interface, since there is no parent community 'above' them. The first operation‚Äîestablishing operation‚ establishing a parent/child relationship - can take place between any community and an orphan. The second operation - removing a parent/child relationship‚Äîwill relationship‚ will make the child an orphan.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="feb4db886a77cfe0-e3821dfe-48b942f3-824eb2c6-3727520efd99b85da4226bba"><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. |
Set a parent/child relationship, issue the following at the CLI:dsrun org.dspace.administer.CommunityFiliator
| Code Block |
|---|
dspace community-filiator --set --parent=parentID --child=childID |
(or using the short form)Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin |
...
/dspace community-filiator |
...
-s |
...
-p parentID |
...
-c childID |
...
where 's' or '-set' means establish a relationship whereby the community identified by the '-p' parameter becomes the parent of the community identified by the '-c' parameter. Both the 'parentID' and 'childID' values may be handles or database IDs.
The reverse operation looks like this:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin |
...
/dspace community-filiator |
...
--remove |
...
--parent=parentID |
...
--child=childID |
...
(or using the short form)Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin |
...
/dspace community-filiator |
...
-r |
...
-p parentID |
...
-c childID |
...
where 'r' or '-remove' means dis-establish the current relationship in which the community identified by 'parentID' is the parent of the community identified by 'childID'. The outcome will be that the 'childID' community will become an orphan, i.e. a top-level community.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f7b3530f105f3b25-9d46e72d-4fec4d77-b9f29a79-470bc87c1591c2abffe1c7ae"><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. |
Exporting Process
To run the batch editing exporter, at the command line:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace metadata-export |
...
-f name_of_file.csv |
...
-i 1023/24 |
...
Example:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace metadata-export |
...
-f /batch_export/col_14.csv |
...
-i /1989.1/24 |
...
In the above example we have requested that a collection, assigned handle '1989.1/24' export the entire collection to the file 'col_14.cvs' found in the '/batch_export' directory.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2dd4145c9e710f02-0363bbc5-4fa446d2-9f65b472-0d029882fff6b9cc2db73326"><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. |
...
To run the batch importer, at the command line:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace metadata-import |
...
-f name_of_file.csv |
...
ExampleWiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace metadata-import |
...
-f /dImport/col_14.csv |
...
If you are wishing to upload new metadata without bistreams, at the command line:Wiki Markup
| Code Block |
|---|
[dspace |
...
]/bin/dspace/metadata-import |
...
-f /dImport/new_file.csv |
...
-e joe@user.com |
...
-w |
...
-n |
...
-t |
...
In the above example we threw in all the arguments. This would add the metadata and engage the workflow, notification, and templates to all be applied to the items that are being added.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="01058cf36fd15a84-4df47277-4c244d6c-bc3a92ff-9ac141caf95785b8556dedbf"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace checker | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.checker.ChecksumChecker | ||
Arguments short and (long) forms): | Description | ||
L or -continuous | Loop continuously through the bitstreams | ||
a or -handle | Specify a handle to check | ||
-b <bitstream-ids> | Space separated list of bitstream IDs | ||
c or -count | Check count | ||
d or -duration | Checking duration | ||
h or -help | Calls online help | ||
l or -looping | Loop once through bitstreams | ||
-p <prune> | Prune old results (optionally using specified properties file for configuration | ||
v or -verbose | Report all processing |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="37aee7b0445a5f24-524095c7-47bf4266-95dc8772-5b8eefbb425abf65ffd007f8"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace checker | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.checker.DailyReportEmailer | ||
Arguments short and (long) forms): | Description | ||
a or -All | Send all the results (everything specified below) | ||
d or -Deleted | Send E-mail report for all bitstreams set as deleted for today. | ||
m or -Missing | Send E-mail report for all bitstreams not found in assetstore for today. | ||
c or -Changed | Send E-mail report for all bitstrems where checksum has been changed for today. | ||
u or -Unchanged | Send the Unchecked bitstream report. | ||
n or -Not Processed | Send E-mail report for all bitstreams set to longer be processed for today. | ||
h or -help | Help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d3e3b8b5d1a5b877-2a208184-4274403c-b8fd8027-b5bd62da051416b2e0a52461"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace embargo-lifter | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.embargo.EmbargoManager | ||
Arguments short and (long) forms): | Description | ||
c or -check | ONLY check the state of embargoed Items, do NOT lift any embargoes | ||
i or -identifier | Process ONLY this handle identifier(s), which must be an Item. Can be repeated. | ||
l or -lift | Only lift embargoes, do NOT check the state of any embargoed items. | ||
n or -dryrun | Do no change anything in the data model, print message instead. | ||
v or -verbose | Print a line describing the action taken for each embargoed item found. | ||
q or -quiet | No output except upon error. | ||
h or -help | Display brief help screen. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6da58729d44bc3cb-3bfb3d43-42434c19-a19c986f-7361fb23630d5d6c37ac83e1"><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="2b2e5b996bd1048d-0944987b-4d3b4cad-ba179e92-1c2c761dbb4b7f366e5a7c36"><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="c05a61b5f2f20417-7c949f7d-42ae4b6d-84149368-9ccd3d3d626e0535ac269263"><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="f5f6a082672a9bb2-ff7414e3-480b4d62-94c98c6a-7ac405fad18382aaf90c5b4d"><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="0a1ebfe46d5d96e3-6d69ba70-4d0a440c-a4248189-b066af055e34dfdaa2be46b4"><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="e1bc9a0c2d187924-8c5e149d-4c584037-9c27af65-3899fd3a96f4231bbbd5fac3"><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="4e7015c0765750c0-27d03c1f-44d34caf-8e429e50-40cb12df41515b0462c5d3f7"><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. |
Overview
Content Tools