Date: Tue, 19 Mar 2024 04:06:00 -0400 (EDT) Message-ID: <1300392042.8689.1710835560912@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8688_849985554.1710835560912" ------=_Part_8688_849985554.1710835560912 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
If you have implemented the Embargo= feature, you will need to run it periodically to check for Items with = expired embargoes and lift them.
Command used: |
|
Java class: |
org.dspace.embargo.EmbargoManager |
Arguments short and (long) forms): |
Description |
| ONLY check the state of embargoed Items, do N= OT 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 o= f any embargoed items. |
| Do no change anything in the data model, prin= t message instead. |
|
Print a line describing the action taken for = each embargoed item found. |
| No output except upon error. |
| Display brief help screen. |
You must run the Embargo Lifter task periodically to check for items wit= h expired embargoes and lift them from being embargoed. For example, to che= ck the status, at the CLI:
[dspace= ]/bin/dspace embargo-lifter -c
To lift the actual embargoes on those items that meet the time criteria,= at the CLI:
[dspace= ]/bin/dspace embargo-lifter -l