For users

This part of wiki is for users of dspace

Uploading files which are bigger than maximum upload size.

• If you want to upload file bigger than maximum upload size you must type the file URL to the following input field:

• Only admin can see this field. NOTE: absolute path to the file must be used
• After typing the file URL and clicking on the Save button there are 3 possibilities:

1. Loading bar near the Save button:

That means that the file is uploading and everything is fine.

2. Error notification:

It's probable that the local metadata field is not updated in the database, you should run dspace database migrate force in the [dspace]/bin. See more: dspace database migrate force

3. Warning and Successful notifications:

It means wrong path path was specified and the file is not updating!

• After uploading you should see the file in the Uploaded files.

Important:

• Do not forget to change upload limit size and timeouts in Nginx (currently the suggest config is https://github.com/ufal/dockerized-nginx-with-shibboleth/blob/19d78a35c841216cd8c33ac9c37103df2c863fbe/nginx/conf/templates/default.conf.template#L74-L83 but check the lastest version)
• Tomcat which is running on Docker could have limited size and therefore attempts to upload big file to /temp directory would fail. In this case, increase size or create new volume.
• If you want to test this functionality, you can:

# inside the dspace container
cd /usr/local/tomcat/temp
fallocate -l 5G big_file.bin
# add the file via gui

The Item Tombstones

NOTE: The admin do not see the tombstone just the Item with the withdrawal message. The Item could have 2 tombstones:

1. If the Item is replaced the User/Anonym see:
2. If the Item is withdrawn without/with the reason the User/Anonym see:

How to add the specific tombstone to the Item.

1. Withdraw the Item

2.1. Replaced tombston:

• Add the new destination to the Items metadata: dc.relation.isreplacedby and dc.description.provenance

2.2. Withdrawn tombstone:

• Add the reason to the Items metadata: local.withdrawn.reason

Manage Handle table

Clarin Dspace use two types of handles: internal handle (url is null) and external handle. You can see them in Manage handles section, which consists from two parts: Handle list, which offers you the basic manipulation functions Create external handle, Edit handle and Delete handle and from Global Actions for changing global prefix.

Handle List

There you can see about each handle:

• handle - persisted identifications
• Internal - Yes/No
• URL - url address referencing to handle
• Resource type - type of handle dspace object
• Resource id - dspace object id

Manage handles

1 Create

1.1 Create internal handle

Internal handle is created automatically, when you create new dspace object (item, collection...). You can see this created handle in the object metadata dc.identifier.uri or in Manage handles section. In internal handle, there is Internal set to Yes and assigned Resource type. Url address isn't specified in this type of handle.

Metadata dc.identifier.uri of item consists from handle

Internal handle

1.2 Create external handle

In Manage handle, there is the button for creating external handle: New external handle. When you click on it, you will see new form consists from two parts: Handle and Url. Each of them is a required field. To create new external handle, you have to click on button Submit. You see this created external handle in list of handles. This handle has field Internal set to No and enter URL. The Resource type and Resource id isn't specified in this type of handle.

The button for creating external handle

Form for creating external handle

External handle

2 Edit

To edit the handle is necessary to mark this handle and push the button Edit handle. You will be redirect to page, where you can edit it.

The button for editing handle

2.1 Edit internal handle

You can see handle, Resource type and Resource id of modified handle. You can edit only handle. Other fields are read-only. There is the option that allow you to archive handle: Archive handle?. When you mark it, it creates new external handle with old handle and url. This url redirects you to edited handle. Old uri of that changed handle after archive which dspace object is Item, you can see in handle metadata dc.identifier.other too.

For for editing the internal handle

Edited handle and new handle created by archiving

Metadata dc.idetifier.other in item

2.2 Edit external handle

You can see Handle and URL of modified handle. There is option to archive handle too. When you mark it, a new external handle will be created with old handle and url, which redirect you to set handle.

Form for editing the external handle

Edited handle and new handle created by archiving

3 Delete

For deleting handle you have to mark this handle and push button Delete. When you do this operation, you have to be very carefull! You delete handle only from handle table. There will be still dspace object, whose uri will consist from this handle .But the redirection to this uri will not work.

The button for deleting handle

The redirection on the uri consists of from deleted handle

Global Actions

You can change global prefix by clicking on button Change handle prefix. You will see form consists from Old prefix and New prefix. Old prefix represents current global prefix and New prefix represents global prefix, which you want to set up. When you mark option Archive old handles?, it will create new external handles with old handle prefix. Them urls will redirect you to new created handles with new handle prefix.

The button for changing global prefix

Form for changing global prefix

Add featured services into Item

• The featured services are showed in the Item refbox:

1. Go to the Item Edit page
2. Add a new metadata to the Item in the format local.featuredService.<FEATURED_SERVICE_NAME>, value must be in the format <COUNTRY>|<SERVICE_URL>. Example: