[dspace-tech] DSpace 6.2 - statistics maintenance problems

[Evgeni Dimitrov]

I have not done any statistics maintenance for several years. Data is
growing and I did:

1. stopped DSpace and backed up /dspace/DSPACE/solr/statistics/data/

2. optimize:
 ./dspace stats-util -o
SOLR Optimize -- Process Started:1570563559015
Exception: background merge hit exception: _3epm(4.10.4):C5192613
_2nyj(4.10.4):C4234562

The whole exception is in the end

3. split by years:
./dspace stats-util -s
Moving: 437373 into core statistics-2016
Moving: 4822733 into core statistics-2017
Exception: No space left on device
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: No
space left on device

This created directories statistics-2016, statistics-2017 and hundreds of
tempxxx.csv files in the DSPACE/temp directory

4. I deleted the directories and the files. Then DSpace created again
statistics-2017 with some data files in it.

5. I stopped DSpace, deleted statistics-2017,
/dspace/DSPACE/solr/statistics/data/ and restored the initial
/dspace/DSPACE/solr/statistics/data/

6. Now statistics does not work. The log file says
2019-10-09 08:37:21,160 ERROR org.apache.solr.core.CoreContainer @ Error
creating core [statistics]: Error opening new searcher
org.apache.solr.common.SolrException: Error opening new searcher
. . .
Caused by: java.nio.file.NoSuchFileException:
/dspace/DSPACE/solr/statistics/data/index/segments_21us

My concern is:
1. How to make the statistics work again?

2. How does "stats-util -s" work? I mean - If I provide more disk space for
the DSPACE/temp directory, will this be enough for the "stats-util -s" to
finish successfully? Does it move everything temporarily to DSPACE/temp? Or
should there be space for some overlap of the old statistics and the new
populated statistics-2016, statistics-2017, ...?

Best regards

=== the exception during optimize:
[root@dspace6 bin]# ./dspace stats-util -o
SOLR Optimize -- Process Started:1570563559015
Exception: background merge hit exception: _3epm(4.10.4):C5192613
_2nyj(4.10.4):C4234562 _1yg5(4.10.4):C3952629 _xme(4.10.2):C2658195
_3yb6(4.10.4):C2239573 _3mtu(4.10.4):C598509 _3hb8(4.10.4):C448155 into
_3ybb [maxNumSegments=1]
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
background merge hit exception: _3epm(4.10.4):C5192613
_2nyj(4.10.4):C4234562 _1yg5(4.10.4):C3952629 _xme(4.10.2):C2658195
_3yb6(4.10.4):C2239573 _3mtu(4.10.4):C598509 _3hb8(4.10.4):C448155 into
_3ybb [maxNumSegments=1]
at
org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
at
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:124)
at
org.apache.solr.client.solrj.SolrServer.optimize(SolrServer.java:204)
at
org.apache.solr.client.solrj.SolrServer.optimize(SolrServer.java:158)
at
org.dspace.statistics.SolrLoggerServiceImpl.optimizeSOLR(SolrLoggerServiceImpl.java:1161)
at
org.dspace.statistics.util.StatisticsClient.main(StatisticsClient.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
[root@dspace6 bin]#

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAJc2bOxVsg%2BxO119A7WqNYHT5kcujgAXZt5vDNWq5gZ_BoBttQ%40mail.gmail.com.

Re: [dspace-tech] Re: Collection Authorization to override Item Authorization

[Evgeni Dimitrov]

I am not sure is this strictly a bug, but this makes move with "inherit 
policies" useless for me:

- the item is submitted to a collection which makes items readable by 
everybody
902 DEFAULT_BITSTREAM_READ Anonymous [Edit]
901 DEFAULT_ITEM_READ Anonymous [Edit]
900 READ Anonymous [Edit]

- then I move the item with "inherit policies" to a collection which makes 
items readable by certain group
906 DEFAULT_BITSTREAM_READ SULRDR [Edit]
904 DEFAULT_ITEM_READ Anonymous [Edit]
903 READ Anonymous [Edit]

The result is - the item becomes readable by everybody and by this group
Policies for Bundle ORIGINAL (b5d2a016-7ff4-45fb-a53c-1b69704ae078)
3441 READ Anonymous [Edit] 
3449 READ SULRDR [Edit] 
Bitstream BK-III-119_t_0001_1.jpg (2aeb18d4-3b80-42b1-aa12-38c228f2f217)
3442 READ Anonymous [Edit] 
3450 READ SULRDR [Edit] 

My workaround is a curate task, which removes the existing policies and 
adds only the policies of the current collection.


On Monday, July 8, 2019 at 7:08:11 PM UTC+3, Tim Donohue wrote:
>
> Hi all,
>
> I was unaware that folks are seeing issues with the "Inherit policies of 
> the destination collection" when moving an Item between Collections.  I'd 
> recommend someone report this to our ticketing system so that we can look 
> for a volunteer to address it:  https://jira.duraspace.org/projects/DS/ .  
> When creating a ticket, please give a step-by-step example of what isn't 
> working, as that will help someone reproduce & debug the issue.
>
> If creating a collection and moving all the items isn't working, you also 
> could use the "Advanced Policy Manager" from the DSpace Admin UI to do a 
> bulk replacement of the policies on those 100 items.  This Advanced Policy 
> Manager isn't the most "user friendly" feature, but it will work to allow 
> you to bulk remove existing policies and bulk add the new ones.  Here's a 
> step-by-step guide that our team wrote for the DSpaceDirect service (hosted 
> by DuraSpace): 
> https://wiki.duraspace.org/display/DSpaceDirectKB/Getting+Started+How-To#GettingStartedHow-To-Bulk/BatchPermissionsChanges(Advanced)
>
> Hopefully that helps give another option on how to resolve this, since it 
> sounds like the inheritance of collection policies when moving items isn't 
> working as expected.
>
> Tim
>
> On Sat, Jul 6, 2019 at 10:00 AM Evgeni Dimitrov  > wrote:
>
>> I think that up to DSpace 6.2 "Inherit policies of the destination 
>> collection" does not work.
>> I don't know how it is in DSpace 6.3.
>>
>>
>> On Friday, July 5, 2019 at 12:11:36 PM UTC+3, Arunendra M. Biswas wrote:
>>>
>>> A reply would be helpful.
>>>
>>> On Wednesday, July 3, 2019 at 7:36:04 PM UTC+5:30, Arunendra M. Biswas 
>>> wrote:
>>>>
>>>> Using Dspace 5.9.
>>>> I created a collection with default authorization and uploaded 100 
>>>> items with the default authorization.
>>>> But then, the client decided to allow the READ policy only and remove 
>>>> the DEFAULT_BITSTREAM_READ policy for Anonymous group.
>>>>
>>>> Reading across the forum, I learnt that the easiest way would be to 
>>>> create another collection with this required authorization and move the 
>>>> 100 
>>>> items from old to this newly created collection, selecting "Inherit 
>>>> policies of the destination collection".
>>>>
>>>> I did, but the older DEFAULT_BITSTREAM_READ policy for Anonymous group 
>>>> did not get overridden. The items can be still opened as Anonymous.
>>>>
>>>> Help please.
>>>>
>>>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspac...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/9cbc95be-ccc0-499a-972c-9a6ac9e45caf%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/9cbc95be-ccc0-499a-972c-9a6ac9e45caf%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/82dda2d0-94ff-486a-9054-06e3cf4a8129%40googlegroups.com.

[dspace-tech] Re: Collection Authorization to override Item Authorization

[Evgeni Dimitrov]

I think that up to DSpace 6.2 "Inherit policies of the destination 
collection" does not work.
I don't know how it is in DSpace 6.3.


On Friday, July 5, 2019 at 12:11:36 PM UTC+3, Arunendra M. Biswas wrote:
>
> A reply would be helpful.
>
> On Wednesday, July 3, 2019 at 7:36:04 PM UTC+5:30, Arunendra M. Biswas 
> wrote:
>>
>> Using Dspace 5.9.
>> I created a collection with default authorization and uploaded 100 items 
>> with the default authorization.
>> But then, the client decided to allow the READ policy only and remove the 
>> DEFAULT_BITSTREAM_READ policy for Anonymous group.
>>
>> Reading across the forum, I learnt that the easiest way would be to 
>> create another collection with this required authorization and move the 100 
>> items from old to this newly created collection, selecting "Inherit 
>> policies of the destination collection".
>>
>> I did, but the older DEFAULT_BITSTREAM_READ policy for Anonymous group 
>> did not get overridden. The items can be still opened as Anonymous.
>>
>> Help please.
>>
>>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9cbc95be-ccc0-499a-972c-9a6ac9e45caf%40googlegroups.com.

[dspace-tech] In 6.2 - how "expensive" is to add / to drop metadata fields local.xxx?

[Evgeni Dimitrov]

I have to migrate a small EPrints repository to a collection in DSpace. I
need some more metadata fields. Like local.contact_email,
local.official_url, ...

Is it enough to add the fields in
...dspace_6.2_src_release/dspace/config/registries/local-types.xml ?

If I add a field and then I drop it or rename it - will this have some
"cost"? When no items are using the field of course.

I will populate the fields either with mets and crosswalk (for the
migration) or with input form (later).

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAJc2bOzSszJ8dZxPr66LXAqVZweNf8Tu6hX9jdoDuY27s-4efg%40mail.gmail.com.

Re: [dspace-tech] Editing a submitted item

[Evgeni Dimitrov]

Yes, it works fine. I gave the user (in a last submission step) only WRITE 
permission on the item. Now the user can edit the metadata (in xmlui). The 
user can not delete the item and can not add/delete bitstreams. And this is 
in DSpace 6.2

Best regards
Evgeni



On Tuesday, February 12, 2019 at 11:56:10 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> To be honest, I don't know whether the UI (either XMLUI or JSPUI) will 
> even provide the user with a link to edit the Item, regardless of whether 
> he/she has Item WRITE permissions.  Originally, both UIs allowed 
> Administrators to edit items.  As noted in my previous message this only 
> began to change in the DSpace 6 JSPUI.
>
> So, that's a long way of saying, you might need to also modify/customize 
> the UI to get this to work.  As this is not a feature that DSpace currently 
> supports out-of-the-box (and I've never tried this before), I don't have 
> any other specific advice I can currently offer.. Hopefully if someone else 
> on this list has experience with this they will speak up.  Otherwise, you 
> could simply try adding an Item WRITE policy and see how the UI reacts to 
> that.
>
> - Tim
>
> On Tue, Feb 12, 2019 at 2:32 PM Evgeni Dimitrov  > wrote:
>
>> Thank you Tim,
>>
>> I am wondering will it work if I add in the end of the submission process 
>> a non-interactive AuthorizationStep?
>> It will add to the item a WRITE policy for the submitter.
>>
>> Best regards
>> Evgeni
>>
>>
>>
>> On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>>
>>> Hello Evgeni,
>>>
>>> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
>>> in the JSPUI when you have Item Versioning enabled. See the documentation 
>>> here: 
>>> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
>>> ) 
>>> <https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly)>
>>>
>>> See also this answer on StackOverflow: 
>>> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>>>  
>>>
>>> I expect this will have broader support in a future version of DSpace 
>>> (possibly even 7.0, but we'll have to see).
>>>
>>> If others have found ways around this, I'd love to hear them. It's 
>>> possible there's workarounds I haven't thought of.
>>>
>>> - Tim
>>>
>>>
>>> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  
>>> wrote:
>>>
>> If a user has "Add" permission for a collection, this user can submit an 
>>>> item to the collection.
>>>> Is there a way to allow this user to edit the metadata of "his" item 
>>>> but no other items in the collection?
>>>> Without changing policies after the submission.
>>>>
>>>> -- 
>>>> 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 the Google 
>>>> Groups "DSpace Technical Support" group.
>>>>
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to dspace-tech...@googlegroups.com.
>>>> To post to this group, send email to dspac...@googlegroups.com.
>>>
>>>
>>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Editing a submitted item

[Evgeni Dimitrov]

Thank you Tim,

I will try and I will let you know if it works.

Best regards
Evgeni


On Tuesday, February 12, 2019 at 11:56:10 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> To be honest, I don't know whether the UI (either XMLUI or JSPUI) will 
> even provide the user with a link to edit the Item, regardless of whether 
> he/she has Item WRITE permissions.  Originally, both UIs allowed 
> Administrators to edit items.  As noted in my previous message this only 
> began to change in the DSpace 6 JSPUI.
>
> So, that's a long way of saying, you might need to also modify/customize 
> the UI to get this to work.  As this is not a feature that DSpace currently 
> supports out-of-the-box (and I've never tried this before), I don't have 
> any other specific advice I can currently offer.. Hopefully if someone else 
> on this list has experience with this they will speak up.  Otherwise, you 
> could simply try adding an Item WRITE policy and see how the UI reacts to 
> that.
>
> - Tim
>
> On Tue, Feb 12, 2019 at 2:32 PM Evgeni Dimitrov  > wrote:
>
>> Thank you Tim,
>>
>> I am wondering will it work if I add in the end of the submission process 
>> a non-interactive AuthorizationStep?
>> It will add to the item a WRITE policy for the submitter.
>>
>> Best regards
>> Evgeni
>>
>>
>>
>> On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>>
>>> Hello Evgeni,
>>>
>>> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
>>> in the JSPUI when you have Item Versioning enabled. See the documentation 
>>> here: 
>>> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
>>> ) 
>>> <https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly)>
>>>
>>> See also this answer on StackOverflow: 
>>> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>>>  
>>>
>>> I expect this will have broader support in a future version of DSpace 
>>> (possibly even 7.0, but we'll have to see).
>>>
>>> If others have found ways around this, I'd love to hear them. It's 
>>> possible there's workarounds I haven't thought of.
>>>
>>> - Tim
>>>
>>>
>>> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  
>>> wrote:
>>>
>> If a user has "Add" permission for a collection, this user can submit an 
>>>> item to the collection.
>>>> Is there a way to allow this user to edit the metadata of "his" item 
>>>> but no other items in the collection?
>>>> Without changing policies after the submission.
>>>>
>>>> -- 
>>>> 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 the Google 
>>>> Groups "DSpace Technical Support" group.
>>>>
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to dspace-tech...@googlegroups.com.
>>>> To post to this group, send email to dspac...@googlegroups.com.
>>>
>>>
>>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Editing a submitted item

[Evgeni Dimitrov]

Thank you Tim,

I am wondering will it work if I add in the end of the submission process a 
non-interactive AuthorizationStep?
It will add to the item a WRITE policy for the submitter.

Best regards
Evgeni


On Tuesday, February 12, 2019 at 5:54:20 PM UTC+2, Tim Donohue wrote:
>
> Hello Evgeni,
>
> Unfortunately, as far as I'm aware, this is only supported in DSpace 6.0 
> in the JSPUI when you have Item Versioning enabled. See the documentation 
> here: 
> https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly
> ) 
> <https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning#ItemLevelVersioning-Allowingsubmitterstoversiontheiritems(JSPUIonly)>
>
> See also this answer on StackOverflow: 
> https://stackoverflow.com/questions/42564072/how-to-define-a-group-policy-that-to-allow-submitters-to-edit-only-yours-items-s
>  
>
> I expect this will have broader support in a future version of DSpace 
> (possibly even 7.0, but we'll have to see).
>
> If others have found ways around this, I'd love to hear them. It's 
> possible there's workarounds I haven't thought of.
>
> - Tim
>
>
> On Tue, Feb 12, 2019 at 4:51 AM Evgeni Dimitrov  > wrote:
>
>> If a user has "Add" permission for a collection, this user can submit an 
>> item to the collection.
>> Is there a way to allow this user to edit the metadata of "his" item but 
>> no other items in the collection?
>> Without changing policies after the submission.
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Editing a submitted item

[Evgeni Dimitrov]

If a user has "Add" permission for a collection, this user can submit an
item to the collection.
Is there a way to allow this user to edit the metadata of "his" item but no
other items in the collection?
Without changing policies after the submission.

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] May this cause problems for the upgrade from 6.2 to 7.x?

[Evgeni Dimitrov]

Thank you Tim,

Best regards
Evgeni


On Monday, November 26, 2018 at 6:22:56 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> As noted in your other email thread about this Solr schema issue, we 
> already have a ticket to fix this.  See: 
> https://jira.duraspace.org/browse/DS-4066 and 
> https://github.com/DSpace/DSpace/pull/2249 
>
> These changes have already been applied to both 6.x (to be released in 
> 6.4) and 7.x.  So, as long as you update your schema in the same way (as 
> that PR) you should see no issues in upgrading to DSpace 7.x (once that is 
> available)
>
> - Tim
>
> On Sat, Nov 24, 2018 at 5:13 PM Evgeni Dimitrov  > wrote:
>
>> In 6.2 in the SOLR statistics schema.xml the field id is declared integer 
>> and the actual content is not integer.
>> This causes some queries like this one
>>
>> q=type:2&
>> fq=-isBot:true&
>> fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5&
>> fq=time:[2018-10-01T00:00:00Z+TO+2018-11-01T00:00:00Z]&
>> rows=0&
>> facet=true&
>> facet.limit=-1&
>> facet.pivot=id,statistics_type&
>> facet.pivot.mincount=1&
>> indent=on
>>
>> to fail.
>>
>> In a test repository I added a new field
>> > required="false" />
>> and a new copyField
>> 
>>
>> Then I ran 
>> dspace solr-reindex-statistics
>>
>> Now the above query works with
>> facet.pivot=idstrng,statistics_type&
>>
>> I am getting one facet for every item with subfacets for view events and 
>> search events.
>>
>> My only question - before doing this with the production repository - is 
>> - may this change of the schema cause problems for the upgrade from 6.2 to 
>> 7.x?
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Statistics query fails in 6.2. May be the ID is expected to be a number??

[Evgeni Dimitrov]

Thank you Tim,

This is very helpful. I will do it.

Best regards
Evgeni

On Monday, November 26, 2018 at 5:48:25 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> Yes, you are correct, the DSpace Solr Statistics Schema was accidentally 
> left as-is between 5.x and 6.x, even though identifiers were changed to 
> UUIDs. This ticket and PR are the fixes that your schema need to work 
> properly for custom queries:
>
> https://jira.duraspace.org/browse/DS-4066
> https://github.com/DSpace/DSpace/pull/2249
>
> These fixes will be released in a 6.4... however, you can also simply 
> update your local schema (see the PR) immediately to fix the main issue.
>
> - Tim
>
> On Thu, Nov 22, 2018 at 9:41 AM Evgeni Dimitrov  > wrote:
>
>> This is in DSpace 6.2
>> The query fails with
>> java.lang.NumberFormatException: For input string: 
>> "025186b3-56fa-4314-9cbb-e951f2bbd467"
>>
>> More of the trace is bellow. Is it possible that it is caused because 
>> SOLR expects the ID to be a number as in 5.x?
>> If this is the case is there a workaround?
>>
>> -
>> 2018-11-22 17:04:39,015 INFO  org.apache.solr.core.SolrCore @ 
>> [statistics] webapp=/solr path=/select 
>> params={q=type:2=-1=id,statistics_type=on=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5=-isBot:true=time:[2018-10-01T00:00:00Z+TO+2018-11-01T00:00:00Z]=0=true=1}
>>  
>> hits=2360 status=500 QTime=1121
>> 2018-11-22 17:04:39,015 ERROR org.apache.solr.servlet.SolrDispatchFilter 
>> @ null:java.lang.NumberFormatException: For input string: 
>> "025186b3-56fa-4314-9cbb-e951f2bbd467"
>> at 
>> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>> at java.lang.Integer.parseInt(Integer.java:580)
>> at java.lang.Integer.valueOf(Integer.java:766)
>> at org.apache.solr.schema.IntField.toObject(IntField.java:92)
>> at org.apache.solr.schema.IntField.toObject(IntField.java:45)
>> at org.apache.solr.schema.FieldType.toObject(FieldType.java:364)
>> at 
>> org.apache.solr.handler.component.PivotFacetProcessor.doPivots(PivotFacetProcessor.java:179)
>> at 
>> org.apache.solr.handler.component.PivotFacetProcessor.processSingle(PivotFacetProcessor.java:143)
>> at 
>> org.apache.solr.handler.component.PivotFacetProcessor.process(PivotFacetProcessor.java:95)
>> at 
>> org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:112)
>> at 
>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:218)
>> at 
>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
>> at org.apache.solr.core.SolrCore.execute(SolrCore.java:1976)
>> at 
>> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777)
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] May this cause problems for the upgrade from 6.2 to 7.x?

