Date: Thu, 28 Mar 2024 13:02:39 -0400 (EDT) Message-ID: <2014636924.28419.1711645359831@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28418_305098906.1711645359831" ------=_Part_28418_305098906.1711645359831 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The purpose of this section is to describe the Export/Import (Ex= cel 97/2003=E2=80=93xls) web functionalities and the format of Excel = document necessary for ingesting (also used for export) in DSpa= ce-CRIS.
The export functionality is available on Administrative section of DSpac= e-CRIS at:
<dspace-url>/cris/administrator/= index.htm
The export page shows two boxes to set the query and the entity type of = the entities used for export. You can choose only one entity type of = DSpace-CRIS per export (e.g. you can export ResearcherPage in the single ex= port but not ResearcherPage and OrganizationUnit together; To export the fu= ll repository needs to export one by one the entities type).
The export is available also via batch script:
dspace = dsrun org.dspace.app.cris.batch.ScriptCrisBulkExport -e <rp|pj|ou|events= |journals|..> -f <export_destination_file>
The import functionality is available on Administrative section of DSpac= e-CRIS (like export) and via Batch Script:
dspace = dsrun org.dspace.app.cris.batch.ScriptCrisBulkChanges -e <rp|pj|ou|event= s|journals|..> -f <export_source_file>
The web page shows two boxes to setup the import with the entity type an= d the file to import. The batch script also uses the same options, launch i= t with =E2=80=93h for other information.
The document (both for export and import) contains two sheets:
Main entities Sheet:
The first four columns are the same in all exported type of entities (
The nested_entities sheet contains the nested object owned by t= he object defined in main_entities sheet. In fact the first three = columns are CRISID_PARENT, SOURCEREF_PARENT, SOURCEID_PARENT that are related to the entity contain= ed in the main_entities sheet. The system during the ingest proces= s will process first the main_entities sheet and then the nested_entities s= heet, in order to make available the parent object when importing the neste= d objects. The other three columns UUID, SOURCEREF, SOURCEID are mandatory for the file structure. The other columns depend on the sp= ecific nested entity configuration.
Only import needs an ACTION and a NONE= column to manipulate the entities. Below is the list of possible actions:<= /p>
CREATE, UPDATE, DELETE, HIDE, SHOW
Note that ACTION column MUST be the fi= rst column of the main_entities sheet and NONE column the last, the NONE column must be filled with= '#' for all entities .
*Please note that if you don=E2=80=99t want modify a metadata you ca= n remove the column from the excel file for import, but please make attenti= on because do not recognize the column with a new type of metadata not pres= ent in the DSpace-CRIS at moment of the import
**Please note that this action works in append mode this mean= s that if you export an entity and add the action column with HIDE/SHOW it = will double every metadata (except for the related nested object that works= different). If you want just to change the visibility of the entity you sh= ould blank the cells and make action with HIDE/SHOW value
***Please note that to remove only nested you have to empties all ce= lls related to the nested row except identifiers column from (column from A= to F in the Nested Entities Sheet).
KNOWN ISSUE: https://github.com/4Science/DSpa=
ce/issues/14 and https://github.com/4Science/DSp=
ace/issues/13
Below there are the requirements for the values in the cells:
[visibi= lity=3D<ATTRIBUTE> URL=3D<ATTRIBUTE>]<VALUE>
ATTRIBUTE:
VALUE:
Example:
[visibi= lity=3DPUBLIC URL=3Dhttp://www.personalpage.com /~mypage/]Personal Page
[visibi= lity=3D<ATTRIBUTE> CRISID=3D<ATTRIBUTE> SOURCEID=3D <ATTRIBU= TE> SOURCEREF=3D<ATTRIBUTE> UUID=3D<ATTRIBUTE>]<VALUE>=
ATTRIBUTE:
NOTE that the UUID or CRISID or the couple SOURCEID/SOURCEREF are ma= ndatory in order to create the relationship.
VALUE:
Example:
[visibi= lity=3DPUBLIC CRISID=3Dou00024 SOURCEID=3D1 SOURCEREF=3Dexternal-database]D= epartment of Logistics and Maritime Studies
[visibi= lity=3D<ATTRIBUTE>LOCAL=3D<ATTRIBUTE>]<VALUE>
ATTRIBUTE:
VALUE:
*Please note that if local attribute is false then the file will be = retrieved from the local absolute path on server machine
**Please note that the path MUST be visible to the user that launch = the batch script or the Tomcat users
Example:
[visibility=3DPUBLIC LOCAL=3Dfalse]/path_to_file /image.jpg
[visibi= lity=3D<ATTRIBUTE>]<VALUE>
VALUE: