Page History
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="94ec8781ca32bdda-33a5bd5c-4cdc4977-94eba599-c78b621dbbee6c3195be2e99"><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. |
...
The above example will display the normal help message, while also listing any additional options available to the "METS" packager plugin.
Ingesting
To ingest a package from a file, give the command:
| Code Block |
|---|
[dspace]/bin/packager -e user -c handle -t packagerpath |
Where _user_ is the e-mail address of the E-Person under whose authority this runs; _handle_ is the Handle of the collection into which the Item is added, _packager_ is the plugin name of the package ingester to use, and _path_ is the path to the file to ingest (or "-" to read from the standard input).
Here is an example that loads a PDF file with internal metadata as a package:
/dspace/bin/packager -e florey@mit.edu -c 1721.2/13 -t pdf thesis.pdf
This example takes the result of retrieving a URL and ingests it:
...
Ingestion Modes & Options
When ingesting packages DSpace supports several different "modes". (Please note that not all packager plugins may support all modes of ingestion)
- Submit/Ingest Mode (
-soption, default) – submit package to DSpace in order to create a new object(s) - Restore Mode (
-roption) – restore pre-existing object(s) in DSpace based on package(s). This also attempts to restore all handles and relationships (parent/child objects). This is a specialized type of "submit", where the object is created with a known Handle and known relationships. - Replace Mode (
-r -foption) – replace existing object(s) in DSpace based on package(s). This also attempts to restore all handles and relationships (parent/child objects). This is a specialized type of "restore" where the contents of existing object(s) is replaced by the contents in the AIP(s). By default, if a normal "restore" finds the object already exists, it will back out (i.e. rollback all changes) and report which object already exists.
Ingesting a Single Package
To ingest a single package from a file, give the command:
| Code Block |
|---|
[dspace]/bin/dspace packager -e [user-email] -p [parent-handle] -t [packager-name] /full/path/to/package |
Where user-email is the e-mail address of the E-Person under whose authority this runs; parent-handle is the Handle of the Parent Object into which the package is ingested, packager-name is the plugin name of the package ingester to use, and /full/path/to/package is the path to the file to ingest (or "-" to read from the standard input).
Here is an example that loads a PDF file with internal metadata as a package:
| Code Block |
|---|
[dspace]/bin/dspace packager -e florey@mit.edu -p 1721.2/13 -t PDF thesis.pdf |
This example takes the result of retrieving a URL and ingests it:
| Code Block |
|---|
wget -O - http://alum.mit.edu/jarandom/my-thesis.pdf | [dspace]/bin/dspace packager -e florey@mit.edu -c 1721.2/13 -t pdf - |
Ingesting Multiple Packages at Once
Some Packager plugins support bulk ingest functionality using the --all (or -a) flag. When --all is used, the packager will attempt to ingest all child packages referenced by the initial package (and continue on recursively). Some examples follow:
- For a Site-based package - this would ingest all Communities, Collections & Items based on the located package files
- For a Community-based packag - this would ingest that Community and all SubCommunities, Collections and Items based on the located package files
- For a Collection - this would ingest that Collection and all contained Items based on the located package files
- For an Item – this just ingest the Item (including all Bitstreams & Bundles) based on the package file.
Here is a basic example of a bulk ingest 'packager' command template:
| Code Block |
|---|
[dspace]/bin/dspace packager -s -a -t AIP -e <eperson> -p <parent-handle> <file-path>
|
for example:
| Code Block |
|---|
[dspace]/bin/dspace packager -s -a -t AIP -e admin@myu.edu -p 4321/12 collection-aip.zip
|
The above command will ingest the package named "collection-aip.zip" as a child of the specified Parent Object (handle="4321/12"). The resulting object is assigned a new Handle (since -s is specified). In addition, any child packages directly referenced by "collection-aip.zip" are also recursively ingested (a new Handle is also assigned for each child AIP).
| Note | ||
|---|---|---|
| ||
Because the packager plugin must know how to locate all child packages from an initial package file, not all plugins can support bulk ingest. Currently, in DSpace the following Packager Plugins support bulk ingest capabilities:
|
Restoring/Replacing using Packages
Restoring is slightly different than just ingesting. When restoring, the packager makes every attempt to restore the object as it used to be (including its handle, parent object, etc.).
There are currently three restore modes:
- Default Restore Mode (
-r) = Attempt to restore object (and optionally children). Rollback all changes if any object is found to already exist. - Restore, Keep Existing Mode (
-r -k) = Attempt to restore object (and optionally children). If an object is found to already exist, skip over it (and all children objects), and continue to restore all other non-existing objects. - Force Replace Mode (
-r -f) = Restore an object (and optionally children) and overwrite any existing objects in DSpace. Therefore, if an object is found to already exist in DSpace, its contents are replaced by the contents of the package. WARNING: This mode is potentially dangerous as it will permanently destroy any object contents that do not currently exist in the package. You may want to first perform a backup, unless you are sure you know what you are doing!
Default Restore Mode
By default, the restore mode (-r option) will rollback all changes if any object is found to already exist. The user will be informed if which object already exists within their DSpace installation.
Use this 'packager' command template:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -t AIP -e <eperson> <file-path>
|
For example:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -t AIP -e admin@myu.edu aip4567.zip
|
Notice that unlike -s option (for submission/ingesting), the -r option does not require the Parent Object (-p option) to be specified if it can be determined from the package itself.
In the above example, the package "aip4567.zip" is restored to the DSpace installation with the Handle provided within the package itself (and added as a child of the parent object specified within the package itself). If the object is found to already exist, all changes are rolled back (i.e. nothing is restored to DSpace)
Restore, Keep Existing Mode
When the "Keep Existing" flag (-k option) is specified, the restore will attempt to skip over any objects found to already exist. It will report to the user that the object was found to exist (and was not modified or changed). It will then continue to restore all objects which do not already exist. This flag is most useful when attempting a bulk restore (using the --all (or -a) option.
One special case to note: If a Collection or Community is found to already exist, its child objects are also skipped over. So, this mode will not auto-restore items to an existing Collection.
Here's an example of how to use this 'packager' command:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -a -k -t AIP -e <eperson> <file-path>
|
For example:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -a -k -t AIP -e admin@myu.edu aip4567.zip
|
In the above example, the package "aip4567.zip" is restored to the DSpace installation with the Handle provided within the package itself (and added as a child of the parent object specified within the package itself). In addition, any child packages referenced by "aip4567.zip" are also recursively restored (the -a option specifies to also restore all child pacakges). They are also restored with the Handles & Parent Objects provided with their package. If any object is found to already exist, it is skipped over (child objects are also skipped). All non-existing objects are restored.
Force Replace Mode
When the "Force Replace" flag (-f option) is specified, the restore will overwrite any objects found to already exist in DSpace. In other words, existing content is deleted and then replaced by the contents of the package(s).
| Warning | ||
|---|---|---|
| ||
Because this mode actually destroys existing content in DSpace, it is potentially dangerous and may result in data loss! It is recommended to always perform a full backup (assetstore files & database) before attempting to replace any existing object(s) in DSpace. |
Here's an example of how to use this 'packager' command:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -f -t AIP -e <eperson> <file-path>
|
For example:
| Code Block |
|---|
[dspace]/bin/dspace packager -r -f -t AIP -e admin@myu.edu aip4567.zip
|
In the above example, the package "aip4567.zip" is restored to the DSpace installation with the Handle provided within the package itself (and added as a child of the parent object specified within the package itself). In addition, any child packages referenced by "aip4567.zip" are also recursively ingested. They are also restored with the Handles & Parent Objects provided with their package. If any object is found to already exist, its contents are replaced by the contents of the appropriate package.
If any error occurs, the script attempts to rollback the entire replacement process.
...
Disseminating
To disseminate an Item as a package, give the command:
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b4895894c6fdaa4f-d6a4be89-44f54a27-9280a044-81ccf8229653eec343cfc083"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace import | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.itemimport.ItemImport | ||
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="e8e2c89f236bfca7-e86764e7-4562472f-9c8c8a06-6ef8a1a11617cf589f3e1071"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace export | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.itemexport.ItemExport | ||
Arguments short and (long) forms: | Description | ||
t or -type | 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.) | ||
i or -ed | The ID or Handle of the Collection or Item to export. | ||
d or -dest | The destination of where you want the file of items to be placed. You place the path if necessary. | ||
n or -number | 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. | ||
m or -migrate | Export the item/collection for migration. This will remove the handle and metadata that will be re-created in the new instance of DSpace. | ||
h or -help | Brief Help. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="776945cf6a5923cc-b089b74a-4a61415a-b78eb9d7-eb0b45225eeb9a2ac5f4e614"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace itemupdate | ]]></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="37ccc3f66e2a179c-99c38ea6-48484be7-b67eb1ec-50c60ce8e7770c28ba0b71c5"><ac:plain-text-body><![CDATA[ | a or -addmetadata [metadata element] | 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="2ac359a23ae37d98-733d7771-4f03400b-b458b3d8-d967b90f8e35f92c4a7b4696"><ac:plain-text-body><![CDATA[ | d or -deletemetadata [metadata element] | Repeatable for multiple elements. All metadata fields matching the element will be deleted. | ]]></ac:plain-text-body></ac:structured-macro> |
A or -addbitstream | 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="26431a0245f253af-f6bc1d7e-44184b8f-b17b9106-32d44573ad0585e7e6c234fe"><ac:plain-text-body><![CDATA[ | D or -deletebitstream [filter plug classname or alis] | 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> |
h or -help | Displays brief command line help. | ||
e or -eperson | Email address of the person or the user's database ID (Required) | ||
s or -source | Directory archive to process (Required) | ||
i or -itemidentifier | 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) | ||
t or -test | Runs the process in test mode with logging but no changes applied to the DSpace instance. (Optional) | ||
P or -alterprovenance | 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) | ||
F or -filterproperties | 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="8f6f2fcc124f3eb0-ec7d8ef5-420f4519-bed495da-b53573ea882dad60217bb1fd"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace mets-export | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.mets.METSExport | ||
Arguments short and (long) forms: | Description | ||
a or -all | Export all items in the archive. | ||
c or -collection | Handle of the collection to export. | ||
d or -destination | Destination directory. | ||
i or -item | Handle of the item to export. | ||
h or -help | Help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b46247da0becf826-72b5204e-43114390-9b349ac7-d72b3fd3804f8ac5ba24a401"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace community-filiator | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.administer.CommunityFiliator | ||
Arguments short and (long) forms: | Description | ||
s or -set | Set a parent/child relationship | ||
r or -remove | Remove a parent/child relationship | ||
c or -child | Child community (Handle or database ID) | ||
p or -parent | Parent community (Handle or database ID | ||
h or -help | Online help. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="bd05764fd84af6bb-35bffff2-46274691-b24aaff2-1ca402c9491373add0a35bcf"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace metadata-export | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataExport | ||
Arguments short and (long) forms): | Description | ||
f or -file | Required. The filename of the resulting CSV. | ||
i or -id | The Item, Collection, or Community handle or Database ID to export. If not specified, all items will be exported. | ||
a or -all | 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. | ||
h or -help | Display the help page. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a5b39f62e49ccfe5-d1d0af94-4aee44db-840abf42-f08d96b16d08370a5fee8846"><ac:plain-text-body><![CDATA[ | Command used: | _[dspace]_/bin/dspace metadata-import | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataImport | ||
Arguments short and (long) forms: | Description | ||
f or -file | Required. The filename of the CSV file to load. | ||
s or -silent | Silent mode. The import function does not prompt you to make sure you wish to make the changes. | ||
e or -email | The email address of the user. This is only required when adding new items. | ||
w or -workflow | When adding new items, the program will queue the items up to use the Collection Workflow processes. | ||
n or -notify | when adding new items using a workflow, send notification emails. | ||
t or -template | When adding new items, use the Collection template, if it exists. | ||
h or -help | Display the brief help page. |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="18638077c7769202-f1b7fc8a-48a04297-9673a973-f5fa50db68832c705617916f"><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="3abbf83b87ab1f4b-78dac100-4de2469a-85f69a49-e76ea1a913c0568a1e644ad6"><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="7383440fcaedc9a4-c96a68e2-4cbb4990-954ba0cc-8f799aa90dec8f21d81c3e22"><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="2ff5d14269a57dfe-d26c2558-450d43b8-8bdbae49-e438b60188209a07f23d59c5"><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="f1dde880044cab64-dd69e882-45134326-bf5c93c1-10d25cba9d8f8f486b5713f2"><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="42a1f450f855ae5d-56ffc4bf-4e90492f-b30a8e6c-071915f82d885329ad0e65c8"><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="fcf8212e794e8ecd-22240d3f-44e14d4b-89e6a252-72d5c392f49709a0e2cc4556"><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="84dbe3507c38f8da-601cb3e6-40484ea4-ac2e9aca-08f1c64de7f46051e1a1ad03"><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="4e6241379e65240c-928295f8-47f641fd-901e8a58-59068ef9cf47a12081cb5e5d"><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="ad30d2fb45367021-f4a15049-46ea43b7-ae33b5b0-e289cf8d2d90f41607ca75d6"><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