[Evgeni Dimitrov]

In 6.2 in the SOLR statistics schema.xml the field id is declared integer
and the actual content is not integer.
This causes some queries like this one

q=type:2&
fq=-isBot:true&
fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5&
fq=time:[2018-10-01T00:00:00Z+TO+2018-11-01T00:00:00Z]&
rows=0&
facet=true&
facet.limit=-1&
facet.pivot=id,statistics_type&
facet.pivot.mincount=1&
indent=on

to fail.

In a test repository I added a new field

and a new copyField


Then I ran
dspace solr-reindex-statistics

Now the above query works with
facet.pivot=idstrng,statistics_type&

I am getting one facet for every item with subfacets for view events and
search events.

My only question - before doing this with the production repository - is -
may this change of the schema cause problems for the upgrade from 6.2 to
7.x?

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Statistics query fails in 6.2. May be the ID is expected to be a number??

[Evgeni Dimitrov]

This is in DSpace 6.2
The query fails with
java.lang.NumberFormatException: For input string:
"025186b3-56fa-4314-9cbb-e951f2bbd467"

More of the trace is bellow. Is it possible that it is caused because SOLR
expects the ID to be a number as in 5.x?
If this is the case is there a workaround?

-
2018-11-22 17:04:39,015 INFO  org.apache.solr.core.SolrCore @ [statistics]
webapp=/solr path=/select
params={q=type:2=-1=id,statistics_type=on=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5=-isBot:true=time:[2018-10-01T00:00:00Z+TO+2018-11-01T00:00:00Z]=0=true=1}
hits=2360 status=500 QTime=1121
2018-11-22 17:04:39,015 ERROR org.apache.solr.servlet.SolrDispatchFilter @
null:java.lang.NumberFormatException: For input string:
"025186b3-56fa-4314-9cbb-e951f2bbd467"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.valueOf(Integer.java:766)
at org.apache.solr.schema.IntField.toObject(IntField.java:92)
at org.apache.solr.schema.IntField.toObject(IntField.java:45)
at org.apache.solr.schema.FieldType.toObject(FieldType.java:364)
at
org.apache.solr.handler.component.PivotFacetProcessor.doPivots(PivotFacetProcessor.java:179)
at
org.apache.solr.handler.component.PivotFacetProcessor.processSingle(PivotFacetProcessor.java:143)
at
org.apache.solr.handler.component.PivotFacetProcessor.process(PivotFacetProcessor.java:95)
at
org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:112)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:218)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1976)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777)

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Number of facets in a SOLR statistics query

[Evgeni Dimitrov]

I found it - it can be done with

facet.mincount=1


On Friday, November 9, 2018 at 10:42:45 AM UTC+2, Evgeni Dimitrov wrote:
>
> Thank you Terry,
>
> The librarians asked for numbers for each of the 500 items in the 
> "community". And the above query gives them. But I don't want to fix the 
> number for facet.limit=600 - to be possible to run the same when the 
> "community" gets bigger. But when I set facet.limit=-1, I get 112000 facets 
> - one for every item in the repository - with zeroes in the items not 
> belonging to this "community". I am looking for a query, which does not 
> depend on the size of the "community" and which returns one facet for every 
> item of the "community" only.
>
> On Thursday, November 8, 2018 at 9:51:26 PM UTC+2, Terry Brady wrote:
>>
>> Evgeni,
>>
>> When I am looking at usage statistics, I tend to facet values by time 
>> rather than by id.
>>
>> The following presentation has some recommended Solr Stats queries that 
>> might be useful to try: 
>> https://gitpitch.com/terrywbrady/TutorialSolrAdmin#/6/1
>> y
>> Terry
>>
>> On Thu, Nov 8, 2018 at 1:30 AM Evgeni Dimitrov  
>> wrote:
>>
>>> This is in DSpace 6.2
>>>
>>> I want to get the usage (view and search, workflow is not used) of all 
>>> items in a small "community".
>>> I use the query
>>>
>>> q=type:2&
>>> fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5&
>>> fq=-isBot:true&
>>> fq=time:[2018-10-01T00:00:00Z TO 2018-11-01T00:00:00Z]&
>>> rows=0&
>>> facet=true&
>>> facet.field=id&
>>> facet.limit=600&
>>> indent=on
>>> 
>>> It works, but I don't want to fix a number for facet.limit. And I set 
>>>
>>> facet.limit=-1  (they say this means unlimited)
>>>
>>> It works again, but it returned 112000 facets, which seems to me a bit 
>>> excessive.
>>>
>>> Is there a better way to get the result?
>>>
>>>
>>> -- 
>>> 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 the Google 
>>> Groups "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to dspace-tech...@googlegroups.com.
>>> To post to this group, send email to dspac...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> Terry Brady
>> Applications Programmer Analyst
>> Georgetown University Library Information Technology
>> https://github.com/terrywbrady/info
>> 425-298-5498 (Seattle, WA)
>>
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Number of facets in a SOLR statistics query

[Evgeni Dimitrov]

Thank you Terry,

The librarians asked for numbers for each of the 500 items in the 
"community". And the above query gives them. But I don't want to fix the 
number for facet.limit=600 - to be possible to run the same when the 
"community" gets bigger. But when I set facet.limit=-1, I get 112000 facets 
- one for every item in the repository - with zeroes in the items not 
belonging to this "community". I am looking for a query, which does not 
depend on the size of the "community" and which returns one facet for every 
item of the "community" only.

On Thursday, November 8, 2018 at 9:51:26 PM UTC+2, Terry Brady wrote:
>
> Evgeni,
>
> When I am looking at usage statistics, I tend to facet values by time 
> rather than by id.
>
> The following presentation has some recommended Solr Stats queries that 
> might be useful to try: 
> https://gitpitch.com/terrywbrady/TutorialSolrAdmin#/6/1
> y
> Terry
>
> On Thu, Nov 8, 2018 at 1:30 AM Evgeni Dimitrov  > wrote:
>
>> This is in DSpace 6.2
>>
>> I want to get the usage (view and search, workflow is not used) of all 
>> items in a small "community".
>> I use the query
>>
>> q=type:2&
>> fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5&
>> fq=-isBot:true&
>> fq=time:[2018-10-01T00:00:00Z TO 2018-11-01T00:00:00Z]&
>> rows=0&
>> facet=true&
>> facet.field=id&
>> facet.limit=600&
>> indent=on
>> 
>> It works, but I don't want to fix a number for facet.limit. And I set 
>>
>> facet.limit=-1  (they say this means unlimited)
>>
>> It works again, but it returned 112000 facets, which seems to me a bit 
>> excessive.
>>
>> Is there a better way to get the result?
>>
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 (Seattle, WA)
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Number of facets in a SOLR statistics query

[Evgeni Dimitrov]

This is in DSpace 6.2

I want to get the usage (view and search, workflow is not used) of all
items in a small "community".
I use the query

q=type:2&
fq=owningComm:94a589a1-33a0-41e3-a83b-f7644db9a1a5&
fq=-isBot:true&
fq=time:[2018-10-01T00:00:00Z TO 2018-11-01T00:00:00Z]&
rows=0&
facet=true&
facet.field=id&
facet.limit=600&
indent=on

It works, but I don't want to fix a number for facet.limit. And I set

facet.limit=-1  (they say this means unlimited)

It works again, but it returned 112000 facets, which seems to me a bit
excessive.

Is there a better way to get the result?

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: I am missing something in the build of DSpace 7

[Evgeni Dimitrov]

Thank you Tim,

It really works with wget.

Best regards
Evgeni

On Tuesday, October 30, 2018 at 6:47:49 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> For the DSpace 7 REST API, the web interface is that "meaningful HTML" 
> page (HAL Browser) that you see. This HTML page lets you form/test out the 
> REST API requests from a web browser.
>
> However, if you want to see the actual JSON responses, then you should use 
> a tool like "wget". For example:
> wget http://localhost:8080/spring-rest/api/core/communities
>
> For what it's worth, I do see that same 500 Response error on our demo 
> site if I put in:
> https://dspace7.4science.it/dspace-spring-rest/api/core/communities 
>
> However, that same URL works fine via "wget" and also works if I enter 
> that URL into the HAL Browser: 
> https://dspace7.4science.it/dspace-spring-rest/#https://dspace7.4science.it/dspace-spring-rest/api/core/communities
>  
>
> So, I think this 500 response might be a minor bug in our pre-DSpace 7 
> codebase. But, it won't affect the performance as long as you are using the 
> Angular UI or HAL Browser or wget.
>
> - Tim
>
> On Tue, Oct 30, 2018 at 10:55 AM Evgeni Dimitrov  > wrote:
>
>> Thank you Tim,
>>
>> It seems the --base-href can be handled in the configuration of webpack 
>> with BaseHrefWebpackPlugin. Or meanwhile the index.html can be edited 
>> manually.
>>
>> But I see a problem with the java side as well. When I enter in the 
>> browser
>>
>> http://localhost:8080/spring-rest
>>
>> I am getting a meaningful html page describing the services. But this is 
>> not what the client can use. When I enter
>>
>> http://localhost:8080/spring-rest/api or
>>
>> http://localhost:8080/spring-rest/api/core/communities
>>
>> the message is
>>
>> This page isn’t working localhost is currently unable to handle this 
>> request. HTTP ERROR 500
>>
>> And I don't see anything in the logs ...
>>
>>
>>
>>
>> On Tuesday, October 30, 2018 at 5:06:18 PM UTC+2, Tim Donohue wrote:
>>
>>> Hi Evgeni,
>>>
>>> At this time, our Production mode build process is not fully worked out 
>>> for the Angular UI.  One of the main reasons is that we do not *yet* 
>>> support the Angular CLI (which provides tools like the "ng build 
>>> --base-href" concept you are looking for).
>>>
>>> However, in the next few weeks, we will be upgrading the Angular UI to 
>>> Angular v6 and Angular CLIso, that will be coming soon.
>>>
>>> In the meantime, if you want to try out / test out the early DSpace 7 
>>> code, we recommend running the Angular UI in development mode, e.g.
>>>
>>> yarn start
>>> (or yarn run watch)
>>>
>>> Then, you should be able to access the UI at http://localhost:3000/
>>>
>>> For more info, see the README at: 
>>> https://github.com/DSpace/dspace-angular#quick-start 
>>>
>>> As for running the REST API, it's build process is the same as the 
>>> DSpace 6 build process.  It sounds like you already figured that out 
>>> though... mvn package , ant fresh_install (or update), and then deploy to 
>>> Tomcat.
>>>
>>> Additional info on getting started with DSpace 7 is in the early 
>>> training resources at 
>>> https://wiki.duraspace.org/display/DSPACE/DSpace+7+Working+Group#DSpace7WorkingGroup-TrainingResources
>>>   
>>>  We also have some early installation notes (constantly being updated) at 
>>> https://wiki.duraspace.org/display/DSPACE/DSpace+7+-+Angular+UI+Development#DSpace7-AngularUIDevelopment-Howtoinstalllocally
>>>  
>>>
>>> Let us know on this list if you are still hitting issues
>>>
>>> Tim
>>>
>>>
>>> On Tue, Oct 30, 2018 at 5:10 AM Evgeni Dimitrov  
>>> wrote:
>>>
>> I mean - somewhere - for yarn or webpack - it should be possible to set 
>>>> something similar to
>>>> ng build --base-href=/dist
>>>> or
>>>> ng build --base-href=/angui
>>>>
>>>>
>>>> On Monday, October 29, 2018 at 9:36:50 PM UTC+2, Evgeni Dimitrov wrote:
>>>>>
>>>>> I want to start it in Tomcat.
>>>>> 1. I downloaded DSpace-master.zip and dspace-angular-master.zip from 
>>>>> github
>>>>> 2. I built the dspace part as usual - maven, ant and deployed to 
>>>>> Tomcat/webapps
>>>>> 3. 

Re: [dspace-tech] Re: I am missing something in the build of DSpace 7

[Evgeni Dimitrov]

Thank you Tim,

It seems the --base-href can be handled in the configuration of webpack 
with BaseHrefWebpackPlugin. Or meanwhile the index.html can be edited 
manually.

But I see a problem with the java side as well. When I enter in the browser

http://localhost:8080/spring-rest

I am getting a meaningful html page describing the services. But this is 
not what the client can use. When I enter

http://localhost:8080/spring-rest/api or

http://localhost:8080/spring-rest/api/core/communities

the message is

This page isn’t working localhost is currently unable to handle this 
request. HTTP ERROR 500

And I don't see anything in the logs ...



On Tuesday, October 30, 2018 at 5:06:18 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> At this time, our Production mode build process is not fully worked out 
> for the Angular UI.  One of the main reasons is that we do not *yet* 
> support the Angular CLI (which provides tools like the "ng build 
> --base-href" concept you are looking for).
>
> However, in the next few weeks, we will be upgrading the Angular UI to 
> Angular v6 and Angular CLIso, that will be coming soon.
>
> In the meantime, if you want to try out / test out the early DSpace 7 
> code, we recommend running the Angular UI in development mode, e.g.
>
> yarn start
> (or yarn run watch)
>
> Then, you should be able to access the UI at http://localhost:3000/
>
> For more info, see the README at: 
> https://github.com/DSpace/dspace-angular#quick-start 
>
> As for running the REST API, it's build process is the same as the DSpace 
> 6 build process.  It sounds like you already figured that out though... mvn 
> package , ant fresh_install (or update), and then deploy to Tomcat.
>
> Additional info on getting started with DSpace 7 is in the early training 
> resources at 
> https://wiki.duraspace.org/display/DSPACE/DSpace+7+Working+Group#DSpace7WorkingGroup-TrainingResources
>   
>  We also have some early installation notes (constantly being updated) at 
> https://wiki.duraspace.org/display/DSPACE/DSpace+7+-+Angular+UI+Development#DSpace7-AngularUIDevelopment-Howtoinstalllocally
>  
>
> Let us know on this list if you are still hitting issues
>
> Tim
>
>
> On Tue, Oct 30, 2018 at 5:10 AM Evgeni Dimitrov  > wrote:
>
>> I mean - somewhere - for yarn or webpack - it should be possible to set 
>> something similar to
>> ng build --base-href=/dist
>> or
>> ng build --base-href=/angui
>>
>>
>> On Monday, October 29, 2018 at 9:36:50 PM UTC+2, Evgeni Dimitrov wrote:
>>>
>>> I want to start it in Tomcat.
>>> 1. I downloaded DSpace-master.zip and dspace-angular-master.zip from 
>>> github
>>> 2. I built the dspace part as usual - maven, ant and deployed to 
>>> Tomcat/webapps
>>> 3. For the angular part I did:
>>>
>>> yarn run global
>>> yarn install
>>> yarn run build:prod
>>>
>>> Before that I changed (perhaps wrongly) in environment.dev.js and 
>>> environment.prod.js
>>>
>>>   // Angular Universal server settings.
>>>   ui: {
>>> ssl: false,
>>> host: 'localhost',
>>> port: 8080,
>>> // NOTE: Space is capitalized because 'namespace' is a reserved 
>>> string in TypeScript
>>> nameSpace: '/dist'
>>>   },
>>>   // The REST API server settings.
>>>   rest: {
>>> ssl: true,
>>> host: 'localhost',
>>> port: 8080,
>>> // NOTE: Space is capitalized because 'namespace' is a reserved 
>>> string in TypeScript
>>> nameSpace: '/spring-rest'
>>>   },
>>>
>>> 4. I started Tomcat and tried http://localhost:8080/dist
>>> The message was that a file is not found at localhost:8080/
>>>
>>> Any suggestions what should be done differently?
>>>
>>>
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon>
>>>  Virus-free. 
>>> www.avast.com 
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link>
>>>  
>>> <#CACKSJ9N1y2Y=kndWS9Dc1BwG2w=LBPqxv2yKr0pMZjpPuKg2fQ@mail.gmail.com_m_-6379266036871596271_m_-7636643062708121379_CAJc2bOyvbN0rjPUa1UBiw68YUY_+JbA92UWq741Og5JvbLQQKA@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>> -- 
>> 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 mess

[dspace-tech] Re: I am missing something in the build of DSpace 7

[Evgeni Dimitrov]

I mean - somewhere - for yarn or webpack - it should be possible to set 
something similar to
ng build --base-href=/dist
or
ng build --base-href=/angui


On Monday, October 29, 2018 at 9:36:50 PM UTC+2, Evgeni Dimitrov wrote:
>
> I want to start it in Tomcat.
> 1. I downloaded DSpace-master.zip and dspace-angular-master.zip from github
> 2. I built the dspace part as usual - maven, ant and deployed to 
> Tomcat/webapps
> 3. For the angular part I did:
>
> yarn run global
> yarn install
> yarn run build:prod
>
> Before that I changed (perhaps wrongly) in environment.dev.js and 
> environment.prod.js
>
>   // Angular Universal server settings.
>   ui: {
> ssl: false,
> host: 'localhost',
> port: 8080,
> // NOTE: Space is capitalized because 'namespace' is a reserved string 
> in TypeScript
> nameSpace: '/dist'
>   },
>   // The REST API server settings.
>   rest: {
> ssl: true,
> host: 'localhost',
> port: 8080,
> // NOTE: Space is capitalized because 'namespace' is a reserved string 
> in TypeScript
> nameSpace: '/spring-rest'
>   },
>
> 4. I started Tomcat and tried http://localhost:8080/dist
> The message was that a file is not found at localhost:8080/
>
> Any suggestions what should be done differently?
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon>
>  Virus-free. 
> www.avast.com 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link>
>  
> <#CAJc2bOyvbN0rjPUa1UBiw68YUY_+JbA92UWq741Og5JvbLQQKA@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] I am missing something in the build of DSpace 7

[Evgeni Dimitrov]

I want to start it in Tomcat.
1. I downloaded DSpace-master.zip and dspace-angular-master.zip from github
2. I built the dspace part as usual - maven, ant and deployed to
Tomcat/webapps
3. For the angular part I did:

yarn run global
yarn install
yarn run build:prod

Before that I changed (perhaps wrongly) in environment.dev.js and
environment.prod.js

  // Angular Universal server settings.
  ui: {
ssl: false,
host: 'localhost',
port: 8080,
// NOTE: Space is capitalized because 'namespace' is a reserved string
in TypeScript
nameSpace: '/dist'
  },
  // The REST API server settings.
  rest: {
ssl: true,
host: 'localhost',
port: 8080,
// NOTE: Space is capitalized because 'namespace' is a reserved string
in TypeScript
nameSpace: '/spring-rest'
  },

4. I started Tomcat and tried http://localhost:8080/dist
The message was that a file is not found at localhost:8080/

Any suggestions what should be done differently?




Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Periodicals in DSpace

[Evgeni Dimitrov]

One issue may be one pdf. One year - one item. All years - one collection.

In my case this works, because:
1. the issues are not too big
2. in the item there is a mets file where the issues are described in the 
structMap. And there is a viewer which shows the item.

This is not a completely standard solution.
If you join some working group you could ask for the introduction of some 
standard interface in DSpace, which allows custom item viewers to be 
attached.


On Saturday, April 28, 2018 at 11:36:17 AM UTC+3, admin wrote:
>
> Hi,
>
> I was wondering if there is any recommended way to handle periodicals in 
> DSpace?
> How to deal with volumes and issues? Should they be separate collections?
> I'd see a need to set up at least every issue as a separate collection 
> (with it's own cover image).
> Apart from collection structure there's also metadata scheme to be 
> introduced into collections/items for periodicals.
>
>
> Thanks, Peter
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] How to edit a bitstream?

[Evgeni Dimitrov]

Thank you Tim,

I really did not know this. But still I don't see why change of the 
filename or the format should affect the authorization policy of the 
bitstream.

Best regards
Evgeni

On Wednesday, August 22, 2018 at 5:09:04 PM UTC+3, Tim Donohue wrote:
>
> Hi Evgeni,
>
> This DS-3979 issue is referring to editing a bitstream's *metadata* (not 
> the actual file associated with the bitstream).  A bitstream's metadata is 
> editable from the UI, but the file itself is not editable (you can only 
> upload a new file).
>
> Here's how you get to the edit a bitstream's metadata in XMLUI:
> * Login, and browse to the Item
> * Edit the Item
> * Click on "Item Bitstreams" tab
> * Click on the Bitstream name. You'll then be on the "Edit Bitstream" page
>
> - Tim
>
> On Wed, Aug 22, 2018 at 4:01 AM Evgeni Dimitrov  > wrote:
>
>> In issue DS-3979 I noticed a comment:
>>
>> Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM
>>
>> Without this in place, if DEFAULT_ITEM_READ is Anonymous and 
>> DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will 
>> add an Anonymous READ policy, making the bitstream public again.
>>
>> I don't know how to "edit a bitstream" and how editing can add a policy 
>> to it. Can somebody shed some light on this?
>>
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] How to edit a bitstream?

