Hi Olivier,
These are perfectly safe to remove, assuming you have no need to revert to a
prior deployment. The ant installer backs up your previous deployment in case
something breaks and you want to roll back.
Regards,
James
On 10/25/17, 4:36 AM, "dspace-tech@googlegroups.com on behalf of
Dear Haimanot,
Check in dspace-api/src/main/resources/Messages.properties
A good way to track down files is with the find command. For example, to
search the current directory for “messages.properties” case insensitive you
could use:
find . -iname messages.properties
Best of luck,
James
Dear Haimanot,
The first things to check is your dspace.cfg. If the community list is not
showing, this is a sure sign that the database does not contain those
communities – no solr indexing is required for the hierarchy to show. So get
your db admin to check the database at the address of
Dear Haimanot Birhanu,
Check the wiki documentation here:
https://wiki.duraspace.org/display/DSDOC3x/Discovery
It should tell you all you need to know on this issue.
James
From: on behalf of Haimanot Birhanu
Date: Thursday, December 1,
Dear Haimanot Birhanu,
It looks like the installer is trying to insert a duplicate row of the
application/octet-stream which has short description “Unknown” in the bistream
format registry database table.
If you want to do a fresh install, try using an empty database. You could drop
the
Hi Everybody,
We have an application where our librarians can curate and publish items to our
DSpace 5.4 repository with the REST API. The push is accomplished with a
sequence of requests, first to create the item, then several more requests to
upload some files and set the bundles and
Dear Holly,
We have had success updating the bitstream policies at the bitstream endpoint
rather than the policy endpoint. You can just embed the policy JSON in the
bistream JSON as for example: