Hi,
We found it was a bitstream duplication... Here's the solution:
http://dspace.2283337.n4.nabble.com/Error-when-exporting-site-because-of-ID-quot-bitstream-2-quot-already-exists-td4680373.html
miercuri, 17 aprilie 2019, 23:27:55 UTC+3, Liviu Petcu a scris:
>
> Hi,
> We tried
Hi,
We tried to export the site (DSpace 6.0) as follows:
/dspace/bin/dspace packager -a -d -t AIP -e user@repo -i 123456789/0
123456789-0.zip
The result was the following error:
Exception: Error exporting METS for DSpace Object, type=ITEM,
handle=123456789/5547, dbID=c1f08fcd-bf21-4aee-8085-99
omedspace/assetstore
for i in `cat $homedspace/internal_id.txt`;
do
bitstr="$assetd/$i"
if [ ! -f $fbitstr ]; then
echo "$i"
fi;
done
I hope this can helps somebody...
luni, 15 aprilie 2019, 10:08:38 UTC+3, Liviu Petcu a scris:
>
> Hi,
>
> I have tried to e
Hi,
I have tried to export a collection using packager:
dspace packager -a -d -t AIP -e user@myrepo -i 123456789/2594
/home/dspace/123456789-2594.zip
but this fails with this message:
Disseminating DSpace COLLECTION [ hdl=123456789/2594 ] to
/home/dspace/123456789-2594.zip
Also disseminating
2019, 23:24:32 UTC+3, Liviu Petcu a scris:
>
> Hi,
>
> After reinstalling DSpace, we found that after I had made index-descovery, in
> authors browsing there are also authority keys.
> I checked the database and found that those authority keys correspond to
> items whose ite
there are many such records (1600).
Thank you.
Liviu Petcu
DSpace version: 6.0
Postgresql 9.6
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to
y4jesACa_O4F_Si30v-kolA>
>
> Good luck
> On 15/03/2019 10:59, Liviu Petcu wrote:
>
> Hello,
> I would need some advice because at this moment our Dspace 6.0, seems to be
> affected (at least) by the DS-3157
> <https://jira.duraspace.org/browse/DS-3157> bug.
> T
y date).
There is a way to solve these issues?
Thank you.
Liviu Petcu
DSpace version: 6.0
SCM revision: 0fea17436854acf9048b0e11fbf988333ea02956
SCM branch: UNKNOWN
OS: Linux(amd64) version 3.10.0-514.6.1.el7.x86_64
Discovery: enabled.
JRE: Oracle Corpo
a] at
org.apache.commons.lang.text.StrSubstitutor.checkCyclicSubstitution(StrSubstitutor.java:701)
All configs was updated before mvn build in
[dspace-src)/dspace/config/dspace.cfg (and local.cfg also).
What should I do to get the CRIS installation done?
Thanks,
Liviu Petcu
--
All messages to this mailing