[Evgeni Dimitrov]

In issue DS-3979 I noticed a comment:

Chris Herron (Atmire) added a comment - 10/Aug/18 11:52 AM

Without this in place, if DEFAULT_ITEM_READ is Anonymous and
DEFAULT_BITSTREAM_READ is Administrator, then any edit to a bitstream will
add an Anonymous READ policy, making the bitstream public again.

I don't know how to "edit a bitstream" and how editing can add a policy to
it. Can somebody shed some light on this?

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Questions about the checksum checker in DSpace 6.2

[Evgeni Dimitrov]

Hi Tim,

As I understand this fix does not change the main design - first create a 
potentially very large list in memory, second update the DB in one single 
transaction. As I understand this fix promises to make the single 
transaction shorter/faster. One needs a big repository to test the fix and 
to compare. My only big repository is the production one. I can not run 
tests on it.

Best regards
Evgeni


On Wednesday, August 15, 2018 at 10:17:57 PM UTC+3, Tim Donohue wrote:
>
> Just a belated follow-up to this thread.  If you are still hitting issues 
> with the Checksum checker in 6.x, I'd recommend looking at the recently 
> logged bug (and proposed fix): https://jira.duraspace.org/browse/DS-3975
>
> Here's the proposed fix (which could use some testers to help us verify): 
> https://github.com/DSpace/DSpace/pull/2169   If you install the fix, 
> please report back on your findings by adding a comment to either the 
> GitHub PR or the JIRA ticket.  Reviews & reports back from the community 
> can help us to approve & merge fixes more quickly.
>
> Thanks,
>
> Tim
>
> On Thu, Jul 5, 2018 at 9:20 AM Evgeni Dimitrov  > wrote:
>
>> Thank you Mark,
>>
>> I am afraid that the checker first tries to update the 
>> most_recent_checksum table comparing with the bitstream table and only 
>> after that it looks at the options (in my case -c 1000).
>>
>> Which means that it will always first try to add 500 000 rows to 
>> most_recent_checksum table regardless the options.
>>
>>
>> On Thursday, July 5, 2018 at 4:10:19 PM UTC+3, Mark H. Wood wrote:
>>>
>>> On Thursday, July 5, 2018 at 8:20:28 AM UTC-4, Evgeni Dimitrov wrote:
>>>>
>>>>
>>>> Judging by MostRecentChecksumServiceImpl, first a simple List was 
>>>> created in memory with (in this case) 500 000 bitstreams.
>>>>
>>>> Now for every element in this list a row is being added to the 
>>>> most_recent_checksum table. Perhaps the transaction will be committed when 
>>>> all 500 000 rows are added . . . in two weeks time . . .
>>>>
>>>>
>>> I believe that you are correct.  There's a very unfortunate collision of 
>>> Java culture (it's easy to create elastic Collections, don't worry about 
>>> the 500 000 members case), ORM (of course you always want all 500 000 rows 
>>> trapped in one transaction until you are done consuming them sequentially), 
>>> and layers of service/DAO/holder, which makes it difficult to do 
>>> large-scale operations efficiently. We may need to augment the storage 
>>> layer with explicit support for bulk operations, such as the ability to 
>>> pass an arbitrary instance of a bulk-operator interface to be applied 
>>> iteratively to each result of a query, so that code which understands the 
>>> storage model can use it well to avoid memory bloat.  The business logic 
>>> layer does not and should not have access to these storage details.  There 
>>> are a number of places in DSpace which might be made less resource-hungry 
>>> by such means.
>>>
>>> Until this changes, you may wish to look over the checksum checker's 
>>> options for limiting the amount of work that it does.  It can be run for a 
>>> given amount of time or over a specific count of bitstreams, for example, 
>>> and continue where it stopped when run again.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] How to branch in GitHub?

[Evgeni Dimitrov]

Hopefully all done.
Thank you again.

On Friday, August 10, 2018 at 3:55:07 PM UTC+3, helix84 wrote:
>
> On Fri, Aug 10, 2018 at 2:48 PM Evgeni Dimitrov  > wrote:
>
>> Eventually something got very wrong, because the pull request appeared as 
>> request to merge to DSpace:master.
>>
>
> When you're creating a pull request in GitHub, you have to choose the 
> target branch in the GitHub web interface. Please, close the PR and open a 
> new one against the correct branch. There's nothing else we could do with 
> it, either.
>  
>
>> On Friday, August 10, 2018 at 3:19:07 PM UTC+3, Evgeni Dimitrov wrote:
>>>
>>> It worked with
>>>
>>> git checkout upstream/dspace-6_x
>>>
>>
>
> https://stackoverflow.com/questions/10002239/difference-between-git-checkout-track-origin-branch-and-git-checkout-b-branch
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] How to branch in GitHub?

[Evgeni Dimitrov]

Eventually something got very wrong, because the pull request appeared as 
request to merge to DSpace:master.

Sorry...

On Friday, August 10, 2018 at 3:19:07 PM UTC+3, Evgeni Dimitrov wrote:
>
> Thank you,
>
> It worked with
>
> git checkout upstream/dspace-6_x
>
> Best regards
> Evgeni
>
> On Friday, August 10, 2018 at 3:08:26 PM UTC+3, helix84 wrote:
>>
>> Are you following the guide we wrote? This chapter talks about how to set 
>> up a tracking branch:
>>
>>
>> https://wiki.duraspace.org/display/DSPACE/Development+with+Git#DevelopmentwithGit-Option2-%22cherry-pick%22changesfrommastertoreleasebranch
>>
>> That's how you get a branch from upstream repo into your local repo.
>>
>>
>> Regards,
>> ~~helix84
>>
>> Compulsory reading: DSpace Mailing List Etiquette
>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>
>> On Fri, Aug 10, 2018 at 1:56 PM Evgeni Dimitrov  
>> wrote:
>>
>>> Thank you helix84,
>>>
>>> When I did in the beginning
>>>
>>> >git remote add upstream git://github.com/DSpace/DSpace.git
>>> >git fetch upstream
>>> I got:
>>>
>>> remote: Counting objects: 287, done.
>>> remote: Compressing objects: 100% (7/7), done.
>>> Rremote: Total 287 (delta 113), reused 126 (delta 113), pack-reused 160
>>> Receiving objects: 100% (287/287), 38.74 KiB | 0 bytes/s, done.
>>> Resolving deltas: 100% (128/128), completed with 37 local objects.
>>> From git://github.com/DSpace/DSpace
>>>  * [new branch]  dspace-1_2_2-patches -> 
>>> upstream/dspace-1_2_2-patches
>>>  * [new branch]  dspace-1_2_2-update -> upstream/dspace-1_2_2-update
>>>  * [new branch]  dspace-1_4_x -> upstream/dspace-1_4_x
>>>  * [new branch]  dspace-1_5_x -> upstream/dspace-1_5_x
>>>  * [new branch]  dspace-1_6_x -> upstream/dspace-1_6_x
>>>  * [new branch]  dspace-1_7_x -> upstream/dspace-1_7_x
>>>  * [new branch]  dspace-1_8_x -> upstream/dspace-1_8_x
>>>  * [new branch]  dspace-3_x -> upstream/dspace-3_x
>>>  * [new branch]  dspace-4_x -> upstream/dspace-4_x
>>>  * [new branch]  dspace-5_x -> upstream/dspace-5_x
>>>  * [new branch]  dspace-6_x -> upstream/dspace-6_x
>>>  * [new branch]  master -> upstream/master
>>>  * [new branch]  rest-tutorial -> upstream/rest-tutorial
>>>
>>> But now I get:
>>>
>>> D:\ADISK5\dspace-src>git checkout dspace-6_x
>>> error: pathspec 'dspace-6_x' did not match any file(s) known to git.
>>>
>>>
>>>
>>> On Friday, August 10, 2018 at 1:33:14 PM UTC+3, helix84 wrote:
>>>>
>>>> # first switch to the dspace 6 branch:
>>>> git checkout dspace-6_x
>>>> # then create a new identical branch as the current one and name it 
>>>> DS-3974
>>>> git checkout -b DS-3974
>>>>
>>>>
>>>> git remote add upstream git://github.com/DSpace/DSpace.git
>>>> # this was a one-time operation which allows you to pull latest changes 
>>>> from the official DSpace repo to your local repo:
>>>> git pull upstream
>>>> # which is identical to
>>>> git fetch upstream
>>>> git merge upstream
>>>>
>>>>
>>>> Regards,
>>>> ~~helix84
>>>>
>>>> Compulsory reading: DSpace Mailing List Etiquette
>>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>>
>>>> On Fri, Aug 10, 2018 at 10:17 AM Evgeni Dimitrov  
>>>> wrote:
>>>>
>>>>> I want to propose a fix to an issue.
>>>>>
>>>>> What I did:
>>>>>
>>>>> 1. I did Fork in https://github.com/DSpace/DSpace
>>>>>
>>>>> 2. I did clone to my machine:
>>>>> git clone git://github.com/xx/DSpace.git dspace-src
>>>>>
>>>>> 3. I did (don't know why):
>>>>> git remote add upstream git://github.com/DSpace/DSpace.git
>>>>> git fetch upstream
>>>>>
>>>>> What I am trying now is to create a branch for the issue. The issue is 
>>>>> in DSpace 6.3 and I suppose my branch should be a subbranch of dspace-6_x:
>>>>>
>>>>> D:\ADISK5\dspace-src>git checkout -b DS-3974 dspace-6_x
>>>>> fatal: Cannot update paths and switch to b

Re: [dspace-tech] How to branch in GitHub?

[Evgeni Dimitrov]

Thank you,

It worked with

git checkout upstream/dspace-6_x

Best regards
Evgeni

On Friday, August 10, 2018 at 3:08:26 PM UTC+3, helix84 wrote:
>
> Are you following the guide we wrote? This chapter talks about how to set 
> up a tracking branch:
>
>
> https://wiki.duraspace.org/display/DSPACE/Development+with+Git#DevelopmentwithGit-Option2-%22cherry-pick%22changesfrommastertoreleasebranch
>
> That's how you get a branch from upstream repo into your local repo.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
> On Fri, Aug 10, 2018 at 1:56 PM Evgeni Dimitrov  > wrote:
>
>> Thank you helix84,
>>
>> When I did in the beginning
>>
>> >git remote add upstream git://github.com/DSpace/DSpace.git
>> >git fetch upstream
>> I got:
>>
>> remote: Counting objects: 287, done.
>> remote: Compressing objects: 100% (7/7), done.
>> Rremote: Total 287 (delta 113), reused 126 (delta 113), pack-reused 160
>> Receiving objects: 100% (287/287), 38.74 KiB | 0 bytes/s, done.
>> Resolving deltas: 100% (128/128), completed with 37 local objects.
>> From git://github.com/DSpace/DSpace
>>  * [new branch]  dspace-1_2_2-patches -> upstream/dspace-1_2_2-patches
>>  * [new branch]  dspace-1_2_2-update -> upstream/dspace-1_2_2-update
>>  * [new branch]  dspace-1_4_x -> upstream/dspace-1_4_x
>>  * [new branch]  dspace-1_5_x -> upstream/dspace-1_5_x
>>  * [new branch]  dspace-1_6_x -> upstream/dspace-1_6_x
>>  * [new branch]  dspace-1_7_x -> upstream/dspace-1_7_x
>>  * [new branch]  dspace-1_8_x -> upstream/dspace-1_8_x
>>  * [new branch]  dspace-3_x -> upstream/dspace-3_x
>>  * [new branch]  dspace-4_x -> upstream/dspace-4_x
>>  * [new branch]  dspace-5_x -> upstream/dspace-5_x
>>  * [new branch]  dspace-6_x -> upstream/dspace-6_x
>>  * [new branch]  master -> upstream/master
>>  * [new branch]  rest-tutorial -> upstream/rest-tutorial
>>
>> But now I get:
>>
>> D:\ADISK5\dspace-src>git checkout dspace-6_x
>> error: pathspec 'dspace-6_x' did not match any file(s) known to git.
>>
>>
>>
>> On Friday, August 10, 2018 at 1:33:14 PM UTC+3, helix84 wrote:
>>>
>>> # first switch to the dspace 6 branch:
>>> git checkout dspace-6_x
>>> # then create a new identical branch as the current one and name it 
>>> DS-3974
>>> git checkout -b DS-3974
>>>
>>>
>>> git remote add upstream git://github.com/DSpace/DSpace.git
>>> # this was a one-time operation which allows you to pull latest changes 
>>> from the official DSpace repo to your local repo:
>>> git pull upstream
>>> # which is identical to
>>> git fetch upstream
>>> git merge upstream
>>>
>>>
>>> Regards,
>>> ~~helix84
>>>
>>> Compulsory reading: DSpace Mailing List Etiquette
>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>
>>> On Fri, Aug 10, 2018 at 10:17 AM Evgeni Dimitrov  
>>> wrote:
>>>
>>>> I want to propose a fix to an issue.
>>>>
>>>> What I did:
>>>>
>>>> 1. I did Fork in https://github.com/DSpace/DSpace
>>>>
>>>> 2. I did clone to my machine:
>>>> git clone git://github.com/xx/DSpace.git dspace-src
>>>>
>>>> 3. I did (don't know why):
>>>> git remote add upstream git://github.com/DSpace/DSpace.git
>>>> git fetch upstream
>>>>
>>>> What I am trying now is to create a branch for the issue. The issue is 
>>>> in DSpace 6.3 and I suppose my branch should be a subbranch of dspace-6_x:
>>>>
>>>> D:\ADISK5\dspace-src>git checkout -b DS-3974 dspace-6_x
>>>> fatal: Cannot update paths and switch to branch 'DS-3974' at the same 
>>>> time.
>>>> Did you intend to checkout 'dspace-6_x' which can not be resolved as 
>>>> commit?
>>>>
>>>> D:\ADISK5\dspace-src>git branch DS-3974 dspace-6_x
>>>> fatal: Not a valid object name: 'dspace-6_x'.
>>>>
>>>> What branch should I create and how?
>>>>
>>>> -- 
>>>> 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 bec

[dspace-tech] How to branch in GitHub?

[Evgeni Dimitrov]

I want to propose a fix to an issue.

What I did:

1. I did Fork in https://github.com/DSpace/DSpace

2. I did clone to my machine:
git clone git://github.com/xx/DSpace.git dspace-src

3. I did (don't know why):
git remote add upstream git://github.com/DSpace/DSpace.git
git fetch upstream

What I am trying now is to create a branch for the issue. The issue is in
DSpace 6.3 and I suppose my branch should be a subbranch of dspace-6_x:

D:\ADISK5\dspace-src>git checkout -b DS-3974 dspace-6_x
fatal: Cannot update paths and switch to branch 'DS-3974' at the same time.
Did you intend to checkout 'dspace-6_x' which can not be resolved as commit?

D:\ADISK5\dspace-src>git branch DS-3974 dspace-6_x
fatal: Not a valid object name: 'dspace-6_x'.

What branch should I create and how?

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] About DS-3729 - can a bitstream belong to several bundles in DSpace 6.x?

[Evgeni Dimitrov]

Thank you Tim,

I believe that the fix to DS-3729 works fine if a bitstream belongs to 1, 3 
or more bundles and the fix fails if a bitstream belongs to 2 bundles.

But if this is practically impossible in DSpace, we need not worry about it.

Best regards
Evgeni


On Friday, August 3, 2018 at 6:59:39 PM UTC+3, Tim Donohue wrote:
>
> Hi Evgeni,
>
> While the DSpace data model technically supports the concept of having a 
> bitstream belong to more than one bundle, there's no way to achieve that 
> through the DSpace code itself (at least none that I'm aware of).  So, I 
> believe the only way to achieve this is by manually creating a new entry in 
> the bundle2bitstream table to link a specific bitstream into another bundle.
>
> - Tim
>
> On Thu, Aug 2, 2018 at 2:55 AM Evgeni Dimitrov  > wrote:
>
>> I retrofitted the fix to DS-3729 into my DSpace 6.2 installation.
>>
>> The fix is about how to check - does certain bitstream belong to one 
>> bundle only or to other bundles as well.
>>
>> The fix looks strange to me. I want to test how it works
>> - when a bitstream belongs to one bundle
>> - when a bitstream belongs to two bundles
>>
>> However I can not figure out how to construct a test case where a 
>> bitstream belongs to two bundles. Can somebody give an idea?
>>
>> -- 
>> 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 the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] About DS-3729 - can a bitstream belong to several bundles in DSpace 6.x?

[Evgeni Dimitrov]

I retrofitted the fix to DS-3729 into my DSpace 6.2 installation.

The fix is about how to check - does certain bitstream belong to one bundle
only or to other bundles as well.

The fix looks strange to me. I want to test how it works
- when a bitstream belongs to one bundle
- when a bitstream belongs to two bundles

However I can not figure out how to construct a test case where a bitstream
belongs to two bundles. Can somebody give an idea?

-- 
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 the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Bitstreams mimetype

[Evgeni Dimitrov]

Thank you Claudia,

It works now.

Best regards
Evgeni

On Monday, March 26, 2018 at 6:14:03 PM UTC+3, Claudia Jürgen wrote:
>
> Hello Evgeni, 
>
> that is correct because the format is not in the bitstream format 
> registry thus  becomes Unknown application/octet-stream. 
> Add the format to your registry and the bitstream format will be set 
> correctly. 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
> Am 26.03.2018 um 17:04 schrieb Evgeni Dimitrov: 
> > In DSpace 6.2 
> > I am ingesting separately two items each one with its own mets.xml. 
> > 
> > in the first mets.xml 
> >   
> > MIMETYPE="video/quicktime" 
> > SEQ="20001"> 
> >   
> > 
> >   
> > 
> > in the second mets.xml 
> >   
> > > SEQ="20001"> 
> >   
> > 
> >   
> > 
> > Later in an application I want to get the mimetype of the bitstream: 
> > 
> >  Bitstream bitstream = bitstreamService.find(context, bitstreamID); 
> >  String mimeType = bitstreamService.getFormat(context, 
> > bitstream).getMIMEType(); 
> > 
> > For the first I get "video/quicktime". 
> > For the second I get "application/octet-stream". 
> > 
> > Should it be this way? 
> > 
>
> -- 
> Claudia Juergen 
> Eldorado 
>
> Technische Universität Dortmund 
> Universitätsbibliothek 
> Vogelpothsweg 76 
> 44227 Dortmund 
>
> Tel.: +49 231-755 40 43 
> Fax: +49 231-755 40 32 
> claudia...@tu-dortmund.de  
> www.ub.tu-dortmund.de 
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank. 
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines 
> solchen Schriftstücks per Telefax erfolgen. 
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Bitstreams mimetype

[Evgeni Dimitrov]

In DSpace 6.2
I am ingesting separately two items each one with its own mets.xml.

in the first mets.xml

  

  


in the second mets.xml

  

  


Later in an application I want to get the mimetype of the bitstream:

Bitstream bitstream = bitstreamService.find(context, bitstreamID);
String mimeType = bitstreamService.getFormat(context,
bitstream).getMIMEType();

For the first I get "video/quicktime".
For the second I get "application/octet-stream".

Should it be this way?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Strange behaviour of OAI in 6.2

[Evgeni Dimitrov]

Or may be this has something to do with another part of ColComFilter.java 
which produces SolrQuery:

item.collections:(col_nls_87 OR col_nls_25523 OR com_nls_22332)

May be they should be separated as

item.collections:(col_nls_87 OR col_nls_25523) and 
item.communities:(com_nls_22332)

or should be combined in one query like

item.collections:(col_nls_87 OR col_nls_25523) OR 
item.communities:(com_nls_22332)

???


On Thursday, March 15, 2018 at 11:21:07 PM UTC+2, Evgeni Dimitrov wrote:
>
> May be it works the same in older versions too. I have not checked.
> I want to exclude from OAI the items under two collections and one 
> community.
>
> I have in xoai.xml filter and condition:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> org.dspace.xoai.filter.ColComFilter
> 
> 
> col_nls_87
> col_nls_25523
> com_nls_22332
> 
> 
> 
>
> 
>
> and the main part of ColComFilter.java is:
>
> public boolean isShown(DSpaceItem item) {
> if (collectionSpecs == null) {
> getCollectionSpecs();
> }
> 
> for (ReferenceSet rs : item.getSets()) {
> if (collectionSpecs.contains(rs.getSetSpec())) {
> return true;
> }
> }
> return false;
> }
>
> 
>
> This works fine for the two collections:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_87
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_25523
>
> return 
>
> But it works differently for the community:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=com_nls_22332
>
> returns a lot of identifiers:
>
> completeListSize="3731"  (which is the size of the community)
>
> and many entries like:
> 
> oai:dspace6:nls/27837
> 2017-12-14T09:52:31Z
> com_nls_22332
> com_nls_94
> col_nls_26938
> 
>
> But for everyone of the identifiers in the list (I tried 20) the request
>
>
> http://dspace6:8080/oai/request?verb=GetRecord=oai_dc=oai:dspace6:nls/27837
>
> returns 
> So that first OAI returns the ID in the list and second it says "the ID 
> does not exist". The second part I expected because I want to exclude all 
> items under this community. But the first part - the non empty list of IDs 
> was unexpected.
>
> Is there an explanation of this or is this a defect in OAI?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Strange behaviour of OAI in 6.2

[Evgeni Dimitrov]

Or may be this has something to do with another part of ColComFilter.java 
which produces SolrQuery:

item.collections:(col_nls_87 OR col_nls_25523 OR com_nls_22332)

May be they should be separated as

item.collections:(col_nls_87 OR col_nls_25523) and 
item.communities:(com_nls_22332)

or combined in one query like

item.collections:(col_nls_87 OR col_nls_25523) OR 
item.communities:(com_nls_22332)

???


On Thursday, March 15, 2018 at 11:21:07 PM UTC+2, Evgeni Dimitrov wrote:
>
> May be it works the same in older versions too. I have not checked.
> I want to exclude from OAI the items under two collections and one 
> community.
>
> I have in xoai.xml filter and condition:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> org.dspace.xoai.filter.ColComFilter
> 
> 
> col_nls_87
> col_nls_25523
> com_nls_22332
> 
> 
> 
>
> 
>
> and the main part of ColComFilter.java is:
>
> public boolean isShown(DSpaceItem item) {
> if (collectionSpecs == null) {
> getCollectionSpecs();
> }
> 
> for (ReferenceSet rs : item.getSets()) {
> if (collectionSpecs.contains(rs.getSetSpec())) {
> return true;
> }
> }
> return false;
> }
>
> 
>
> This works fine for the two collections:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_87
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_25523
>
> return 
>
> But it works differently for the community:
>
>
> http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=com_nls_22332
>
> returns a lot of identifiers:
>
> completeListSize="3731"  (which is the size of the community)
>
> and many entries like:
> 
> oai:dspace6:nls/27837
> 2017-12-14T09:52:31Z
> com_nls_22332
> com_nls_94
> col_nls_26938
> 
>
> But for everyone of the identifiers in the list (I tried 20) the request
>
>
> http://dspace6:8080/oai/request?verb=GetRecord=oai_dc=oai:dspace6:nls/27837
>
> returns 
> So that first OAI returns the ID in the list and second it says "the ID 
> does not exist". The second part I expected because I want to exclude all 
> items under this community. But the first part - the non empty list of IDs 
> was unexpected.
>
> Is there an explanation of this or is this a defect in OAI?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Strange behaviour of OAI in 6.2

[Evgeni Dimitrov]

May be it works the same in older versions too. I have not checked.
I want to exclude from OAI the items under two collections and one
community.

I have in xoai.xml filter and condition:




























org.dspace.xoai.filter.ColComFilter


col_nls_87
col_nls_25523
com_nls_22332





and the main part of ColComFilter.java is:

public boolean isShown(DSpaceItem item) {
if (collectionSpecs == null) {
getCollectionSpecs();
}

for (ReferenceSet rs : item.getSets()) {
if (collectionSpecs.contains(rs.getSetSpec())) {
return true;
}
}
return false;
}


This works fine for the two collections:

http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_87

http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=col_nls_25523

return http://dspace6:8080/oai/request?verb=ListIdentifiers=oai_dc=com_nls_22332

returns a lot of identifiers:

completeListSize="3731"  (which is the size of the community)

and many entries like:

oai:dspace6:nls/27837
2017-12-14T09:52:31Z
com_nls_22332
com_nls_94
col_nls_26938


But for everyone of the identifiers in the list (I tried 20) the request

http://dspace6:8080/oai/request?verb=GetRecord=oai_dc=oai:dspace6:nls/27837

returns https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Updating 5.6 to 6.2 - two questions

[Evgeni Dimitrov]

Yes, I repeated everything from the beginning and all worked fine.

Best regards
Evgeni

On Tuesday, February 6, 2018 at 11:59:17 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> Yes, that section of the documentation is actually asking you to run the 
> v5.6 "update-sequences.sql" against your 5.6-compatible database before 
> upgrading it. It's not required, but sometimes if your database sequences 
> get out of "sync", then the database upgrade could fail.
>
> Obviously, as the database changes in new releases, sometimes the 
> "update-sequences.sql" script needs to also change.  So, the issue here 
> seems to be that you ran the v6.2 "update-sequences.sql" against a 5.6 
> compatible database, and there are changes in the v6.2 
> "update-sequences.sql" that are not compatible with 5.6.
>
> Hopefully that makes more sense,
>
> Tim
>
>
> On Tue, Feb 6, 2018 at 2:46 PM Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> Thank you Tim,
>>
>> I followed the "Upgrade steps":
>> "In some scenarios, if your database's "sequences" are outdated, 
>> inconsistent or incorrect, a
>> database migration error may occur (in your DSpace logs). In order to 
>> AVOID this scenario, you
>> may wish to manually run the "update-sequences.sql" script PRIOR to 
>> upgrade."
>>
>> So, I did run "update-sequences.sql" AFTER setting 6.2 in [dspace-source] 
>> and running mvn and ant, but BEFORE the DB migration...
>>
>> Or may be this "PRIOR to upgrade" means to run the "update-sequences.sql" 
>> script of the 5.6 version before even starting the upgrade to 6.2?
>>
>> Best regards
>> Evgeni
>>
>>
>> On Tuesday, February 6, 2018 at 7:13:39 PM UTC+2, Tim Donohue wrote:
>>
>>> Hi Evgeni,
>>>
>>> It sounds to me like your DSpace 6.2 upgrade didn't fully succeed *OR* 
>>> you haven't yet run all the database migrations.  You might want to check 
>>> your DSpace logs (dspace.log) and/or the output of "[dspace]/bin/dspace 
>>> database status".  If migrations are listed as PENDING, that means they 
>>> haven't yet been run, and your database is not fully upgraded yet.  You can 
>>> manually run "./dspace database migrate" to run all Pending migrations (and 
>>> you should then watch the dspace.log file to see that they successfully are 
>>> applied). 
>>>
>>> 1) The "handle_id_seq" is created in one of the migrations that upgrade 
>>> your database to 6.x.  Specifically, this migration: 
>>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2016.07.26__DS-3277_fix_handle_assignment.sql#L15
>>>   
>>>  So, it sounds to me like this migration did not run yet, or failed in some 
>>> way.  Once this migration runs, the "update-sequences.sql" should work 
>>> again.
>>>
>>> 2) The registry updates should be triggered automatically (and you 
>>> should find them noted in your dspace.log file, if they were executed).  
>>> The database migrations and registry updates both should appear in your 
>>> dspace.log file.  If you have concerns though, you *can* manually run those 
>>> registry updates. Manually running them won't hurt anything, as it simply 
>>> checks if all the registry entries already exist...if they already do exist 
>>> in your database, then no changes will be made.
>>>
>>> In general, during a DSpace upgrade, you should keep a close eye on the 
>>> DSpace log files. That's where you'll see more information on whether a 
>>> migration failed, which migrations succeeded, and whether or not your 
>>> registry updates automatically.
>>>
>>> Good luck,
>>>
>>> Tim
>>>
>>> On Tue, Feb 6, 2018 at 9:12 AM Evgeni Dimitrov <dimitr...@gmail.com> 
>>> wrote:
>>>
>> I updated a small test repository from 5.6 to 6.2. Quite smoothly and all 
>>>> works in the end, but two questions appeared:
>>>>
>>>> 1. Running update-sequences.sql there was an error message:
>>>>
>>>> psql -U dspace -f 
>>>> D:\DSPACE.5.6.n\DSPACE\etc\postgres\update-sequences.sql dspace56n
>>>>
>>>> ...
>>>>
>>>>  setval
>>>> 
>>>> (1 row)
>>>>
>>>> psql:D:/DSPACE.5.6.n/DSPACE/etc/postgres/updat

Re: [dspace-tech] Updating 5.6 to 6.2 - two questions

[Evgeni Dimitrov]

Thank you Tim,

I followed the "Upgrade steps":
"In some scenarios, if your database's "sequences" are outdated, 
inconsistent or incorrect, a
database migration error may occur (in your DSpace logs). In order to AVOID 
this scenario, you
may wish to manually run the "update-sequences.sql" script PRIOR to 
upgrade."

So, I did run "update-sequences.sql" AFTER setting 6.2 in [dspace-source] 
and running mvn and ant, but BEFORE the DB migration...

Or may be this "PRIOR to upgrade" means to run the "update-sequences.sql" 
script of the 5.6 version before even starting the upgrade to 6.2?

Best regards
Evgeni

On Tuesday, February 6, 2018 at 7:13:39 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> It sounds to me like your DSpace 6.2 upgrade didn't fully succeed *OR* you 
> haven't yet run all the database migrations.  You might want to check your 
> DSpace logs (dspace.log) and/or the output of "[dspace]/bin/dspace database 
> status".  If migrations are listed as PENDING, that means they haven't yet 
> been run, and your database is not fully upgraded yet.  You can manually 
> run "./dspace database migrate" to run all Pending migrations (and you 
> should then watch the dspace.log file to see that they successfully are 
> applied). 
>
> 1) The "handle_id_seq" is created in one of the migrations that upgrade 
> your database to 6.x.  Specifically, this migration: 
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2016.07.26__DS-3277_fix_handle_assignment.sql#L15
>   
>  So, it sounds to me like this migration did not run yet, or failed in some 
> way.  Once this migration runs, the "update-sequences.sql" should work 
> again.
>
> 2) The registry updates should be triggered automatically (and you should 
> find them noted in your dspace.log file, if they were executed).  The 
> database migrations and registry updates both should appear in your 
> dspace.log file.  If you have concerns though, you *can* manually run those 
> registry updates. Manually running them won't hurt anything, as it simply 
> checks if all the registry entries already exist...if they already do exist 
> in your database, then no changes will be made.
>
> In general, during a DSpace upgrade, you should keep a close eye on the 
> DSpace log files. That's where you'll see more information on whether a 
> migration failed, which migrations succeeded, and whether or not your 
> registry updates automatically.
>
> Good luck,
>
> Tim
>
> On Tue, Feb 6, 2018 at 9:12 AM Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> I updated a small test repository from 5.6 to 6.2. Quite smoothly and all 
>> works in the end, but two questions appeared:
>>
>> 1. Running update-sequences.sql there was an error message:
>>
>> psql -U dspace -f 
>> D:\DSPACE.5.6.n\DSPACE\etc\postgres\update-sequences.sql dspace56n
>>
>> ...
>>
>>  setval
>> 
>> (1 row)
>>
>> psql:D:/DSPACE.5.6.n/DSPACE/etc/postgres/update-sequences.sql:63: ERROR:  
>> relation "handle_id_seq" does not exist
>> LINE 1: SELECT setval('handle_id_seq', max(handle_id)) FROM handle;
>>   ^
>>  setval
>> 
>>  42
>> (1 row)
>>
>> Is this an error in the script or an error in the database? Is not 
>> update-sequences.sql supposed to fix errors, not to report errors?
>>
>> 2. In the "Upgrade Steps" there is "The database migration should also 
>> trigger your metadata/file registries to be automatically updated (based on 
>> the config files in [dspace]/config/registries/). However, if this update 
>> was NOT triggered, you can also manually run these registry updates (they 
>> will not harm existing registry contents)."
>>
>> How can I know was the update of "metadata/file registries" triggered or 
>> not? What does registry-loader do? What if I run
>>
>> [dspace]/bin/dspace registry-loader -metadata 
>> [dspace]/config/registries/dcterms-types.xml
>>
>> without knowing was the update already triggered or not?
>>
>> Best regards
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/d

[dspace-tech] Updating 5.6 to 6.2 - two questions

[Evgeni Dimitrov]

I updated a small test repository from 5.6 to 6.2. Quite smoothly and all
works in the end, but two questions appeared:

1. Running update-sequences.sql there was an error message:

psql -U dspace -f D:\DSPACE.5.6.n\DSPACE\etc\postgres\update-sequences.sql
dspace56n

...

 setval

(1 row)

psql:D:/DSPACE.5.6.n/DSPACE/etc/postgres/update-sequences.sql:63: ERROR:
relation "handle_id_seq" does not exist
LINE 1: SELECT setval('handle_id_seq', max(handle_id)) FROM handle;
  ^
 setval

 42
(1 row)

Is this an error in the script or an error in the database? Is not
update-sequences.sql supposed to fix errors, not to report errors?

2. In the "Upgrade Steps" there is "The database migration should also
trigger your metadata/file registries to be automatically updated (based on
the config files in [dspace]/config/registries/). However, if this update
was NOT triggered, you can also manually run these registry updates (they
will not harm existing registry contents)."

How can I know was the update of "metadata/file registries" triggered or
not? What does registry-loader do? What if I run

[dspace]/bin/dspace registry-loader -metadata
[dspace]/config/registries/dcterms-types.xml

without knowing was the update already triggered or not?

Best regards

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] In 6.2 in REST dc.description.provenance is missing

[Evgeni Dimitrov]

Thank you Tim,

In the real program I am logging in as admin. But I wanted to check quickly 
in the browser what will I get in the program and here 
"dc.description.provenance" was missing. Now I know why :)

Thank you again
Evgeni

On Monday, January 22, 2018 at 5:12:54 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> I'm pretty sure the REST API hides any fields that are in the 
> "metadata.hide. " settings in your dspace.cfg (or local.cfg) file.  By 
> default, "dc.description.provenance" is hidden to anonymous users (in all 
> interfaces), as it may contain sensitive or private information (email 
> addresses, etc). It is available however from a UI if you are logged in as 
> an Administrator or someone with edit metadata rights (as you noted)
>
> It should also be available/visible if you authenticate to the REST API 
> first, and then look at the Item metadata while authenticated.
>
> Alternatively, if you want this field to be available in all interfaces, 
> you can un-hide it (in all interfaces) by commenting out this line of the 
> dspace.cfg:
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L798
>
> - Tim
>
> On Mon, Jan 22, 2018 at 9:01 AM Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> When I do in xmlui Item Edit/Metadata, then I see 
>> dc.description.provenance with a meaningful value.
>>
>> When I enter in the browser 
>> .../rest/items/{item UUID}/metadata
>>
>> then there is no dc.description.provenance
>>
>> Is there some easy patch that I could apply to 6.2?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Assign Role-Based Groups based on values from multiple Shib attributes

[Evgeni Dimitrov]

I have another system, which can authenticate some of the users.

I coded a standalone application, which gets userId/password and asks that 
system to authenticate. Then it calls DSpace and adds in the URL something 
about belonging to some group.

On the DSpace side I have something like the IPAuthentication.

On Friday, January 12, 2018 at 4:24:44 PM UTC+2, Jakub Řihák wrote:
>
> Dear all,
>
> we would like to assing users to DSpace Role-Based groups authenticated 
> with ShibAuthentication plugin using values from multiple Shibboleth 
> headers, for example:
>
> - assign users with value of Affiliation attribute = 'student' and value 
> of DisabledCategory attribute = 'A1' to predefined DSpace group 
> 'DisableStudent' to provide access to digitized materials that can only be 
> available for 'disabled students'
>
> - assign users with value of 'Affiliation attribute = 'member-1lf' and 
> value of 'AffiliationRole' = studentCorrdinator to predefined DSpace group 
> 'FacultyCoordinator1LF" to provide admin rights for DSpace collections to 
> users based on their affiliation within the university and their role 
> stored in our IdP
>
> etc.
>
> As far as I know, there is no way with current implementation of 
> ShibbolethAuthentication plugin  to take into account multiple Shibboleth 
> headers and their values when assigning user to a Group after he's 
> authenticated, am I right? ShibbolethAuthentication plugin seems to take 
> into account only values from one Shibboleth Header defined in 
> ShibAuthentication.cfg file. 
>
> Could you perhaps tell me, if anyone tried to achieve something similar?
>
> As it is (hopefully) apparent from examples, we need far greater 
> granularity when assigning authenticated users to DSpace groups. Right know 
> we are discussing our possibilities: 
>
> I think we have three possibilities:
> - 'calculate' correct user role based on multiple user attributes on the 
> side of IdP and send send 'calculated dspace group' as a value of some 
> Shibboleth Header the is defined in ShibAuthentication plugin (requires 
> programming)
>
> - use a standalone program to fetch user attributes from IdP and 
> preprocess them for DSpace ShibAuthentication plugin (requires programming)
>
> - modify ShibbolethAuthentication plugin in our DSpace instalation to look 
> for values from multiple ShibHeaders and assign users to groups based on 
> some newly programmed logic (requires programming as well)
>
> It would be very helpful to know, if there were some attempts to do this 
> on the 'DSpace side'  and/or if this would be a viable way how to improve 
> DSpace Authentication Plugin.
>
> We are using DSpace 5.6, so it might be better to just wait for newer 
> version of DSpace where this might be solved?  
>
> Thank you for any answer or suggestion,
> with best regards,
>
> Jakub Řihák
> Charles University
> Prague, Czech Republic
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Bitstream IDs when migrating 5.6 to 6.2

[Evgeni Dimitrov]

Thank you Tim,

This is really helpful.

Best regards
Evgeni

On Wednesday, November 22, 2017 at 6:22:30 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> The old and new IDs can be found in the "bitstream" table in the database 
> (see the "bitstream_id" and "uuid" columns for the old and new IDs 
> respectively).  New bitstreams will *not* receive an old ID however, which 
> is why the URLs now only utilize the new UUIDs.
>
> Handles are preserved through the entire migration, as Handles are 
> external, persistent identifiers.  The old Bitstream IDs were internal 
> identifier only, and have been replaced by UUIDs going forward (as UUIDs 
> are universally unique, while the old ID format was simply an incremental 
> internal counter in the database).
>
> - Tim
>
> On Fri, Nov 3, 2017 at 1:18 PM Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> I have DSpace 5.6 in production and I am going to migrate to 6.2.
>> I have some other software, which relies on links to bitstreams in 5.6 
>> like:
>>
>> http://xx.xx.xx/rest/bitstreams/256503/retrieve
>>
>> In 6.2 the bitstream IDs are different and a link looks like
>>
>>
>> http://xx.xx.xx/rest/bitstreams/ef9c9063-92e9-460e-9adc-c35a3921b741/retrieve
>>
>> Is there a way during the migration to get the mapping (old ID) -> (new 
>> ID)?
>>
>> Otherwise I should find the new IDs from their role in the item 
>> (thumbnail etc.).
>> I believe that the handles of the items are preserved during the 
>> migration?
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  Virus-free. 
>> www.avg.com 
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  
>> <#CACKSJ9N96f5E0J5oejZKYg4tpbpqtmp1R5W7RfajKaHU_GmKLA@mail.gmail.com_m_4098215834393260377_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Bitstream IDs when migrating 5.6 to 6.2

[Evgeni Dimitrov]

I have DSpace 5.6 in production and I am going to migrate to 6.2.
I have some other software, which relies on links to bitstreams in 5.6 like:

http://xx.xx.xx/rest/bitstreams/256503/retrieve

In 6.2 the bitstream IDs are different and a link looks like

http://xx.xx.xx/rest/bitstreams/ef9c9063-92e9-460e-9adc-c35a3921b741/retrieve

Is there a way during the migration to get the mapping (old ID) -> (new ID)?

Otherwise I should find the new IDs from their role in the item (thumbnail
etc.).
I believe that the handles of the items are preserved during the migration?



Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: NullPointerException when creating a root community

[Evgeni Dimitrov]

May be something with the migration of the database. I have freshly 
installed DSpace 6.2 and I had no problems creating communities and 
collections.

On Tuesday, October 31, 2017 at 1:47:53 PM UTC+2, karma.some...@gmail.com 
wrote:
>
> Hi,
>
> We're running DSpace 6.2 and we're having an issue creating root 
> communities (on the top of the hierarchy). Immediately after hitting the 
> "Create" button, a NullPointerException is shown. The strange thing is that 
> there are no logs anywhere in the 'logs' directory nor in the tomcat logs 
> when the exception pops-up. I could get Cocoon and Java logs though from 
> the web browser, which I'm attaching.
>
> We can just reproduce it when it comes to create a root community, no 
> issues when creating subcommunities nor collections.
>
> Could someone give some pointers on why is this happening and possibly how 
> to solve it?
>
> Thanks in advance
>
> James
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Replacing a bitstream in DSpace 6.2 using REST

[Evgeni Dimitrov]

Looks like this is a known bug:

https://jira.duraspace.org/browse/DS-3511 
<https://www.google.com/url?q=https%3A%2F%2Fjira.duraspace.org%2Fbrowse%2FDS-3511=D=1=AFQjCNFFNPEbNp19sxSXTRo3ki3B4cwTyQ>

and has been fixed on 19.09.2017 - after the release of 6.2 . . .


On Tuesday, October 31, 2017 at 10:32:10 PM UTC+2, Evgeni Dimitrov wrote:
>
> I may be wrong, but I expected to replace a bitstream with this line:
>
> curl -v --cookie "JSESSIONID=9EB449E3FCC173204AB14AD189911324" -T mets.xml 
> http://localhost:8080/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data
>
> It did not happen and I got in different places the following messages:
>
> -
> HTTP Status 500 - Internal Server Error
>
> -
> 127.0.0.1 - - [31/Oct/2017:22:14:38 +0200] "PUT 
> /rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data HTTP/1.1" 500 
> 1082
>
> -
> 2017-10-31 22:14:38,463 INFO  org.dspace.rest.BitstreamResource @ Updating 
> bitstream(id=5a286ddc-f138-43ac-afca-3d0a761f5149) data.
> 2017-10-31 22:14:38,712 INFO  org.dspace.content.BitstreamServiceImpl @ 
> e...@nomail.xx::update_bitstream:bitstream_id=5a286ddc-f138-43ac-afca-3d0a761f5149
> 2017-10-31 22:14:38,728 ERROR org.dspace.rest.Resource @ Something get 
> wrong. Aborting context in finally statement.
>
> Any advice is welcome.
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free. 
> www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  
> <#CAJc2bOzQr_sGE7k_So_qMGMM1wx8zR1dm+W2LKhgzHLYXLZagQ@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Replacing a bitstream in DSpace 6.2 using REST

[Evgeni Dimitrov]

I may be wrong, but I expected to replace a bitstream with this line:

curl -v --cookie "JSESSIONID=9EB449E3FCC173204AB14AD189911324" -T mets.xml
http://localhost:8080/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data

It did not happen and I got in different places the following messages:

-
HTTP Status 500 - Internal Server Error

-
127.0.0.1 - - [31/Oct/2017:22:14:38 +0200] "PUT
/rest/bitstreams/5a286ddc-f138-43ac-afca-3d0a761f5149/data HTTP/1.1" 500
1082

-
2017-10-31 22:14:38,463 INFO  org.dspace.rest.BitstreamResource @ Updating
bitstream(id=5a286ddc-f138-43ac-afca-3d0a761f5149) data.
2017-10-31 22:14:38,712 INFO  org.dspace.content.BitstreamServiceImpl @
e...@nomail.xx
::update_bitstream:bitstream_id=5a286ddc-f138-43ac-afca-3d0a761f5149
2017-10-31 22:14:38,728 ERROR org.dspace.rest.Resource @ Something get
wrong. Aborting context in finally statement.

Any advice is welcome.



Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: OAI questions

[Evgeni Dimitrov]

Hi,

One can do everything. And it is easy.

One can define new format - providing an xsl which transforms from xoai to 
the new format. If one needs more then one can call Java from the xsl.

One can define new filter based on existing conditions and if necessary one 
can code a new condition in Java.

On Tuesday, October 24, 2017 at 10:24:08 PM UTC+3, Keith Jones wrote:
>
>
> Hi,
>
> I'm trying to find information about how much customizing one can do with 
> OAI harvesting.
> Is it possible to define what level of data is returned when a Dspace 
> repository is accessed via OAI.
> Can you also set up different data returned based on 
> Community/Collection/Item levels?
>
> Thanks
> Keith
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Two OAI problems with DSpace 6.2

[Evgeni Dimitrov]

Thank you Christian,
You may be right. But in my case it goes wrong before it comes to XML.
I am logging the SolrDocument before sending to Solr:

SolrInputDocument(fields: [item.id=ecc9c18e-4e91-4e7a-8e61-eb88472f8f0a, 
item.public=true, item.handle=nls/3, item.lastmodified=2017-10-16 
23:18:01.117, item.submitter=e...@nomail.xx, item.deleted=false, 
item.collections=col_nls_2, item.communities=com_nls_1, 
metadata.dc.coverage.spatial=София, България, 
metadata.dc.creator=Карастоянов, Д., 

I am logging the SolrDocument after Solr returns it:

SolrDocument{item.id=ecc9c18e-4e91-4e7a-8e61-eb88472f8f0a, 
item.public=true, item.handle=nls/3, item.lastmodified=Mon Oct 16 23:18:01 
EEST 2017, item.submitter=e...@nomail.xx, item.deleted=false, 
item.collections=[col_nls_2], item.communities=[com_nls_1], 
metadata.dc.coverage.spatial=[?, ], 
metadata.dc.creator=[???, ?.],

I tried querying Solr from my own standalone application - same way as 
DSpace does - same version of the Solr client - the result is as above.

Finally I am querying Solr from the browser and I am getting a correct 
response:

София, 
БългарияКарастоянов, 
Д.

Which makes me think that there is a problem with the Solr client - either 
configuration missing or something wrong in this exactly version.


On Tuesday, October 24, 2017 at 8:58:19 AM UTC+3, Christian Scheible wrote:
>
> Hi together,
>
> we are currently investigating the same problem.
> It's because there are non valid XML 1.0 Characters in the metadata (like 
> surrogate pairs).
>
> This block explains it and shows a method how to get rid of them:
>
>
> http://blog.mark-mclaren.info/2007/02/invalid-xml-characters-when-valid-utf8_5873.html
>
> If I have time I am going to make a pull request for this issue.
>
> Hope this helps
> Christian
>
> Am 23.10.2017 um 22:20 schrieb Evgeni Dimitrov:
>
> The problem with
>
>
> http://localhost:8080/oai/request?verb=GetRecord=xoai=oai:localhost:nls/3
>
> not working is related to metadata with non-ASCII characters. The strange 
> thing is that the added log shows that DSpace gets with SolrServer.query() 
> the metadata with the non-ASCII characters distorted. But when Solr is 
> queried in the browser:
>
> http://localhost:8080/solr/oai/select?q=item.handle:nls/3
>
> then the non-ASCII characters are correct. I can not figure out why . . .
>
>
> On Thursday, October 19, 2017 at 9:04:39 PM UTC+3, Evgeni Dimitrov wrote: 
>>
>> I have a freshly installed DSpace 6.2 with 15 items in it.
>> I have not changed anything in the OAI configuration.
>> Two of the items have READ access for certain groups only. The rest are 
>> accessible to everybody.
>>
>> Problem 1.
>> When I run
>> dspace oai import -c
>>
>> I get in dspace.log two exceptions (I suppose for each of the restricted 
>> access items):
>>
>> 2017-10-19 17:55:22,650 WARN  org.dspace.xoai.util.ItemUtils @ 
>> Authorization denied for action READ on 
>> BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
>> org.dspace.authorize.AuthorizeException: Authorization denied for action 
>> READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
>>
>> The whole text of the exception is very long.
>>
>> Problem 2.
>> After that I am trying
>> http://localhost:8080/oai/request?verb=Identify
>> http://localhost:8080/oai/request?verb=ListSets
>> http://localhost:8080/oai/request?verb=ListMetadataFormats
>> http://localhost:8080/oai/request?verb=ListIdentifiers=xoai
>> and it all works.
>>
>> But for
>>
>> http://localhost:8080/oai/request?verb=GetRecord=oai:localhost:nls/3=xoai
>> (nls/3 is an item accessible to everybody)
>> I get in the browser
>>
>> java.io.IOException: 
>> com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying 
>> to output ''
>> 
>> org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113)
>>
>> The whole text of the exception is very long.
>>
>> My question is - am I missing something in the configuration or is this a 
>> known problem with DSpace 6.2?
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  Virus-free. 
>> www.avg.com 
>> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspace-tech...@go

[dspace-tech] Re: Two OAI problems with DSpace 6.2

[Evgeni Dimitrov]

The problem with

http://localhost:8080/oai/request?verb=GetRecord=xoai=oai:localhost:nls/3

not working is related to metadata with non-ASCII characters. The strange 
thing is that the added log shows that DSpace gets with SolrServer.query() 
the metadata with the non-ASCII characters distorted. But when Solr is 
queried in the browser:

http://localhost:8080/solr/oai/select?q=item.handle:nls/3

then the non-ASCII characters are correct. I can not figure out why . . .


On Thursday, October 19, 2017 at 9:04:39 PM UTC+3, Evgeni Dimitrov wrote:
>
> I have a freshly installed DSpace 6.2 with 15 items in it.
> I have not changed anything in the OAI configuration.
> Two of the items have READ access for certain groups only. The rest are 
> accessible to everybody.
>
> Problem 1.
> When I run
> dspace oai import -c
>
> I get in dspace.log two exceptions (I suppose for each of the restricted 
> access items):
>
> 2017-10-19 17:55:22,650 WARN  org.dspace.xoai.util.ItemUtils @ 
> Authorization denied for action READ on 
> BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
> org.dspace.authorize.AuthorizeException: Authorization denied for action 
> READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
>
> The whole text of the exception is very long.
>
> Problem 2.
> After that I am trying
> http://localhost:8080/oai/request?verb=Identify
> http://localhost:8080/oai/request?verb=ListSets
> http://localhost:8080/oai/request?verb=ListMetadataFormats
> http://localhost:8080/oai/request?verb=ListIdentifiers=xoai
> and it all works.
>
> But for
>
> http://localhost:8080/oai/request?verb=GetRecord=oai:localhost:nls/3=xoai
> (nls/3 is an item accessible to everybody)
> I get in the browser
>
> java.io.IOException: 
> com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying 
> to output ''
> 
> org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113)
>
> The whole text of the exception is very long.
>
> My question is - am I missing something in the configuration or is this a 
> known problem with DSpace 6.2?
>
>
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free. 
> www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  
> <#CAJc2bOxUdju=Fai5GKJ3-dgzeduhdrOkBUe-Hw7v=DPRxRj87w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Two OAI problems with DSpace 6.2

[Evgeni Dimitrov]

It turned out that Problem 1 is easy to fix - with one line added to 
XOAI.java

But this does not help for Problem 2 - which is that

http://localhost:8080/oai/request?verb=GetRecord=xoai=oai:localhost:nls/3

works fine for 10 items and does not work for 5 items . . .


On Thursday, October 19, 2017 at 9:04:39 PM UTC+3, Evgeni Dimitrov wrote:
>
> I have a freshly installed DSpace 6.2 with 15 items in it.
> I have not changed anything in the OAI configuration.
> Two of the items have READ access for certain groups only. The rest are 
> accessible to everybody.
>
> Problem 1.
> When I run
> dspace oai import -c
>
> I get in dspace.log two exceptions (I suppose for each of the restricted 
> access items):
>
> 2017-10-19 17:55:22,650 WARN  org.dspace.xoai.util.ItemUtils @ 
> Authorization denied for action READ on 
> BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
> org.dspace.authorize.AuthorizeException: Authorization denied for action 
> READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
>
> The whole text of the exception is very long.
>
> Problem 2.
> After that I am trying
> http://localhost:8080/oai/request?verb=Identify
> http://localhost:8080/oai/request?verb=ListSets
> http://localhost:8080/oai/request?verb=ListMetadataFormats
> http://localhost:8080/oai/request?verb=ListIdentifiers=xoai
> and it all works.
>
> But for
>
> http://localhost:8080/oai/request?verb=GetRecord=oai:localhost:nls/3=xoai
> (nls/3 is an item accessible to everybody)
> I get in the browser
>
> java.io.IOException: 
> com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying 
> to output ''
> 
> org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113)
>
> The whole text of the exception is very long.
>
> My question is - am I missing something in the configuration or is this a 
> known problem with DSpace 6.2?
>
>
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free. 
> www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  
> <#CAJc2bOxUdju=Fai5GKJ3-dgzeduhdrOkBUe-Hw7v=DPRxRj87w@mail.gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Two OAI problems with DSpace 6.2

[Evgeni Dimitrov]

I have a freshly installed DSpace 6.2 with 15 items in it.
I have not changed anything in the OAI configuration.
Two of the items have READ access for certain groups only. The rest are
accessible to everybody.

Problem 1.
When I run
dspace oai import -c

I get in dspace.log two exceptions (I suppose for each of the restricted
access items):

2017-10-19 17:55:22,650 WARN  org.dspace.xoai.util.ItemUtils @
Authorization denied for action READ on
BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null
org.dspace.authorize.AuthorizeException: Authorization denied for action
READ on BITSTREAM:3d21ebf7-ef3e-4d98-a265-c4a516b1740b by user null

The whole text of the exception is very long.

Problem 2.
After that I am trying
http://localhost:8080/oai/request?verb=Identify
http://localhost:8080/oai/request?verb=ListSets
http://localhost:8080/oai/request?verb=ListMetadataFormats
http://localhost:8080/oai/request?verb=ListIdentifiers=xoai
and it all works.

But for
http://localhost:8080/oai/request?verb=GetRecord=oai:localhost:nls/3=xoai
(nls/3 is an item accessible to everybody)
I get in the browser

java.io.IOException:
com.lyncode.xoai.dataprovider.exceptions.WritingXmlException: Error trying
to output ''

org.dspace.xoai.services.impl.cache.DSpaceXOAICacheService.store(DSpaceXOAICacheService.java:113)

The whole text of the exception is very long.

My question is - am I missing something in the configuration or is this a
known problem with DSpace 6.2?


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: What is in the assetstore?

[Evgeni Dimitrov]

Yes Stefanie,

I don't like this way, but the other option is to query the database. Which 
I don't like either.

So that I sent requests for all 24601 items and this took about 4 hours. 
The program was running on the server.

Best regards
Evgeni


On Monday, April 10, 2017 at 10:14:45 PM UTC+3, Stefanie Behnke wrote:
>
> Dear Evgeni,
>
> I have got a question to your text, what does "" in 
> rest/items//bitstreams?offset= stands for?
> The item id? Do you send this request for all your 24601 items?
>
> I am looking for a simple method how to get the number of bitstreams.
>
> Thanking you in advance
> Stefanie
>
> Am Montag, 10. April 2017 10:42:30 UTC+2 schrieb Evgeni Dimitrov:
>>
>> This is with DSpace 5.6.
>>
>> I had to provide for every top community
>> - number of items
>> - number of bitstreams
>>
>> I used REST - for items:
>>
>> rest/items?offset==parentCommunityList
>>
>> for bitstreams:
>>
>> rest/items//bitstreams?offset=
>>
>> The total for all top communities is
>> - items 24601
>> - bitstreams 335380
>>
>> Just to double-check I got the number of files in the assetstore
>>
>> find /assetstore -type f | wc -l
>>
>> It is 385867 - much bigger than the number of bitstreams - 50487 files 
>> more.
>> Are there in the assetstore other files apart of bitstreams or may be 
>> something in my counting is wrong?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] What is in the assetstore?

[Evgeni Dimitrov]

Thank you Emilio,

For every item, I ingest
- the content (the files appearing in the bundle ORIGINAL) 
- mets.xml (appearing in the METADATA bundle)
- a thumbnail (appearing in the THUMBNAIL bundle).
DSpace creates one more - license.txt (in the LICENSE bundle).

All these 3 additional bitstreams are listed in the result obtained with

rest/items//bitstreams?offset=

So that the 3 additional files in every item are counted in my total of 
bitstreams - 335380.
But there are 50487 more in the assetstore, which I can not explain.

Best regards
Evgeni

On Monday, April 10, 2017 at 11:49:45 AM UTC+3, Emilio Lorenzo wrote:
>
> Hi, Evgeni 
>
> yes, the assestore can contains more files you would not have thought 
> about, in fact anything belonging to ítems that it is not metadata 
>
> Thumbnails 
> full-text extraction 
> licenses (txt and creative commons) 
> etc... 
>
> regards 
> Emilio 
>
>
> > This is with DSpace 5.6. 
> > 
> > I had to provide for every top community 
> > - number of items 
> > - number of bitstreams 
> > 
> > I used REST - for items: 
> > 
> > rest/items?offset==parentCommunityList 
> > 
> > for bitstreams: 
> > 
> > rest/items//bitstreams?offset= 
> > 
> > The total for all top communities is 
> > - items 24601 
> > - bitstreams 335380 
> > 
> > Just to double-check I got the number of files in the assetstore 
> > 
> > find /assetstore -type f | wc -l 
> > 
> > It is 385867 - much bigger than the number of bitstreams - 50487 files 
> > more. 
> > Are there in the assetstore other files apart of bitstreams or may be 
> > something in my counting is wrong? 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "DSpace Technical Support" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to dspace-tech...@googlegroups.com . 
> > To post to this group, send email to dspac...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/dspace-tech. 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] What is in the assetstore?

[Evgeni Dimitrov]

This is with DSpace 5.6.

I had to provide for every top community
- number of items
- number of bitstreams

I used REST - for items:

rest/items?offset==parentCommunityList

for bitstreams:

rest/items//bitstreams?offset=

The total for all top communities is
- items 24601
- bitstreams 335380

Just to double-check I got the number of files in the assetstore

find /assetstore -type f | wc -l

It is 385867 - much bigger than the number of bitstreams - 50487 files more.
Are there in the assetstore other files apart of bitstreams or may be
something in my counting is wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Dissemination Crosswalk class for OAI

[Evgeni Dimitrov]

The idea behind SimpleDCDisseminationCrosswalk.java remains not clear, but 
there is workaround. One can use a crosswalk marcxml.xsl like this:

. . .
xmlns:marcxml="org.dspace.xoai.metadataFormats.MarcXML"
. . .




Everything necessary can be done in the Java method.


On Thursday, March 2, 2017 at 3:28:30 PM UTC+2, Evgeni Dimitrov wrote:
>
> I have in every ingested item a mets.xml file with descriptive metadata in 
> MARC.
> I am looking at SimpleDCDisseminationCrosswalk.java
> I can code something similar, which will extract the MARC xml from the 
> mets file.
>
> I can not figure out what to do after that - how to describe in xoai.xml 
> one context with this single marcxml format - which is produced by my 
> MarcXMLDisseminationCrosswalk.java
>
> Could you help?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Dissemination Crosswalk class for OAI

[Evgeni Dimitrov]

I have in every ingested item a mets.xml file with descriptive metadata in
MARC.
I am looking at SimpleDCDisseminationCrosswalk.java
I can code something similar, which will extract the MARC xml from the mets
file.

I can not figure out what to do after that - how to describe in xoai.xml
one context with this single marcxml format - which is produced by my
MarcXMLDisseminationCrosswalk.java

Could you help?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] The order of the Curation Tasks in DSpace 6.0

[Evgeni Dimitrov]

Thank you helix84,

Yes, it works this way.

Best regards
Evgeni

On Friday, February 24, 2017 at 5:49:42 PM UTC+2, helix84 wrote:
>
> I *think* it should work if you paste the whole block with your addition 
> into local.cfg. It should override what's in dspace.cfg. Please, try it and 
> let us know.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
> On Fri, Feb 24, 2017 at 4:47 PM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> in 5.6 I have in curate.cfg:
>>
>> ui.tasknames = \
>>  nalispoliciesa = Inherit Default Policies, \
>>  profileformats = Profile Bitstream Formats, \
>>  requiredmetadata = Check for Required Metadata, \
>>  checklinks = Check Links in Metadata
>>
>> in 6.0 there is in curate.cfg:
>>
>> curate.ui.tasknames = profileformats = Profile Bitstream Formats
>> curate.ui.tasknames = requiredmetadata = Check for Required Metadata
>> curate.ui.tasknames = checklinks = Check Links in Metadata
>>
>> I need to add
>>
>> curate.ui.tasknames = nalispoliciesa = Inherit Default Policies
>>
>> Perhaps, the "better" way is to add it not to curate.cfg, but to 
>> local.cfg? But I want this task to be the first in the list of Curation 
>> Tasks in the UI.
>>
>> Is this still possible?
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] The order of the Curation Tasks in DSpace 6.0

[Evgeni Dimitrov]

in 5.6 I have in curate.cfg:

ui.tasknames = \
 nalispoliciesa = Inherit Default Policies, \
 profileformats = Profile Bitstream Formats, \
 requiredmetadata = Check for Required Metadata, \
 checklinks = Check Links in Metadata

in 6.0 there is in curate.cfg:

curate.ui.tasknames = profileformats = Profile Bitstream Formats
curate.ui.tasknames = requiredmetadata = Check for Required Metadata
curate.ui.tasknames = checklinks = Check Links in Metadata

I need to add

curate.ui.tasknames = nalispoliciesa = Inherit Default Policies

Perhaps, the "better" way is to add it not to curate.cfg, but to local.cfg?
But I want this task to be the first in the list of Curation Tasks in the
UI.

Is this still possible?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] REST returns a bitstream as an attachment

[Evgeni Dimitrov]

This is about DSpace 5.6.
I noticed only now that when I request in the browser a bitstream -
something like

http://xxx.xxx.xxx/rest/bitstreams/n/retrieve

then the browser gets it with

Content-Disposition: "attachment; filename="img_01.jpg""

I remember there is something about JSPUI and XMLUI
webui.content_disposition_threshold
xmlui.content_disposition_threshold

but here it is about REST. Is there a way to tell rest to return the
bitstream inline?

Best regards
Evgeni

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] the elements of DIM

[Evgeni Dimitrov]

Thank you very much Claudia,

I am interested in the crosswalk, which happens when I ingest an object, 
described in a METS file (with some descriptive metadata in it).

>From what you are saying, I understand, that it is up to me to choose for 
my crosswalk:
- to map some metadata to dc.rights.holder or to dcterms.rightsHolder
- and in general
--- to map to qualified DC (dc.xxx.xxx) or
--- to map to DC terms (dcterms.xxx) or
--- to map to a mixture of both (however ugly it is)

Is this correct?
I think I saw in the Manuel that there is a "tendency" in the DSpace 
project to move from qualified DC to DC terms. Do you know anything about 
this?

Best regards
Evgeni


On Thursday, January 26, 2017 at 4:04:00 PM UTC+2, Claudia Jürgen wrote:
>
> Hello Evgeni, 
>
> the metadata listed in item edit and all metadata fields usable in an 
> DSpace instance are in the metadata registry. 
>
> On a fresh installation this is populated from: 
> https://github.com/DSpace/DSpace/tree/dspace-5.6/dspace/config/registries 
>
> You can view/add/change metadata fields or even new schemata as 
> administrator via 
> Administer -> General Settings -> Metadata Registry 
>
> The list of the default settings is quite stable, but there might be 
> changes, e.g. for the support of metadata for all objects new metadata 
> schemata were introduced like eperson. 
>
> As DSpace supports metadata for not only items but also other DSpace 
> objects like 
> communites, collections, eperson ... 
> There are some "special" metadata schemata like eperson which are not 
> used for item metadata. 
> The DIM (DSpace intermediate metada) is just a legacy interim format 
> exposing all the item's metadata for internal use in crosswalking. 
>
> In OAI the base for crosswalking is nowadays xoai not dim, if you are 
> working on a crosswalk there. 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
>
> Am 26.01.2017 um 14:47 schrieb Evgeni Dimitrov: 
> > Hi, this is about DSpace 5.6. 
> > When I edit an item and add new metadata, I can select the kind of 
> metadata 
> > in a list (see bellow). I would like to know - what are this elements - 
> are 
> > they all elements of DIM? In terms of crosswalk - can they all be on the 
> > left side or on the right side of the crosswalk? Is this list supposed 
> to 
> > be stable from one version of DSpace to the next one? 
> > 
> > Best regards 
> > Evgeni 
> > 
> > = 
> > dc.contributor.advisor, dc.contributor.author, dc.contributor.editor, 
> > dc.contributor.illustrator, dc.contributor.other, dc.contributor, 
> > dc.coverage.spatial, dc.coverage.temporal, dc.creator, 
> dc.date.accessioned, 
> > dc.date.available, dc.date.copyright, dc.date.created, dc.date.issued, 
> > dc.date.submitted, dc.date.updated, dc.date, dc.description.abstract, 
> > dc.description.provenance, dc.description.sponsorship, 
> > dc.description.statementofresponsibility, 
> dc.description.tableofcontents, 
> > dc.description.uri, dc.description.version, dc.description, 
> > dc.format.extent, dc.format.medium, dc.format.mimetype, dc.format, 
> > dc.identifier.citation, dc.identifier.govdoc, dc.identifier.isbn, 
> > dc.identifier.ismn, dc.identifier.issn, dc.identifier.other, 
> > dc.identifier.sici, dc.identifier.slug, dc.identifier.uri, 
> dc.identifier, 
> > dc.language.iso, dc.language.rfc3066, dc.language, dc.provenance, 
> > dc.publisher, dc.relation.haspart, dc.relation.hasversion, 
> > dc.relation.isbasedon, dc.relation.isformatof, dc.relation.ispartof, 
> > dc.relation.ispartofseries, dc.relation.isreferencedby, 
> > dc.relation.isreplacedby, dc.relation.isversionof, dc.relation.replaces, 
> > dc.relation.requires, dc.relation.uri, dc.relation, dc.rights.holder, 
> > dc.rights.license, dc.rights.uri, dc.rights, dc.source.uri, dc.source, 
> > dc.subject.classification, dc.subject.ddc, dc.subject.lcc, 
> dc.subject.lcsh, 
> > dc.subject.mesh, dc.subject.other, dc.subject, dc.title.alternative, 
> > dc.title, dc.type, dcterms.abstract, dcterms.accessRights, 
> > dcterms.accrualMethod, dcterms.accrualPeriodicity, 
> dcterms.accrualPolicy, 
> > dcterms.alternative, dcterms.audience, dcterms.available, 
> > dcterms.bibliographicCitation, dcterms.comformsTo, dcterms.conformsTo, 
> > dcterms.contributor, dcterms.coverage, dcterms.created, dcterms.creator, 
> > dcterms.date, dcterms.dateAccepted, dcterms.dateCopyrighted, 
> > dcterms.dateSubmitted, dcterms.description, dcterms.educationLevel, 
> > dcterms.extent, dcterms.format, dcterms.hasFormat, dcterms.hasPart, 
> > dcterms.hasVersion, dcterms.identifie

[dspace-tech] the elements of DIM

[Evgeni Dimitrov]

Hi, this is about DSpace 5.6.
When I edit an item and add new metadata, I can select the kind of metadata
in a list (see bellow). I would like to know - what are this elements - are
they all elements of DIM? In terms of crosswalk - can they all be on the
left side or on the right side of the crosswalk? Is this list supposed to
be stable from one version of DSpace to the next one?

Best regards
Evgeni

=
dc.contributor.advisor, dc.contributor.author, dc.contributor.editor,
dc.contributor.illustrator, dc.contributor.other, dc.contributor,
dc.coverage.spatial, dc.coverage.temporal, dc.creator, dc.date.accessioned,
dc.date.available, dc.date.copyright, dc.date.created, dc.date.issued,
dc.date.submitted, dc.date.updated, dc.date, dc.description.abstract,
dc.description.provenance, dc.description.sponsorship,
dc.description.statementofresponsibility, dc.description.tableofcontents,
dc.description.uri, dc.description.version, dc.description,
dc.format.extent, dc.format.medium, dc.format.mimetype, dc.format,
dc.identifier.citation, dc.identifier.govdoc, dc.identifier.isbn,
dc.identifier.ismn, dc.identifier.issn, dc.identifier.other,
dc.identifier.sici, dc.identifier.slug, dc.identifier.uri, dc.identifier,
dc.language.iso, dc.language.rfc3066, dc.language, dc.provenance,
dc.publisher, dc.relation.haspart, dc.relation.hasversion,
dc.relation.isbasedon, dc.relation.isformatof, dc.relation.ispartof,
dc.relation.ispartofseries, dc.relation.isreferencedby,
dc.relation.isreplacedby, dc.relation.isversionof, dc.relation.replaces,
dc.relation.requires, dc.relation.uri, dc.relation, dc.rights.holder,
dc.rights.license, dc.rights.uri, dc.rights, dc.source.uri, dc.source,
dc.subject.classification, dc.subject.ddc, dc.subject.lcc, dc.subject.lcsh,
dc.subject.mesh, dc.subject.other, dc.subject, dc.title.alternative,
dc.title, dc.type, dcterms.abstract, dcterms.accessRights,
dcterms.accrualMethod, dcterms.accrualPeriodicity, dcterms.accrualPolicy,
dcterms.alternative, dcterms.audience, dcterms.available,
dcterms.bibliographicCitation, dcterms.comformsTo, dcterms.conformsTo,
dcterms.contributor, dcterms.coverage, dcterms.created, dcterms.creator,
dcterms.date, dcterms.dateAccepted, dcterms.dateCopyrighted,
dcterms.dateSubmitted, dcterms.description, dcterms.educationLevel,
dcterms.extent, dcterms.format, dcterms.hasFormat, dcterms.hasPart,
dcterms.hasVersion, dcterms.identifier, dcterms.instructionalMethod,
dcterms.isFormatOf, dcterms.isPartOf, dcterms.isReferencedBy,
dcterms.isReplacedBy, dcterms.isRequiredBy, dcterms.issued,
dcterms.isVersionOf, dcterms.language, dcterms.license, dcterms.mediator,
dcterms.medium, dcterms.modified, dcterms.provenance, dcterms.publisher,
dcterms.references, dcterms.relation, dcterms.replaces, dcterms.requires,
dcterms.rights, dcterms.rightsHolder, dcterms.source, dcterms.spatial,
dcterms.subject, dcterms.tableOfContents, dcterms.temporal, dcterms.title,
dcterms.type, dcterms.valid, eperson.firstname, eperson.language,
eperson.lastname, eperson.phone
===

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Is this a possible kind of search?

[Evgeni Dimitrov]

Hi Terry,

Thank you for the information. I will see will it be possible to introduce 
a new kind of facet.
To have a bean of the new kind for the "relation" facet.
And to add some Java code to make a request to SOLR and get results. I have 
now some time to try.

Best regards
Evgeni

On Thursday, December 22, 2016 at 7:28:18 PM UTC+2, Terry Brady wrote:
>
> Evgeni,
>
> The default behavior of the facets and filters will not accomplish your 
> goal.
>
> There is a feature called a Hierarchical Sidebar Facet that might help.  I 
> have not used this feature, so I do not know if it will help with your 
> issue.
>
>
> https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-Hierarchical(taxonomiesbased)sidebarfacets
>
> I believe we attempted something like what you are trying to accomplish.  
> We settled for what we could achieve with the default facet options.
>
> In our repository, we have a community of MOOC courses.  It is faceted by 
> course name.  Each course lives in a separate collection.  (Since each 
> course it distinct, it made sense to place each one in its own collection.)
>
> https://repository.library.georgetown.edu/handle/10822/710899
>
> If you navigate to a collection, the collection content is faceted by week 
> of the course.
>
> https://repository.library.georgetown.edu/handle/10822/712963
>
> Unfortunately, if you follow the course facet, you do not see the week 
> facet because you are still at the community level.
>
>
> https://repository.library.georgetown.edu/handle/10822/710899/discover?filtertype=gu-course_relational_operator=equals=Genomic+Medicine+Gets+Personal-GeorgetownX-MEDX202-01
>
> Terry
>
> On Thu, Dec 22, 2016 at 1:47 AM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> Thank you Terry,
>>
>> I want a facet, a sidebar facet. But it is a "parameterized" facet.
>> It makes sense only together with a search filter "relation" 
>> (dc.relation.*).
>>
>> There is an item A with dc.identifier=123.
>> The end-user makes search and adds the filter "relation = 123".
>> Because the end-user wants all items with some relation to item A.
>>
>> Only in this context the facet makes sense and it may be produced by
>>
>> =relation.isbasedon:123
>> =relation.isformatof:123
>> =relation.isreferencedby:123
>>
>> The value of the search (123) is the parameter of the facet.
>>
>> I mean - we make search for all items with any kind of relation to item A 
>> (123). And we get a facet with the breakdown by the kind of relation to 
>> item A. The facet makes sense and is possible only in pair with the search 
>> filter "relation".
>>
>> Best regards
>> Evgeni
>>
>>
>> On Thursday, December 22, 2016 at 12:28:30 AM UTC+2, Terry Brady wrote:
>>>
>>> Are you attempting to create a query or to create a facet?
>>>
>>> If you are building a query, who will run the query?  Does it need to be 
>>> run through the DSpace UI, or can it be run in the background?
>>>
>>> Reading your initial note, it sounds like you would like to define a 
>>> facet.  Your initial plan to add a bean to discovery.xml should accomplish 
>>> what you need.
>>>
>>> Assuming you want to create a facet, here are some suggestions.
>>>
>>>- If you wish to create a sidebar facet, add your new bean to the 
>>>list of filters and to the list of sidebar facets.
>>>- After you deploy your updated discovery.xml file, you must 
>>>re-index your repository for the filter/facet to take effect
>>>
>>> The following gist file illustrates a number of custom facets and 
>>> filters that we have defined in our repository: 
>>> https://gist.github.com/terrywbrady/d31fc1bcb9567204470f
>>>
>>> Terry
>>>
>>> On Wed, Dec 21, 2016 at 1:26 AM, Evgeni Dimitrov <dimitr...@gmail.com> 
>>> wrote:
>>>
>>>> Hi helix84,
>>>>
>>>> My thoughts are rather in this direction:
>>>>
>>>> To add somewhere? some code? so that only when the search filter 
>>>> "relation" is applied (with value XXX), to have:
>>>> - a new temporary field relation_kind added - with value isformatof - 
>>>> for every record with (relation.isformatof XXX)
>>>> - a new temporary field relation_kind added - with value isreferencedby 
>>>> - for every record with (relation.isreferencedby XXX)
>>>>
>>>> And to have a facet over relation_kin

Re: [dspace-tech] Is this a possible kind of search?

[Evgeni Dimitrov]

Thank you Terry,

I want a facet, a sidebar facet. But it is a "parameterized" facet.
It makes sense only together with a search filter "relation" 
(dc.relation.*).

There is an item A with dc.identifier=123.
The end-user makes search and adds the filter "relation = 123".
Because the end-user wants all items with some relation to item A.

Only in this context the facet makes sense and it may be produced by

=relation.isbasedon:123
=relation.isformatof:123
=relation.isreferencedby:123

The value of the search (123) is the parameter of the facet.

I mean - we make search for all items with any kind of relation to item A 
(123). And we get a facet with the breakdown by the kind of relation to 
item A. The facet makes sense and is possible only in pair with the search 
filter "relation".

Best regards
Evgeni


On Thursday, December 22, 2016 at 12:28:30 AM UTC+2, Terry Brady wrote:
>
> Are you attempting to create a query or to create a facet?
>
> If you are building a query, who will run the query?  Does it need to be 
> run through the DSpace UI, or can it be run in the background?
>
> Reading your initial note, it sounds like you would like to define a 
> facet.  Your initial plan to add a bean to discovery.xml should accomplish 
> what you need.
>
> Assuming you want to create a facet, here are some suggestions.
>
>- If you wish to create a sidebar facet, add your new bean to the list 
>of filters and to the list of sidebar facets.
>- After you deploy your updated discovery.xml file, you must re-index 
>your repository for the filter/facet to take effect
>
> The following gist file illustrates a number of custom facets and filters 
> that we have defined in our repository: 
> https://gist.github.com/terrywbrady/d31fc1bcb9567204470f
>
> Terry
>
> On Wed, Dec 21, 2016 at 1:26 AM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> Hi helix84,
>>
>> My thoughts are rather in this direction:
>>
>> To add somewhere? some code? so that only when the search filter 
>> "relation" is applied (with value XXX), to have:
>> - a new temporary field relation_kind added - with value isformatof - for 
>> every record with (relation.isformatof XXX)
>> - a new temporary field relation_kind added - with value isreferencedby - 
>> for every record with (relation.isreferencedby XXX)
>>
>> And to have a facet over relation_kind.
>>
>> Anyway, if you think that this is not a viable option, could you please 
>> elaborate on your initial suggestion. Where and how to use this query. And 
>> where is this notation described. I have not seen anything similar. Thank 
>> you again.
>>
>> Best regards
>> Evgeni
>>
>>
>> On Tuesday, December 20, 2016 at 6:23:04 PM UTC+2, helix84 wrote:
>>>
>>> The query you want is:
>>>
>>> (relation.isbasedon:[* TO *] OR relation.isformatof:[* TO *] OR
>>>  relation.isreferencedby:[* TO *]) AND your_identifier:123
>>>
>>> Then use faceting as usual.
>>>
>>>
>>> Regards,
>>> ~~helix84
>>>
>>> Compulsory reading: DSpace Mailing List Etiquette
>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>
>>>
>>> On Tue, Dec 20, 2016 at 3:29 PM, Evgeni Dimitrov <dimitr...@gmail.com> 
>>> wrote:
>>>
>>>> I am wondering - is it possible to have a search like this:
>>>>
>>>> - to find all items, which have in any of
>>>> relation.isbasedon, relation.isformatof, relation.isreferencedby etc.
>>>>
>>>> certain value (the identifier of certain item);
>>>>
>>>> - then to have a facet "relation" with values
>>>> isbasedon (1)
>>>> isformatof (1)
>>>> isreferencedby (3)
>>>>
>>>> I mean - is it possible to have this without too much coding? I am 
>>>> using xmlui - Mirage.
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "DSpace Technical Support" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to dspace-tech...@googlegroups.com.
>>>> To post to this group, send email to dspac...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Grou

Re: [dspace-tech] Is this a possible kind of search?

[Evgeni Dimitrov]

Hi helix84,

My thoughts are rather in this direction:

To add somewhere? some code? so that only when the search filter "relation" 
is applied (with value XXX), to have:
- a new temporary field relation_kind added - with value isformatof - for 
every record with (relation.isformatof XXX)
- a new temporary field relation_kind added - with value isreferencedby - 
for every record with (relation.isreferencedby XXX)

And to have a facet over relation_kind.

Anyway, if you think that this is not a viable option, could you please 
elaborate on your initial suggestion. Where and how to use this query. And 
where is this notation described. I have not seen anything similar. Thank 
you again.

Best regards
Evgeni


On Tuesday, December 20, 2016 at 6:23:04 PM UTC+2, helix84 wrote:
>
> The query you want is:
>
> (relation.isbasedon:[* TO *] OR relation.isformatof:[* TO *] OR
>  relation.isreferencedby:[* TO *]) AND your_identifier:123
>
> Then use faceting as usual.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
> On Tue, Dec 20, 2016 at 3:29 PM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> I am wondering - is it possible to have a search like this:
>>
>> - to find all items, which have in any of
>> relation.isbasedon, relation.isformatof, relation.isreferencedby etc.
>>
>> certain value (the identifier of certain item);
>>
>> - then to have a facet "relation" with values
>> isbasedon (1)
>> isformatof (1)
>> isreferencedby (3)
>>
>> I mean - is it possible to have this without too much coding? I am using 
>> xmlui - Mirage.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Is this a possible kind of search?

[Evgeni Dimitrov]

Thank you helix84,

I can not get your suggestion - where can I place this query?

And I am not sure have I explained clear my goal.
If there are:
- item A (dc.identifier 123)
- item B (dc.relation.isformatof 123)
- item C (dc.relation.isreferencedby 123)
- item D (dc.relation.isreferencedby 123)


I want to have a search filter "relation", which for the value "123" will 
select the items B, C, D

And I want to have a facet "relation" (or similar name), which looks in 
this case like this:

relation
  isformatof (1) --for item B
  isreferencedby (2) --for items C, D

May be the filter can be something like this:


  
  

  dc.relation.*

  


But I have no idea how to approach the facet.

Best regards
Evgeni


On Tuesday, December 20, 2016 at 6:23:04 PM UTC+2, helix84 wrote:
>
> The query you want is:
>
> (relation.isbasedon:[* TO *] OR relation.isformatof:[* TO *] OR
>  relation.isreferencedby:[* TO *]) AND your_identifier:123
>
> Then use faceting as usual.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
> On Tue, Dec 20, 2016 at 3:29 PM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> I am wondering - is it possible to have a search like this:
>>
>> - to find all items, which have in any of
>> relation.isbasedon, relation.isformatof, relation.isreferencedby etc.
>>
>> certain value (the identifier of certain item);
>>
>> - then to have a facet "relation" with values
>> isbasedon (1)
>> isformatof (1)
>> isreferencedby (3)
>>
>> I mean - is it possible to have this without too much coding? I am using 
>> xmlui - Mirage.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Is this a possible kind of search?

[Evgeni Dimitrov]

I am wondering - is it possible to have a search like this:

- to find all items, which have in any of
relation.isbasedon, relation.isformatof, relation.isreferencedby etc.

certain value (the identifier of certain item);

- then to have a facet "relation" with values
isbasedon (1)
isformatof (1)
isreferencedby (3)

I mean - is it possible to have this without too much coding? I am using 
xmlui - Mirage.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] version 5.6?

[Evgeni Dimitrov]

Thank you very much Luigi Andrea,

Best regards
Evgeni

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] version 5.6?

[Evgeni Dimitrov]

Is DSpace version 5.6 expected?

If so, I will be considering an update from 5.4 to 5.6.
Is there any difference in the db schema of 5.4 and 5.6?

The best option for me would be to install, configure and customize 5.6 and
when everything is working to transfer the db. Will this be possible?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: External authentication

[Evgeni Dimitrov]

Well, the problem has a solution with methods like those bellow. But minor 
changes are necessary in AuthenticationManager.java, 
AuthenticationUtil.java, AuthenticateAction.java, because now for them 
SUCCESS in authentication means always and only a non-null EPerson in 
Context.

-
public int authenticate(Context context,
String username,
String password,
String realm,
HttpServletRequest request)
throws SQLException {
HttpSession session = request.getSession();

. . .
if (externalUser(username, password)) {
Group g4 = Group.findByName(context, G4);
int g4id = g4.getID();
Integer g4ID = Integer.valueOf(g4id);

session.setAttribute(G4KEY, g4ID);
return SUCCESS;
}
. . .
}

public int[] getSpecialGroups(Context context,
  HttpServletRequest request) {
try {
HttpSession session = request.getSession();
Integer g4ID = (Integer) session.getAttribute(G4KEY);

if (g4ID != null) {
int g4id = g4ID.intValue();
return new int[] {g4id};
}
}
catch (Exception e) {
}
return new int[0];
}


>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: External authentication

[Evgeni Dimitrov]

Is it possible to have such an authenticate method:

public int authenticate(
Context context, String username, String password, String realm, 
HttpServletRequest request)
throws Exception {
if (validUser(username, password)) {
context.setSpecialGroup(G4);
}
else {
return BAD_CREDENTIALS;
}
}

And if it is possible, then do I need such an getSpecialGroups method?

public int[] getSpecialGroups(Context context, HttpServletRequest request) {
for (Group group: context.getSpecialGroups()) {
. . .
}
return groups;
}


>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] How to authorize a group to add/delete users to another group

[Evgeni Dimitrov]

Yes Monika, I know - this is what I am doing now. And what I want is to 
delegate ONLY this to somebody else. My reason to hope that it could be 
possible is this:
- the policies are attached to resources
- the policies say who can perform an action on the resource (e.g. 
ADD/REMOVE)
- the resource can be any of the DSpace object types: Bitstream: 0; Bundle: 
1; Item: 2; Collection: 3; Community: 4; Site: 5; Group: 6; Eperson: 7.

This is the theory. This is what the DSpace-Manual says. And I am asking 
now - does this exist in reality? Can I attach a policy to a group (saying 
who is authorized to ADD/REMOVE to this group).

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] How to authorize a group to add/delete users to another group

[Evgeni Dimitrov]

I need to authorize a user (a group) to create users and add/delete them to 
one other group.

In DSpace-Manual I see things like "custom policy" (policy_id: 4847; 
resource_type_id: 2; resource_id: 89; ...). There are "DSpace types" 
(Bitstream: 0; ... Group: 6; Eperson: 7).

But I can not figure out - can I use these in order to solve my problem. If 
the solution requires some coding, this is fine by me.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Setting a ResourcePolicy via REST API?

[Evgeni Dimitrov]

I mean that the documentation says

POST /bitstreams/{bitstream id}/policy

and in what you have

curl -X POST 
https://demo.dspace.org/rest/bitstreams/ea41e143-0b2c-447a-a46d-681282c6ff9a/policy
 


the "ea41e143-0b2c-447a-a46d-681282c6ff9a" looks more like 
"rest-dspace-token" than "bitstream id"


On Thursday, August 4, 2016 at 11:58:58 PM UTC+3, Holly Becker wrote:
>
> Hi,
>
> That endpoint gives me item information, but doesn't include anything 
> about bitstreams or policies.  Can you clarify your suggestion?
>
> Thanks,
> -Holly
>
> On Tuesday, July 12, 2016 at 7:38:40 AM UTC-7, Evgeni Dimitrov wrote:
>>
>> I think with curl you should do something like this:
>>
>> curl -X GET -H "Content-Type: application/json" -H "rest-dspace-token: 
>> d4020530-ce01-471d-a474-5fb0cea04661" http://localhost:8080/rest/items/2
>>
>>
>> On Tuesday, July 12, 2016 at 1:46:18 AM UTC+3, Holly Becker wrote:
>>>
>>> Hello all,
>>>
>>> I'm trying to post bitstream policies to the REST API, and having 
>>> trouble finding what the correct format for the ResourcePolicy is.  The 
>>> documentation [1] says a ResourcePolicy is  
>>> [{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":null,"rpName":null,"rpType":"TYPE_INHERITED","startDate":null,"endDate":null}]
>>>   
>>> This looks like the policies returned by /rest/bitstreams/?expand=policies  
>>> However, when I post that policy or policies that look similar I get a 500 
>>> server error [3] on a local install of DSpace 5.
>>>
>>> On demo.dspace.org none of the bitstreams have policies, even when I 
>>> add one in the GUI, and I get a 500 when querying 
>>> https://demo.dspace.org/rest/bitstreams/?expand=policies When posting a 
>>> policy, I get different behavior on demo.dspace.org.  It gives a 400 
>>> error, but the same exception. [2]
>>>
>>> Can someone point me towards more detailed documentation, or provide an 
>>> explanation of what a ResourcePolicy is supposed to look like?  Is there a 
>>> better or different way to set bitstream policies through the REST API or 
>>> SWORD2 API?
>>>
>>> Thanks,
>>> -Holly Becker
>>> Archivematica developer
>>>
>>> [1] https://wiki.duraspace.org/display/DSDOC5x/REST+API
>>>
>>> [2] To reproduce
>>> curl -X POST 
>>> https://demo.dspace.org/rest/bitstreams/ea41e143-0b2c-447a-a46d-681282c6ff9a/policy
>>>  
>>> --data 
>>> '[{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":null,"rpName":null,"rpType":"TYPE_INHERITED","startDate":null,"endDate":null}]'
>>>  
>>> -u 'dspacedemo+ad...@gmail.com:dspace' -H 'Content-type: application/json' 
>>> -k
>>> Response:
>>> Can not deserialize instance of org.dspace.rest.common.ResourcePolicy 
>>> out of START_ARRAY token
>>>  at [Source: 
>>> org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream@43a44ac9;
>>>  
>>> line: 1, column: 1]
>>>
>>> Or (in Python2, requires 'requests' library):
>>> import requests
>>> url = '
>>> https://demo.dspace.org/rest/bitstreams/ea41e143-0b2c-447a-a46d-681282c6ff9a/policy
>>> '
>>> json_body = 
>>> [{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":None,"rpName":None,"rpType":"TYPE_INHERITED","startDate":None,"endDate":None}]
>>> auth = ('dspacede...@gmail.com', 'dspace')
>>> response = requests.post(url, json=json_body, auth=auth, verify=False)
>>> print response  # 
>>> print response.content  # 'Can not deserialize instance of 
>>> org.dspace.rest.common.ResourcePolicy out of START_ARRAY token\n at 
>>> [Source: 
>>> org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream@32229b7e;
>>>  
>>> line: 1, column: 1]'
>>>
>>> [3] Traceback from

[dspace-tech] Re: Setting a ResourcePolicy via REST API?

[Evgeni Dimitrov]

I think with curl you should do something like this:

curl -X GET -H "Content-Type: application/json" -H "rest-dspace-token: 
d4020530-ce01-471d-a474-5fb0cea04661" http://localhost:8080/rest/items/2


On Tuesday, July 12, 2016 at 1:46:18 AM UTC+3, Holly Becker wrote:
>
> Hello all,
>
> I'm trying to post bitstream policies to the REST API, and having trouble 
> finding what the correct format for the ResourcePolicy is.  The 
> documentation [1] says a ResourcePolicy is  
> [{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":null,"rpName":null,"rpType":"TYPE_INHERITED","startDate":null,"endDate":null}]
>   
> This looks like the policies returned by /rest/bitstreams/?expand=policies  
> However, when I post that policy or policies that look similar I get a 500 
> server error [3] on a local install of DSpace 5.
>
> On demo.dspace.org none of the bitstreams have policies, even when I add 
> one in the GUI, and I get a 500 when querying 
> https://demo.dspace.org/rest/bitstreams/?expand=policies When posting a 
> policy, I get different behavior on demo.dspace.org.  It gives a 400 
> error, but the same exception. [2]
>
> Can someone point me towards more detailed documentation, or provide an 
> explanation of what a ResourcePolicy is supposed to look like?  Is there a 
> better or different way to set bitstream policies through the REST API or 
> SWORD2 API?
>
> Thanks,
> -Holly Becker
> Archivematica developer
>
> [1] https://wiki.duraspace.org/display/DSDOC5x/REST+API
>
> [2] To reproduce
> curl -X POST 
> https://demo.dspace.org/rest/bitstreams/ea41e143-0b2c-447a-a46d-681282c6ff9a/policy
>  
> --data 
> '[{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":null,"rpName":null,"rpType":"TYPE_INHERITED","startDate":null,"endDate":null}]'
>  
> -u 'dspacedemo+ad...@gmail.com:dspace' -H 'Content-type: application/json' 
> -k
> Response:
> Can not deserialize instance of org.dspace.rest.common.ResourcePolicy out 
> of START_ARRAY token
>  at [Source: 
> org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream@43a44ac9;
>  
> line: 1, column: 1]
>
> Or (in Python2, requires 'requests' library):
> import requests
> url = '
> https://demo.dspace.org/rest/bitstreams/ea41e143-0b2c-447a-a46d-681282c6ff9a/policy
> '
> json_body = 
> [{"id":317127,"action":"READ","epersonId":-1,"groupId":0,"resourceId":47166,"resourceType":"bitstream","rpDescription":None,"rpName":None,"rpType":"TYPE_INHERITED","startDate":None,"endDate":None}]
> auth = ('dspacede...@gmail.com ', 'dspace')
> response = requests.post(url, json=json_body, auth=auth, verify=False)
> print response  # 
> print response.content  # 'Can not deserialize instance of 
> org.dspace.rest.common.ResourcePolicy out of START_ARRAY token\n at 
> [Source: 
> org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream@32229b7e;
>  
> line: 1, column: 1]'
>
> [3] Traceback from DSpace 5 server (catalina.out)
>
> Jul 11, 2016 6:13:58 PM com.sun.jersey.spi.container.ContainerResponse 
> mapMappableContainerException
> SEVERE: The exception contained within MappableContainerException could 
> not be mapped to a response, re-throwing to the HTTP container
> org.codehaus.jackson.map.JsonMappingException: Can not deserialize 
> instance of org.dspace.rest.common.ResourcePolicy out of START_ARRAY token
>  at [Source: org.apache.catalina.connector.CoyoteInputStream@4c4b6dda; 
> line: 1, column: 1]
> at 
> org.codehaus.jackson.map.JsonMappingException.from(JsonMappingException.java:163)
> at 
> org.codehaus.jackson.map.deser.StdDeserializationContext.mappingException(StdDeserializationContext.java:219)
> at 
> org.codehaus.jackson.map.deser.StdDeserializationContext.mappingException(StdDeserializationContext.java:212)
> at 
> org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromArray(BeanDeserializer.java:869)
> at 
> org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:597)
> at 
> org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:2695)
> at 
> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1308)
> at 
> org.codehaus.jackson.jaxrs.JacksonJsonProvider.readFrom(JacksonJsonProvider.java:419)
> at 
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy.readFrom(JacksonProviderProxy.java:139)
> at 
> com.sun.jersey.spi.container.ContainerRequest.getEntity(ContainerRequest.java:490)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.EntityParamDispatchProvider$EntityInjectable.getValue(EntityParamDispatchProvider.java:123)
> at 
> com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:86)
> at 
> 

[dspace-tech] Re: xmlui.Discovery.AbstractSearch.type_department message

[Evgeni Dimitrov]

Hi Susan,

You can find 

...\apache-tomcat-8.0.30\webapps\xmlui\WEB-INF\lib\dspace-xmlui-5.4-classes.jar

and inside it (because it is like zip file) you can find

dspace-xmlui-5.4-classes.jar\aspects\Discovery\i18n\messages.xml

Inside this messages file is 

Filter by: 
Author

==

On Wednesday, June 22, 2016 at 9:22:52 PM UTC+3, Susan Borda wrote:
>
> Hi All-
> This appears when with 
> http://scholarworks.montana.edu/xmlui/search-filter?field=department
> “xmlui.Discovery.AbstractSearch.type_department"
>
> When field=department is swapped with field=author this is what I get:
> "Filter by: Author”
>
> I looked in $CATALINA_HOME/webapps/xmlui/i18n/messages.xml (where I 
> usually resolve these sorts of issues) for the “Filter by: Author” and am 
> not finding it. 
>
> I’m not sure how this was first discovered as someone just sent the 
> “offending” URL to me. Also, I have seen this same issue on a number of 
> other Dspace instances.
>
> Any thoughts?
>
> Thanks,
> susan
> — 
> Susan Borda
> Digital Technologies Development Librarian
> Montana State University Library
> 406-994-1873
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] 4 questions about DELETE

[Evgeni Dimitrov]

1. Can a community be deleted if there are non-empty collections in it
(items are owned by collections in the community)?

2. Can a community be deleted if there are only empty collections in it?

3. Can a collection be deleted if there are items in it (owned by the
collection)?

4. What could be the reason to allow to the community admin to delete
subcommunities but not to delete collections?


for COMMUNITIES - in
org.dspace.app.xmlui.aspect.administrative.community.EditCommunityMetadataForm:

if (AuthorizeManager.authorizeActionBoolean(context, thisCommunity,
Constants.DELETE))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}

for COLLECTIONS - in
org.dspace.app.xmlui.aspect.administrative.collection.EditCollectionMetadataForm:

//Only System Admins can Delete Collections
if (AuthorizeManager.isAdmin(context))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Can not delete a collection (DSpace 5.4)

[Evgeni Dimitrov]

Well, this has been done on purpose:

for COMMUNITIES - in 
org.dspace.app.xmlui.aspect.administrative.community.EditCommunityMetadataForm:

if (AuthorizeManager.authorizeActionBoolean(context, thisCommunity, 
Constants.DELETE))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}

for COLLECTIONS - in 
org.dspace.app.xmlui.aspect.administrative.collection.EditCollectionMetadataForm:

//Only System Admins can Delete Collections
if (AuthorizeManager.isAdmin(context))
{
buttonList.addButton("submit_delete").setValue(T_submit_delete);
}

Could somebody explain - why was decided that "Only System Admins can 
Delete Collections"?


On Friday, June 24, 2016 at 3:35:03 PM UTC+3, Evgeni Dimitrov wrote:
>
> DSpace 5.4
>
> I have
> - community A
> - in A - subcommunity B
> - in B - collection C
>
> 1. I have an user with "admin" rights on A
> - he can not delete B
> - he can not delete C
>
> 2. I have an user with
> -"admin" rights on A
> -"remove" rights on A
> - he can delete B
> - he can not delete C
>
> For one community I need an user who is allowed to do everything (delete 
> including) with the lower level subcommunities and collections. How to do 
> this?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Can not delete a collection (DSpace 5.4)

[Evgeni Dimitrov]

DSpace 5.4

I have
- community A
- in A - subcommunity B
- in B - collection C

1. I have an user with "admin" rights on A
- he can not delete B
- he can not delete C

2. I have an user with
-"admin" rights on A
-"remove" rights on A
- he can delete B
- he can not delete C

For one community I need an user who is allowed to do everything (delete
including) with the lower level subcommunities and collections. How to do
this?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] REST API metadata DELETE PUT

[Evgeni Dimitrov]

About DSpace 5.4
In the DSpace-Manual something may be missing and something is not quite
correct.
I am saying this, because if the description is vague, it is not certain
how will the next version behave.

DELETE. It says

DELETE /items/{item id}/metadata - Clear item metadata.

It seems that some metadata remains
dc.identifier.uri
dc.date.accessioned
dc.date.available
dc.description.provenance

PUT. It says

PUT /items/{item id}/metadata - Update metadata in item. You must put a
MetadataEntry

Actually it expects an array of MetadataEntry

It seems to me that:
- if there is a MetadataEntry both in the array and existing, then it is
updated
- if there is a MetadataEntry in the array and NOT existing, then it is
added

Could, please, somebody comment/clarify about this.

Best regards

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Downloading a bitstream using XMLUI

[Evgeni Dimitrov]

And I am wondering - if the bitstream (in my case the only bitstream in the 
THUMBNAIL bundle) is downloaded through XMLUI - will this affect the usage 
statistics of this item?

On Friday, June 10, 2016 at 11:34:22 PM UTC+3, Evgeni Dimitrov wrote:
>
> In the DSpace-Manual it is documented how to get a bitstream using REST:
>
> //dspace.xx.xx:8080/rest/bitstreams/290183/retrieve
>
> But the bitstream can be downloaded using XMLUI:
>
> //dspace.xx.xx:8080/xmlui/bitstream/nls/22290/10001/*
>
> I believe that this is also documented - the rule how to create the above 
> link, based on xmlui.
> Could somebody point to the place where this is documented.
>
> Best regards
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Downloading a bitstream using XMLUI

[Evgeni Dimitrov]

In the DSpace-Manual it is documented how to get a bitstream using REST:

//dspace.xx.xx:8080/rest/bitstreams/290183/retrieve

But the bitstream can be downloaded using XMLUI:

//dspace.xx.xx:8080/xmlui/bitstream/nls/22290/10001/*

I believe that this is also documented - the rule how to create the above
link, based on xmlui.
Could somebody point to the place where this is documented.

Best regards

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Usage Statistics and the REST API

[Evgeni Dimitrov]

Thank you very much Peter,

In my case this is an excellent solution.

Best regards
Evgeni

On Wednesday, June 8, 2016 at 7:40:40 PM UTC+3, Peter Dietz wrote:
>
> Hi Evgeni,
>
> If your concern is that using REST increased the usage count, then you can 
> disable UsageEvents from being counted by REST through a config. 
>
> config/modules/rest.cfg
>
> https://wiki.duraspace.org/display/DSDOC5x/REST+API#RESTAPI-ConfigurationforDSpaceREST
>
> There's no parameter you can add to a rest request that says "this is an 
> insignificant request, please don't count this as usage". All or nothing.
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Wed, Jun 8, 2016 at 9:50 AM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> I am getting the usage statistics (top 100 titles) for a community with
>>
>> // http://localhost:8080/solr/statistics/select
>> // ?q=type:2=owningComm:12
>> // =time:[2016-05-01T00:00:00Z TO 2016-06-01T00:00:00Z]
>> // =0=true=id
>> // =100=on
>>
>> as a list of pairs (count, id).
>>
>> To give to the librarian a nice result, I am replacing the id with the 
>> handle and the title of the book.
>> Using
>> REST GET /items/{item id}
>>
>> Works fine, but every time I run the report, the count (the usage) of 
>> this 100 books is increased by one :(
>>
>> Will it be the same, if instead of
>> GET /items/{item id}
>>
>> I use
>> GET /items/{item id}/metadata
>>
>> ??
>>
>> If the answer is "yes", is there any unintrusive way to decode the item 
>> id into handle + title?
>>
>> Best regards
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] One item many collections on 5.x

[Evgeni Dimitrov]

Hi Claudia,

There is in Item a method 
public Collection[] getCollections()

so that there may be many collections of one item
but there is only one
public Collection getOwningCollection()

Could you explain the difference?

Best regards
Evgeni


On Monday, May 30, 2016 at 5:40:49 PM UTC+3, Claudia Jürgen wrote:
>
> Hi Tiago,
>
> yes you can map items see:
> https://wiki.duraspace.org/display/DSDOC5x/Mapping+Items
>
> Hope this helps
>
> Claudia Jürgen
>
> Am 30.05.2016 um 16:15 schrieb Tiago Delboni:
>
> Hi!
>
> Is it possible to assign one item to more than one collection? I couldn't 
> find a way to do it using the JSPUI of DSpace 5.x.
>
> Tiago Delboni
>
>
>
> -- 
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32claudia...@tu-dortmund.de 
> www.ub.tu-dortmund.de
>
>
>
>
> *Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz 
> per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, 
> wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder 
> durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. 
> Important note: The information included in this e-mail is confidential. It 
> is solely intended for the recipient. If you are not the intended recipient 
> of this e-mail please contact the sender and delete this message. Thank 
> you. Without prejudice of e-mail correspondence, our statements are only 
> legally binding when they are made in the conventional written form (with 
> personal signature) or when such documents are sent by fax. * 
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: [Dspace-tech] Bulk METS ingest

[Evgeni Dimitrov]

Hi Pedro,

I will attach two files - the whole program and the pom.xml. The program 
runs standalone on the server, for every item reads a directory, zips it 
and creates the item. The program is as I needed it in my case. I think you 
need a Java developer to make it work for you.

Best regards
Evgeni

On Tuesday, May 31, 2016 at 2:58:05 PM UTC+3, Pedro Amorim wrote:
>
> Hello Evgeni,
>
> Yes that is definetly an option for me, even being an alternative solution.
> I was already planning on developing a script in shell to package folders 
> in zips and run dspace/bin packager for each of them.
>
> Would you please elaborate on:
>
> // get parent object
> parentObj = HandleManager
> .resolveToObject(context, itemParentHandle);
> 
> // create a single item
> itemObj = metsIngester.ingest(
> context,
> parentObj,
> zippedItemPath.toFile(),
> pkgParams,
> null
> );
>
> I'm not the most experienced Java developer and wouldn't know how to 
> implement custom code in DSpace.
>
> Thank you so much for replying.
>
> Cheers,
>
> Pedro Amorim
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
// DSPItemCreator.java
//

package bg.nalis.dsptools;

import java.io.BufferedReader;
import java.io.BufferedWriter;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.PrintWriter;
import java.nio.charset.Charset;
import java.nio.charset.StandardCharsets;
import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.Arrays;
import java.util.Collections;
import java.util.List;
import java.util.Map;
import java.util.TreeMap;
import java.util.zip.ZipEntry;
import java.util.zip.ZipOutputStream;

import org.dspace.content.DSpaceObject;
import org.dspace.content.packager.PackageIngester;
import org.dspace.content.packager.PackageParameters;
import org.dspace.core.ConfigurationManager;
import org.dspace.core.Context;
import org.dspace.core.PluginManager;
import org.dspace.eperson.EPerson;
import org.dspace.handle.HandleManager;
import org.dspace.servicemanager.DSpaceKernelInit;

/**
 * The class creates items.
 */
public class DSPItemCreator {
	
	// logWriter
	private BufferedWriter logWriter;

// - Final Fields
	private static final String ADMIN_PERSON_EMAIL = "ad...@admin.xx";

	// directory
	private static final String ITEMS_DIR = "/stagingarea/dtlexports/mets/";
	
	// fileNames
	private static final String ITEMS_MAP = "items_map.txt";
	private static final String COLLECTIONS_MAP = "collections_map.txt";
	private static final String ITEM_ZIPPED = "item.zip";
	private static final String ERRLOG = "errlog.txt";
	private static final Charset FILEENCODING = StandardCharsets.UTF_8;

// - Fields
	private Map itemsMap;
	private Map collectionsMap;
	private List itemsList;

// - Methods
/**
 *
 */
public static void main(String[] args) {
	new DSPItemCreator().go();
}

/**
 *
 */
private void go() {
		// try to create logWriter and exit on failure
		try {
			Path logPath = Paths.get(ERRLOG);
			logWriter = Files.newBufferedWriter(logPath, FILEENCODING);
		}
		catch (IOException e) {
			return;
		}
		try {
			createItem();
		}
		catch (Throwable t) {
			t.printStackTrace();
			logTrace(t);
		}
		try {
			logWriter.close();
		}
	catch (Exception ex) {}
}

/**
 *
 */
private void createItem() {
		// context
		Context context = null;
		
		// parameters
		PackageParameters pkgParams = new PackageParameters();
		pkgParams.setWorkflowEnabled(false);
		
		// ingester
		PackageIngester metsIngester = null;
		
	try {
		// read files
		itemsMap = readFileToMap(ITEMS_MAP, FILEENCODING);
		collectionsMap = readFileToMap(COLLECTIONS_MAP, FILEENCODING);
		
		// read directory
		Path dirPath = Paths.get(ITEMS_DIR);
 	File dir = dirPath.toFile();
		String[] subDirs = dir.list();
		itemsList = Arrays.asList(subDirs);
		Collections.sort(itemsList);

		//--- start services ---
		( DSpaceKernelInit
.getKernel(null) )
		.start(ConfigurationManager.getProperty("dspace.dir"));
		
		// get ingester
		metsIngester = (PackageIngester) 

[dspace-tech] Re: [Dspace-tech] Bulk METS ingest

[Evgeni Dimitrov]

Hi Pedro,

Recently I migrated thousands of objects to DSpace, but I made a separate 
zip file for every one. The zip file contains the files (bitstreams) and 
the mets file. The zip files are ingested programmatically:

// get parent object
parentObj = HandleManager
.resolveToObject(context, itemParentHandle);

// create a single item
itemObj = metsIngester.ingest(
context,
parentObj,
zippedItemPath.toFile(),
pkgParams,
null
);

I don't know is this an option for you?

About your first email:
When I look at the mets.xml file of an item with Edit this Item / Item 
Bitstreams / View - I see that it is exactly as ingested. Perhaps in your 
case something got distorted during the export.
In my case the struct map in the mets.xml describes the structure of the 
book. Somethig like






. . .

Best regards
Evgeni


On Monday, May 30, 2016 at 6:09:57 PM UTC+3, Pedro Amorim wrote:
>
> Hello Evgeni, 
>>
>
> I am also having the same problem.
> I'll share the post I made in dspace-community for introduction:
>
> https://groups.google.com/forum/#!searchin/dspace-community/Questions$20regarding$20METS$2FAIP$20ingestion$20in$20DSpace/dspace-community/1OrWeDfnD20/ECZWJv9oBgAJ
>
> 1)
> If I import the collection using -t METS, the following error message 
> happens:
>  java.lang.ClassCastException: org.dspace.content.Community cannot be cast 
> to org.dspace.content.Collection
>
> 2)
> If I import the collection using -t AIP (after changing the PROFILE, etc), 
> the following happens:
> "METS document is missing the required structMap[@LABEL='Parent'] element."
>
> NOTE: I did not export from an existing DSpace. I'm importing METS items 
> for the first time in DSpace.
> What I *think* is happening is, for the -t METS, DSpace won't recognize 
> the mets package as a collection, instead it will interpret it as an Item, 
> as such, when interpreting the parent in the structMap of the collection 
> being imported (a community), it'll interpret it as a collection, instead 
> of a community. Hence the message.
> After that I tried with -t AIP and have the message in 2). What I *think* 
> happens in this case is it's complaining because the structMap in the ITEMS 
> (not the COLLECTION package being imported) is non-existent. But why would 
> it exist? I'm importing the COLLECTION package that already defines each 
> ITEM package contained in it. Additionally, even if I wanted to inject some 
> structMap for each ITEM (just to bypass this) how would I? I don't know the 
> handle of the parent collection because I'm submitting it for the first 
> time.
>
> I hope this wasn't too confusing.
> Any help would be greatly appreciated.
>
> Thank you,
>
> Pedro Amorim
>
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] A bug in REST API introduced in 5.3 or 5.4

[Evgeni Dimitrov]

Perhaps the idea was to have context.complete() after normal execution. 
Which is missing.

On Tuesday, February 23, 2016 at 10:29:30 PM UTC+2, Peter Dietz wrote:
>
> Look at Git Blame to find out why things changed:
>
> https://github.com/DSpace/DSpace/blame/dspace-5_x/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java
>
> And that line leads to:
> https://github.com/DSpace/DSpace/pull/1007
>
> So, adding that was intending to prevent stale connections / contexts from 
> being held open for a very long time, and behave like other endpoints. The 
> problem was that you could view /rest/handle, and get data, then change 
> that object, and the next time you view that /rest/handle, the data would 
> not have changed. 
>
> If you have a stack trace, please consider investigating the root of the 
> bug for 5x. In the upcoming DSpace 6x, contexts are completely different 
> with the services refactor, and changes here would have limited utility.
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Tue, Feb 23, 2016 at 3:19 PM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after 
>> the line:
>>
>> return new Community((org.dspace.content.Community) dso, expand, context);
>>
>> some lines are added:
>>
>> } finally{
>> processFinally(context);
>> }
>>
>> Because context is not null and valid, processFinally generates 500 
>> "INTERNAL_SERVER_ERROR"
>>
>> What was the intention for adding "finally" there? What should be the 
>> fix? I can just delete these lines . . .
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] A bug in REST API introduced in 5.3 or 5.4

[Evgeni Dimitrov]

I am not getting this. Now processFinally is called always - after 
exception and after normal execution - and it always generates 500 
"INTERNAL_SERVER_ERROR".
It is true that in addition it aborts the context, but . . .

On Tuesday, February 23, 2016 at 10:29:30 PM UTC+2, Peter Dietz wrote:
>
> Look at Git Blame to find out why things changed:
>
> https://github.com/DSpace/DSpace/blame/dspace-5_x/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java
>
> And that line leads to:
> https://github.com/DSpace/DSpace/pull/1007
>
> So, adding that was intending to prevent stale connections / contexts from 
> being held open for a very long time, and behave like other endpoints. The 
> problem was that you could view /rest/handle, and get data, then change 
> that object, and the next time you view that /rest/handle, the data would 
> not have changed. 
>
> If you have a stack trace, please consider investigating the root of the 
> bug for 5x. In the upcoming DSpace 6x, contexts are completely different 
> with the services refactor, and changes here would have limited utility.
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Tue, Feb 23, 2016 at 3:19 PM, Evgeni Dimitrov <dimitr...@gmail.com 
> > wrote:
>
>> Comparing 5.2 and 5.4 - org.dspace.rest.HandleResource - I see that after 
>> the line:
>>
>> return new Community((org.dspace.content.Community) dso, expand, context);
>>
>> some lines are added:
>>
>> } finally{
>> processFinally(context);
>> }
>>
>> Because context is not null and valid, processFinally generates 500 
>> "INTERNAL_SERVER_ERROR"
>>
>> What was the intention for adding "finally" there? What should be the 
>> fix? I can just delete these lines . . .
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Something wrong with REST API - DSpace 5.4

[Evgeni Dimitrov]

I have used REST API with DSpace 5.2 and Windows. Now I am trying with
DSpace 5.4 and Linux. Doing not the same but very similar thing. Trying to
get a community by handle.

I am getting in the DSpace log

2016-02-23 17:24:12,947 INFO  org.dspace.rest.RestIndex @ REST Login
Success for user: @
2016-02-23 17:24:12,973 INFO  org.dspace.rest.HandleResource @ DSO Lookup
by handle: [nls] / [94] got result of: COMMUNITY_17
2016-02-23 17:24:13,091 ERROR org.dspace.rest.Resource @ Something get
wrong. Aborting context in finally statement.
2016-02-23 17:24:13,104 INFO  org.dspace.rest.RestIndex @ REST Logout:
@

In the Tomcat log there is more - see bellow.

Has anybody any ideas?


23-Feb-2016 17:24:13.091 SEVERE [http-nio-8080-exec-4]
com.sun.jersey.spi.container.ContainerResponse.logException Mapped
exception to response: 500 (Internal Server Error)
 javax.ws.rs.WebApplicationException
at org.dspace.rest.Resource.processFinally(Resource.java:169)
at org.dspace.rest.HandleResource.getObject(HandleResource.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:521)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1096)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:674)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1500)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1456)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

-- 
You received this message because 

[dspace-tech] Missing dependency in DSpace 5.4 ??

[Evgeni Dimitrov]

I have a small application, which adds items to DSpace. It works in DSpace
5.2.

In DSpace 5.4 it fails at

( DSpaceKernelInit.getKernel(null) )
 .start(ConfigurationManager.getProperty("dspace.dir"));

with
 java.lang.NoClassDefFoundError: javax/servlet/ServletRequest

I am building the application with Maven with a single dependency:


  org.dspace
  dspace-api
  5.4


And I see that there is a difference in the .jars when building for 5.2 and
5.4

What can be done in this case?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Missing dependency in DSpace 5.4 ??

[Evgeni Dimitrov]

I added
   servlet-api-2.5-20081211.jar

And it seems this problem was resolved...

On Friday, January 8, 2016 at 1:28:36 PM UTC+2, Evgeni Dimitrov wrote:
>
> I have a small application, which adds items to DSpace. It works in DSpace 
> 5.2.
>
> In DSpace 5.4 it fails at
>
> ( DSpaceKernelInit.getKernel(null) )
>  .start(ConfigurationManager.getProperty("dspace.dir"));
>
> with
>  java.lang.NoClassDefFoundError: javax/servlet/ServletRequest
>
> I am building the application with Maven with a single dependency:
>
> 
>   org.dspace
>   dspace-api
>   5.4
> 
>
> And I see that there is a difference in the .jars when building for 5.2 
> and 5.4
>
> What can be done in this case?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] In DSpace 5.4 something dubious with the crosswalks ?

[Evgeni Dimitrov]

On ingest I am getting a message

org.dspace.core.PluginInstantiationException: Cannot load plugin class:
java.lang.ClassNotFoundException:
org.dspace.content.crosswalk.MARCIngestionCrosswalk

But there is a file

/dspace/dspace-5.4-src-release/dspace-api/target/classes/org/dspace/content/crosswalk/MARCIngestionCrosswalk.class

And it works in DSpace 5.2 ...

Any ideas?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: In DSpace 5.4 something dubious with the crosswalks ?

[Evgeni Dimitrov]

My mistake - the generated dspace-api-5.4.jar was not in the classpath...

On Friday, January 8, 2016 at 3:25:05 PM UTC+2, Evgeni Dimitrov wrote:
>
> On ingest I am getting a message
>
> org.dspace.core.PluginInstantiationException: Cannot load plugin class: 
> java.lang.ClassNotFoundException: 
> org.dspace.content.crosswalk.MARCIngestionCrosswalk
>
> But there is a file
>
>
> /dspace/dspace-5.4-src-release/dspace-api/target/classes/org/dspace/content/crosswalk/MARCIngestionCrosswalk.class
>
> And it works in DSpace 5.2 ...
>
> Any ideas?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Migrating a community

[Evgeni Dimitrov]

I have in DSpace 5.2 a community with 60 collections and 16000 items.
I want to have a copy of this community in another DSpace installation.

>From the Manual it seems to me that exporting - both "packager" and
"export" will create in one directory 16000 subdirectories.

1. Is this the best what I can do in this situation?

2. To every item I have a mets.xml file and I would like to have it the
same in the new place. Is "packager" or "export"/"import" better for this
job?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Can not ingest an Item

[Evgeni Dimitrov]

I am trying to ingest an Item:

--
// get ingester
PackageIngester metsIngester = (PackageIngester) PluginManager
.getNamedPlugin(PackageIngester.class, "METS");

// get context
Context context = getContext();

// get parent object
String parentHandle = "123456789/93";
DSpaceObject parentObj = HandleManager
.resolveToObject(context, parentHandle);

// get zipped item file
String zippedItemName = "146900.zip";
File zippedItemFile = new File(zippedItemName);

// set parameters
PackageParameters pkgParams = new PackageParameters();
pkgParams.setWorkflowEnabled(false);

// create a single item
metsIngester.ingest(
context,
parentObj,
zippedItemFile,
pkgParams,
null
);
--

This fails:
java.lang.IllegalStateException: DSpace kernel cannot be null

I can not see in the Packager class how the Kernel is started, but here I
added in the beginning:
( DSpaceKernelInit.getKernel(null) ).start();

Then it fails differently:
2015-11-05 23:11:50,880 INFO  org.dspace.content.Bitstream @ e...@xxx.yy
::update_bitstream:bitstream_id=284
2015-11-05 23:11:50,889 ERROR
org.dspace.identifier.VersionedHandleIdentifierProvider @ e...@xxx.yy::Error
while attempting to create handle:Item id\colon; 64
java.lang.NullPointerException
at
org.dspace.identifier.VersionedHandleIdentifierProvider.retrieveVersionHistory(VersionedHandleIdentifierProvider.java:625)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.mint(VersionedHandleIdentifierProvider.java:250)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.register(VersionedHandleIdentifierProvider.java:82)
at
org.dspace.identifier.IdentifierServiceImpl.register(IdentifierServiceImpl.java:83)
at org.dspace.content.InstallItem.installItem(InstallItem.java:67)
at
org.dspace.content.packager.PackageUtils.finishCreateItem(PackageUtils.java:537)
at
org.dspace.content.packager.AbstractMETSIngester.ingestObject(AbstractMETSIngester.java:510)
at
org.dspace.content.packager.AbstractMETSIngester.ingest(AbstractMETSIngester.java:228)
at bg.nalis.dsptools.DSPItemCreator.go(DSPItemCreator.java:106)

Any ideas - what is wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Two administrators with different privileges??

[Evgeni Dimitrov]

I have one Eperson "", created during installation with "dspace
create-administrator".

I have another Eperson "" created from the command line with:
dspace user --add -m b...@nomail.xx -p  -g BB -s BB

Both users are in the group "Administrator".

I can login as "":
d:\apps\curl\curl -H "Content-Type: application/json" --data
"{\"email\":\"a...@nomail.xx\", \"password\":\"\"}"
http://localhost:8080/rest/login

and I can create a collection:

d:\apps\curl\curl -X POST -H "Content-Type: application/json" -H
"rest-dspace-token: " --data
"{\"name\":\"People\"}"
http://localhost:8080/rest/communities/3/collections > d:\adir\log


When I do the same with Eperson "", I do login, but when I try to
create the collection, I get "Unauthorized", "This request requires HTTP
authentication.".

"" is administrator - I can login as "" to XMLUI and I can delete
the collection, but as if "" is not good enough to create the
collection??

Any ideas what may be wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Two administrators with different privileges??

[Evgeni Dimitrov]

My mistake - the token used was produced before and after the Eperson 
became administrator, but without a "logout" in between.

On Tuesday, November 3, 2015 at 3:17:48 PM UTC+2, Evgeni Dimitrov wrote:
>
> I have one Eperson "", created during installation with "dspace 
> create-administrator".
>
> I have another Eperson "" created from the command line with:
> dspace user --add -m b...@nomail.xx -p  -g BB -s BB
>
> Both users are in the group "Administrator".
>
> I can login as "":
> d:\apps\curl\curl -H "Content-Type: application/json" --data 
> "{\"email\":\"a...@nomail.xx\", \"password\":\"\"}"  
> http://localhost:8080/rest/login
>
> and I can create a collection:
>
> d:\apps\curl\curl -X POST -H "Content-Type: application/json" -H 
> "rest-dspace-token: " --data 
> "{\"name\":\"People\"}"  
> http://localhost:8080/rest/communities/3/collections > d:\adir\log
>
>
> When I do the same with Eperson "", I do login, but when I try to 
> create the collection, I get "Unauthorized", "This request requires HTTP 
> authentication.".
>
> "" is administrator - I can login as "" to XMLUI and I can delete 
> the collection, but as if "" is not good enough to create the 
> collection??
>
> Any ideas what may be wrong?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.