Re: [dspace-tech] Issues with REST find-by-metadata-field in DSpace 5
Hi,
I tried to do something similar (all items with something in the field X), but
it seems that find-by-metadata-field does not support wildcards, only exact
matches. Helix84 suggested SOLR for me, There's also a new REST api for reports
in 6.0 (Terry Brady suggested that to me). You can probably find the threads
with my name & those mentioned.
For the other question, are there differences in the item access permissions
and/or if any of the items are in the workflow or in the collections. I think
the SQL queries will give you all the items, but I think there is some
filtering done with the REST - didn't look very deeply into that, though.
Ilja
From: dspace-tech@googlegroups.com on behalf of
Alan Orth
Sent: Thursday, November 10, 2016 1:38:34 PM
To: DSpace Technical Support
Subject: [dspace-tech] Issues with REST find-by-metadata-field in DSpace 5
Hi,
We're trying to build an application that uses metadata from DSpace's REST API
and I'm having some issues. We're testing on DSpace 5.5 with PostgreSQL.
First, it seems there is no way to use a wildcard value with the
find-by-metadata-field endpoint—I want all items where a field
`cg.subject.ilri` exists. Second, for another query, I'm not sure that the API
is returning the correct results. Taking into account the text_lang of the
metadata, the following database queries and REST API results don't add up.
Here are the database results for null, blank, and en_US text_lang values:
dspace=# select count(text_value) from metadatavalue where resource_type_id=2
and metadata_field_id=203 and text_value='SEEDS' and text_lang is null;
count
---
15
dspace=# select count(text_value) from metadatavalue where resource_type_id=2
and metadata_field_id=203 and text_value='SEEDS' and text_lang='';
count
---
4
dspace=# select count(text_value) from metadatavalue where resource_type_id=2
and metadata_field_id=203 and text_value='SEEDS' and text_lang='en_US';
count
---
66
Then the API results, in the order of null, blank, and en_US language:
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X
POST "http://localhost:8080/rest/items/find-by-metadata-field"; -d '{"key":
"cg.subject.ilri","value": "SEEDS"}' | jq length
55
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X
POST "http://localhost:8080/rest/items/find-by-metadata-field"; -d '{"key":
"cg.subject.ilri","value": "SEEDS", "language":""}' | jq length
34
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X
POST "http://localhost:8080/rest/items/find-by-metadata-field"; -d '{"key":
"cg.subject.ilri","value": "SEEDS", "language":"en_US"}' | jq length
The results don't even remotely match, and there are actually more results from
the API than from the database (85 vs 89).
Does anyone know what's up with either of these issues? Thanks,
--
Alan Orth
alan.o...@gmail.com
https://englishbulgaria.net
https://alaninkenya.org
https://mjanja.ch
--
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.
--
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] DSpace current master: ERROR: prepared statement "S_29" does not exist
I created an issue here: https://jira.duraspace.org/browse/DS-3335 and if I find anything more, I'll record it. Ilja From: dspace-tech@googlegroups.com on behalf of Tim Donohue Sent: Thursday, September 22, 2016 4:58:15 PM To: dspace-tech@googlegroups.com Subject: Re: [dspace-tech] DSpace current master: ERROR: prepared statement "S_29" does not exist Hi Ilja, Thanks for noting this. I have not yet encountered this error, but it definitely would be worth trying to find a way to reliably reproduce it (if possible). From the error stacktrace you linked to, it looks like the problem originates in the UploadWithEmbargoStep of the submission process (at least in this example). If you are able to recreate this error again, it might be interesting to see what is similar between each of the stacktraces. Is it a single submission step to blame? Does the error occur more randomly (in different submission steps)? Essentially if we can find a similarity between these stacktraces or a way to reliably reproduce the error, it would help us in determining whether this is only encountered with particular configurations/setups, and/or what the root cause may be. You are welcome to create a ticket for investigating this issue, as that may be a better place to add notes should anyone encounter this issue. If we find it to be a non-issue, we can always close the ticket. Thanks, and please do let us know if you find ways to reproduce or similarities between the error stacktraces. - Tim On 9/22/2016 5:28 AM, Ilja Sidoroff wrote: > I've been testing the latest git master (upcoming DS 6), and since pulling > the latest changes on Tuesday, I've encountered errors like: > > ERROR: prepared statement "S_29" does not exist > (a paste for the full stack trace: http://pastebin.com/2mLKNNHD) > > (where "S_29" varies). The errors seem to happen when I use workflow > functionality and try to submit something, or directly try to submit > something to a collection. When the error state is on, I cannot start new > submissions, upload bitstreams from the workflow, or upload bitstreams from > administration->edit item - and possibly more. I don't know exactly what are > the conditions for reproducing this nor I know how to recover from the state. > I managed recovery once by restarting postgres, but in general it doesn't > seem to help. > > I first encountered this on Tuesday and asked help on irc. Helix84 did some > googling and one reason this might happen, is some sort of concurrency > problem, where the original PSTMT gets deleted/flushed out and is not > available when resumed (unfortunately I don't have the reference or the irc > log). > > My environment is: Ubuntu 16.04, Java 1.8, Jetty 9, PostgreSQL 9.5. I'll > continue examining the issue to determine if it is just something in my own > environment or a genuine bug. > > br, > > Ilja Sidoroff > University of Eastern Finland > -- 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. -- 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] DSpace current master: ERROR: prepared statement "S_29" does not exist
I've been testing the latest git master (upcoming DS 6), and since pulling the latest changes on Tuesday, I've encountered errors like: ERROR: prepared statement "S_29" does not exist (a paste for the full stack trace: http://pastebin.com/2mLKNNHD) (where "S_29" varies). The errors seem to happen when I use workflow functionality and try to submit something, or directly try to submit something to a collection. When the error state is on, I cannot start new submissions, upload bitstreams from the workflow, or upload bitstreams from administration->edit item - and possibly more. I don't know exactly what are the conditions for reproducing this nor I know how to recover from the state. I managed recovery once by restarting postgres, but in general it doesn't seem to help. I first encountered this on Tuesday and asked help on irc. Helix84 did some googling and one reason this might happen, is some sort of concurrency problem, where the original PSTMT gets deleted/flushed out and is not available when resumed (unfortunately I don't have the reference or the irc log). My environment is: Ubuntu 16.04, Java 1.8, Jetty 9, PostgreSQL 9.5. I'll continue examining the issue to determine if it is just something in my own environment or a genuine bug. br, Ilja Sidoroff University of Eastern Finland -- 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 organize customizations in dspace?
I started with having a separate repository and a shell script that copied changed files from that repository to the original sources, which IMO works well as long as you don't make too many changes to the code. After I started having more changes in the code, not only in configuration, I started using patches. I have a DSpace git-tree, from where I generate patches for my changes. I then store the patches to a different repository and use quilt to apply them to the original sources. br, Ilja Sidoroff University of Eastern Finland From: dspace-tech@googlegroups.com on behalf of Christoph Weber Sent: Wednesday, September 14, 2016 4:31:38 PM To: DSpace Technical Support Subject: [dspace-tech] How to organize customizations in dspace? Hello, I'm currently setting up our dspace instance and doing a few changes to customize it. Till. ex. some changes in [dspace-source]/config/input-forms.xml and [dspace-source]/config/registries/dublin-core-types.xml to support DOI. Now I wonder what the best way is to preserve this changes after an update of dspace in the future. Its not something specific to a theme as far as I know, where I simply can put my customizations in [dspace-source]/themes/... as an overlay and use them again in the future. I want to keep my dspace repository as standard as possible to avoid any hassles on the next update. So what is the best way to do that without needing do merge all my changes manually to the new source code? Best regards, Christoph -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To post to this group, send email to dspace-tech@googlegroups.com<mailto: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. -- 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] Hiding communities/collections from unauthenticated users.
I'm trying to hide some internal communities and collections from unauthenticated users (with DSpace 5.5/XMLUI, but also with upcoming 6.0). How-to in the Wiki has been outdated (https://wiki.duraspace.org/display/DSPACE/Hide+Community+or+Collection+from+list) and some other googling turned out advise to filter specific communities/collections in xsl, which I think is prone to breakage in migrations and such (e.g. http://stackoverflow.com/questions/37122851/hiding-collections-and-sub-collections-in-dspace). What I'd like to do is to filter the community/collection list when it is generated. This seems such common requirement, that it might have been implemented already by someone? br, Ilja Sidoroff University of Eastern Finland -- 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] Moving a collection to a different community
Is there a "canonical" way of moving collections to different community? There is some old advice on this, which involves direct modifications to the database, and a recent one here: https://gist.github.com/alanorth/392c4660e8b022d99dfa Is this still the way to do this? br, Ilja Sidoroff University of Eastern Finland -- 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] REST Interface Sample App on Rails
The /rest/login api changed a bit in version 6, but now the docs are updated: https://wiki.duraspace.org/display/DSDOC6x/REST+API br, Ilja Sidoroff University of Eastern Finland From: dspace-tech@googlegroups.com on behalf of Bruno Nocera Zanette Sent: Tuesday, September 6, 2016 8:12:45 PM To: DSpace Technical Support Subject: [dspace-tech] REST Interface Sample App on Rails Hey all!! I've been writting, on my spare time, a REST interface sample app on Ruby on Rails and it finally got to a point where i can show it to you. It is fully based on "dspace-rest-client" ruby gem: The link to the app is: https://drcgem-sample-interface.herokuapp.com/ The code can be found here: https://gitlab.c3sl.ufpr.br/bnzanette/DspaceRestSample (P.s.: I plan to move it to github, but for now this is the only source. It's completely safe and hosted by a research group on the University where i study.). I decided to keep it as simple as possible so that other people can use it as basis for other apps. Like a "live documentation". There are somethings that i still have to do to make it more usable, like adding links to add collections/items/bitstreams on a community/collection/item page, so that you don't need to always choose a parent object when creating a new object. I also need to add a footer and an "about page" to add "powered by..." infos and stuff like that. However, for some reason, Dspace's REST login isn't working on demo.dspace.org<http://demo.dspace.org>, so the app crashes everytime the buttons to save/edit are clicked. On my tests on a 5.x version everything works fine. Feel free to do whatever you want with it!! Hope you like it and find some utility for it. Cheers!! -- Bruno Nocera Zanette +55 41 9992-2508 -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To post to this group, send email to dspace-tech@googlegroups.com<mailto: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. -- 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] Querying items by metadata item via SOLR and REST
Ari and Terry,
thanks for help! At least with brief testing, it seems the new api does what I
need. One question - if I leave the parameters 'limit' and 'offset' from the
query, will I get all the items, or is there some upper limit for results
returned in one query?
Ilja
From: Ari
Sent: Monday, September 5, 2016 8:34:50 AM
To: DSpace Technical Support
Cc: terry.br...@georgetown.edu; Ilja Sidoroff
Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST
Hi Ilja,
we aiming fullly REST-based solution (dumping both workflow and XMLUI admin UI)
so we do lot of REST tests.
This should work for filtered-items (items who's author name contains "Matti"):
curl -H "Accept: application/json"
"http:your.dspace.com:8080/rest/filtered-items?&query_field[]=dc.contributor.author&query_op[]=contains&query_val[]=Matti&collSel[]=&limit=100&offset=0&expand=parentCollection,metadata&filters=none"
-g | python -m json.tool
If you need to be logged in, then:
1. First, authenticate your self:
curl --data "email=your.email&password=your_pass"
http://your_dspace.com:8080/rest/login<http://your_dspace.com:8080/rest/login>
-c cookies.txt
2. Test that authentication was successful:
curl -H "Accept: application/json"
http://your_dspace.com:8080/rest/status<http://your_dspace.com:8080/rest/status>
-b cookies.txt
- this should return something like this:
{"okay":true,"authenticated":true,"email":"your.email","fullname":"ari
","sourceVersion":null,"apiVersion":null}
Hope this helps,
Ari
On Saturday, 3 September 2016 10:38:07 UTC+3, Ilja Sidoroff wrote:
Terry,
I looked very briefly into this on Friday, but I didn't quite get how to create
and execute queries without using the interactive webpages. The endpoint GET
/rest/filtered-items seemed promising, but at the limited time I looked at it,
I didn't see how to use it, but I'll try to look bit more into that.
Ilja
From: dspac...@googlegroups.com
> on behalf of Terry Brady
>
Sent: Friday, September 2, 2016 8:55:13 PM
To: Ilja Sidoroff
Cc: DSpace Technical Support
Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST
Ilja,
In DSpace 6, the REST API will provide additional query capabilities.
https://wiki.duraspace.org/display/DSDOC6x/REST+Based+Quality+Control+Reports
While this may not solve your immediate issues, it might provide a good future
solution.
Terry
On Thu, Sep 1, 2016 at 3:43 AM, Ilja Sidoroff
<mailto:ilja.sidor...@uef.fi>> wrote:
Hello,
I am using DSpace 5.5.
Am I correct, that SOLR queries return only items that are in
*collections* and not in the *workflow*? At least my search attemps
indicate that?
In the REST API, however, it seems that GET /items returns only
results that are in the collections. However, with POST
/items/find-by-metadata-field I can get all items in the DSpace, both
those in the collections and those in the workflow?
What I need, is a list of *all items* (both in the workflow and the
collections) that have certain metadata field set and *the value of
that field*. I don't see other way of doing that, except by direct SQL
query to the database. I have one for 5.x, but I'm not happy with it
since, I need to update it for 6.x etc. Is there any other way of
doing this?
Also, it seems that
dspace import -d -m mapfile ...
does not delete items currently in the workflow? Is this intentional or a bug?
regards,
Ilja Sidoroff
University of Eastern Finland
--
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<mailto:dspace-tech%2bunsubscr...@googlegroups.com>.
To post to this group, send email to
dspac...@googlegroups.com<mailto: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
http://georgetown-university-libraries.github.io/<https://www.library.georgetown.edu/lit/code>
425-298-5498 (Seattle, WA)
--
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<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to
dspac...@googlegroups.com<mailto:dspac...@googlegroups.com>.
Visit this group at https://groups.google.com/grou
Re: [dspace-tech] Querying items by metadata item via SOLR and REST
Terry, I looked very briefly into this on Friday, but I didn't quite get how to create and execute queries without using the interactive webpages. The endpoint GET /rest/filtered-items seemed promising, but at the limited time I looked at it, I didn't see how to use it, but I'll try to look bit more into that. Ilja From: dspace-tech@googlegroups.com on behalf of Terry Brady Sent: Friday, September 2, 2016 8:55:13 PM To: Ilja Sidoroff Cc: DSpace Technical Support Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST Ilja, In DSpace 6, the REST API will provide additional query capabilities. https://wiki.duraspace.org/display/DSDOC6x/REST+Based+Quality+Control+Reports While this may not solve your immediate issues, it might provide a good future solution. Terry On Thu, Sep 1, 2016 at 3:43 AM, Ilja Sidoroff mailto:ilja.sidor...@uef.fi>> wrote: Hello, I am using DSpace 5.5. Am I correct, that SOLR queries return only items that are in *collections* and not in the *workflow*? At least my search attemps indicate that? In the REST API, however, it seems that GET /items returns only results that are in the collections. However, with POST /items/find-by-metadata-field I can get all items in the DSpace, both those in the collections and those in the workflow? What I need, is a list of *all items* (both in the workflow and the collections) that have certain metadata field set and *the value of that field*. I don't see other way of doing that, except by direct SQL query to the database. I have one for 5.x, but I'm not happy with it since, I need to update it for 6.x etc. Is there any other way of doing this? Also, it seems that dspace import -d -m mapfile ... does not delete items currently in the workflow? Is this intentional or a bug? regards, Ilja Sidoroff University of Eastern Finland -- 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<mailto:dspace-tech%2bunsubscr...@googlegroups.com>. To post to this group, send email to dspace-tech@googlegroups.com<mailto: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. -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology http://georgetown-university-libraries.github.io/<https://www.library.georgetown.edu/lit/code> 425-298-5498 (Seattle, WA) -- 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<mailto:dspace-tech+unsubscr...@googlegroups.com>. To post to this group, send email to dspace-tech@googlegroups.com<mailto: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. -- 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] Querying items by metadata item via SOLR and REST
On Fri, Sep 02, 2016 at 09:52:54AM -0400, Monika Mevenkamp wrote: > Ilja > > Yep - that little CS guy sometimes gets in the way > > I myselfI do more and more in ruby - much faster turn around, since it is an > interpreted language and without the strict typing and all that Java > verbosity many fewer lines of codes - i actually wrote the little lister > script you need in between other things yesterday. I even use jruby when I > need to develop Java code and want to figure out what all those mysterious > semi documented DSPace Java methods really are doing > > I am eager (as you probably can tell) to promote my dspace / ruby gem > So if you are interested in trying this out - I am very interested in helping > / supporting this Monika, I'm not sure if I will use your scripts directly, since I've done other parts of my production pipeline already in golang; using (j)ruby in just one might confuse others. However, I'm starting to see the advantange of using a jvm-based scripting language; I've already have an acquintance of mine using jython with DSpace. I myself prefer ruby over python (or maybe I'm just bored with python), so I will definitely keep your gem and script in mind. Ilja -- 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] Querying items by metadata item via SOLR and REST
Yeah, the speed is not that crucial, if it stays somewhere in the order of
minutes or even some hours. What I'm doing in is transferring items from CRIS,
which doesn't know which items DSpace already has, and I'll have to prune those
records already in the DSpace. This happens once a day (night) by cron, so I
can live with that speed. It's just probably the little computer scientist in
me that had hoped for the most efficient solution.
Thanks for the numbers and testing!
Ilja
From: Monika Mevenkamp
Sent: Thursday, September 1, 2016 7:05:12 PM
To: Ilja Sidoroff
Cc: DSpace Tech
Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST
does speed matter ? Is this something you’ll have to do a lot - or is it one
of those one-of-scripts ?
If you run this on the command line / cron it may not be so important -
especially with a cron job you may not care that much - as log as you can
start it at midnight and it gets done by 7am
Calling the JRuby script from the UI, aka calling from Java is possible - but I
have not actually done that yet
I don’t believe that calling Java via JRuby adds much to the performance
A bigger issue, I see, is that DSpace.findByMetadataValue returns an array of
matching DSpaceObjects - if speed matters this needs to be changed to return an
iterator, which shouldn’t be too hard
Why not just try and see - since the script only accesses data and does not
change anything - there is no danger to disturb your instance. Plus you can run
this anywhere - as long as you have access to the database.
Monika
—
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven
> On Sep 1, 2016, at 11:48 AM, Ilja Sidoroff wrote:
>
> Thanks! That script would indeed do what I'd need, but I'm bit concerned
> about the scalability, since it will have to do one request per item - and if
> I have thousands of items, that might get a bit heavy? Or would it? I really
> don't know don't know how long for instance 10.000 item/id/metadata requests
> would take.
>
> Ilja
>
>
> From: Monika Mevenkamp
> Sent: Thursday, September 1, 2016 6:30:33 PM
> To: Ilja Sidoroff
> Cc: DSpace Tech
> Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST
>
> Hi Ilja
>
> I have a script that given a metadata field, e.g. pu.workflow.state, produces
> a tab separated list so:
>
> field id handle value
> pu.workflow.state 969 9/fk4w099v32approved
> pu.workflow.state 903 nullemailed
> pu.workflow.state 753 nullemailed
> pu.workflow.state 752 nullemailed
> pu.workflow.state 902 nullorphaned
>
>
> The script is written in jruby and based on my dspace-jruby gem, see Script
> here<https://github.com/akinom/dspace-cli/blob/master/metadata/list_values.rb>.
> The gem as well as the script are available from github: jrdspace
> gem<https://github.com/akinom/dspace-jruby>. and
> cli-dspace<https://github.com/akinom/dspace-cli> , which has a bunch of other
> scripts.
>
> The script is quite small, its ‘action’ is in the doit method
>
> def doit(metadata_field)
> puts ['field', 'id', 'handle', 'value'].join("\t")
> dsos = DSpace.findByMetadataValue(metadata_field, nil, DConstants::ITEM)
> dsos.each do |dso|
>vals = dso.getMetadataByMetadataString(metadata_field).collect { |v|
> v.value }
>puts [metadata_field, dso.getID, dso.getHandle.nil? ? "null" :
> dso.getHandle, vals ].join("\t")
> end
> end
>
> if you want to try this out , there are instructions on GitHUb. If you want
> to work in Java, look at the implementation of the DSpace.findByMetadataValue
> method. It has the SQL statement. see
> HERE<https://github.com/akinom/dspace-jruby/blob/master/lib/dspace/dspace.rb#L150-L171>
>
> Monika
>
> —
> Monika Mevenkamp
> Digital Repository Infrastructure Developer
> Princeton University
> Phone: 609-258-4161
> Skype: mo-meven
>
>
>
> On Sep 1, 2016, at 6:43 AM, Ilja Sidoroff
> mailto:ilja.sidor...@uef.fi>> wrote:
>
> Hello,
>
> I am using DSpace 5.5.
>
> Am I correct, that SOLR queries return only items that are in
> *collections* and not in the *workflow*? At least my search attemps
> indicate that?
>
> In the REST API, however, it seems that GET /items returns only
> results that are in the collections. However, with POST
> /items/find-by-metadata-field I can get all items in the DSpace, both
> those in the collections and those in the workflo
Re: [dspace-tech] Querying items by metadata item via SOLR and REST
Thanks! That script would indeed do what I'd need, but I'm bit concerned about
the scalability, since it will have to do one request per item - and if I have
thousands of items, that might get a bit heavy? Or would it? I really don't
know don't know how long for instance 10.000 item/id/metadata requests would
take.
Ilja
From: Monika Mevenkamp
Sent: Thursday, September 1, 2016 6:30:33 PM
To: Ilja Sidoroff
Cc: DSpace Tech
Subject: Re: [dspace-tech] Querying items by metadata item via SOLR and REST
Hi Ilja
I have a script that given a metadata field, e.g. pu.workflow.state, produces a
tab separated list so:
field id handle value
pu.workflow.state 969 9/fk4w099v32approved
pu.workflow.state 903 nullemailed
pu.workflow.state 753 nullemailed
pu.workflow.state 752 nullemailed
pu.workflow.state 902 nullorphaned
The script is written in jruby and based on my dspace-jruby gem, see Script
here<https://github.com/akinom/dspace-cli/blob/master/metadata/list_values.rb>.
The gem as well as the script are available from github: jrdspace
gem<https://github.com/akinom/dspace-jruby>. and
cli-dspace<https://github.com/akinom/dspace-cli> , which has a bunch of other
scripts.
The script is quite small, its ‘action’ is in the doit method
def doit(metadata_field)
puts ['field', 'id', 'handle', 'value'].join("\t")
dsos = DSpace.findByMetadataValue(metadata_field, nil, DConstants::ITEM)
dsos.each do |dso|
vals = dso.getMetadataByMetadataString(metadata_field).collect { |v|
v.value }
puts [metadata_field, dso.getID, dso.getHandle.nil? ? "null" :
dso.getHandle, vals ].join("\t")
end
end
if you want to try this out , there are instructions on GitHUb. If you want to
work in Java, look at the implementation of the DSpace.findByMetadataValue
method. It has the SQL statement. see
HERE<https://github.com/akinom/dspace-jruby/blob/master/lib/dspace/dspace.rb#L150-L171>
Monika
—
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven
On Sep 1, 2016, at 6:43 AM, Ilja Sidoroff
mailto:ilja.sidor...@uef.fi>> wrote:
Hello,
I am using DSpace 5.5.
Am I correct, that SOLR queries return only items that are in
*collections* and not in the *workflow*? At least my search attemps
indicate that?
In the REST API, however, it seems that GET /items returns only
results that are in the collections. However, with POST
/items/find-by-metadata-field I can get all items in the DSpace, both
those in the collections and those in the workflow?
What I need, is a list of *all items* (both in the workflow and the
collections) that have certain metadata field set and *the value of
that field*. I don't see other way of doing that, except by direct SQL
query to the database. I have one for 5.x, but I'm not happy with it
since, I need to update it for 6.x etc. Is there any other way of
doing this?
Also, it seems that
dspace import -d -m mapfile ...
does not delete items currently in the workflow? Is this intentional or a bug?
regards,
Ilja Sidoroff
University of Eastern Finland
--
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<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to
dspace-tech@googlegroups.com<mailto: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.
--
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] Querying items by metadata item via SOLR and REST
Hello, I am using DSpace 5.5. Am I correct, that SOLR queries return only items that are in *collections* and not in the *workflow*? At least my search attemps indicate that? In the REST API, however, it seems that GET /items returns only results that are in the collections. However, with POST /items/find-by-metadata-field I can get all items in the DSpace, both those in the collections and those in the workflow? What I need, is a list of *all items* (both in the workflow and the collections) that have certain metadata field set and *the value of that field*. I don't see other way of doing that, except by direct SQL query to the database. I have one for 5.x, but I'm not happy with it since, I need to update it for 6.x etc. Is there any other way of doing this? Also, it seems that dspace import -d -m mapfile ... does not delete items currently in the workflow? Is this intentional or a bug? regards, Ilja Sidoroff University of Eastern Finland -- 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] LICENSE-bundle in BTE imported items
Is it so, that LICENSE-bundle is not created for items imported via BTE-import (CSV)? Also, is there any way of adding files to other than the default bitstream in the UPLOAD step in the submission phase? The only way of adding license files to BTE-imported items seems to be after they are ingested, via "Edit Item"? Also, I'm not seeing that the configuration option "webui.licence_bundle.show" has any effect in XMLUI. Has anyone any insight how that option should actually to work? I'm using DSpace 5.4 with XMLUI (Mirage). Ilja Sidoroff Information Specialist University of Eastern Finland, Library -- 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: LICENSE-bundle in BTE imported items
Regarding the latter question, it seems that the configuration property is used only in dspace-xmlui/src/main/java/org/dspace/app/xmlui/objectmanager/ItemAdapter. java (in XMLUI, there are couple of references in JSPUI). According to the comments in that file, This is an adapter which translates a DSpace item into a METS document * following the DSpace METS profile, err well mostly. Does this mean that in XMLUI, the property gets used only in METS export, or is the METS format used also in other places? Ilja torstai 17. maaliskuuta 2016 12.43.20 UTC+2 Ilja Sidoroff kirjoitti: > > Is it so, that LICENSE-bundle is not created for items imported via > BTE-import (CSV)? Also, is there any way of adding files to other than the > default bitstream in the UPLOAD step in the submission phase? The only way > of adding license files to BTE-imported items seems to be after they are > ingested, via "Edit Item"? > > Also, I'm not seeing that the configuration option > "webui.licence_bundle.show" has any effect in XMLUI. Has anyone any insight > how that option should actually to work? I'm using DSpace 5.4 with XMLUI > (Mirage). > > Ilja Sidoroff > Information Specialist > University of Eastern Finland, Library > -- 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] jQuery 1.6.2
Oops, I accidentally deleted my reply when trying to remove a spurious empty message. Anyway, I made a pull request for non Mirage2 themes in XMLUI (see issue) [1]. Ilja [1] https://jira.duraspace.org/browse/DS-3099 lauantai 12. maaliskuuta 2016 0.43.25 UTC+2 Hardy Pottinger kirjoitti: > > Hi, Ilja, alas we manage our JS dependencies a bit differently than our > Java dependencies. [1] In the case of Mirage2, Bower is used to fetch > jQuery, and the version is specified with a tilde, which according to NPM > translates to "close enough to."[2][3] > > I have made a Jira ticket for upgrading our jQuery version with the UIs we > have right now [4]. As Tim said previously, we welcome a pull request to > address this. > > --Hardy > > [1] https://github.com/DSpace/DSpace/search?q=jquery > [2] > http://stackoverflow.com/questions/19541494/bower-dependency-tilde-in-node > [3] https://github.com/npm/node-semver > [4] https://jira.duraspace.org/browse/DS-3099 > > -- > *From:* dspac...@googlegroups.com [dspac...@googlegroups.com > ] on behalf of Tim Donohue [tdon...@duraspace.org > ] > *Sent:* Thursday, March 10, 2016 1:59 PM > *To:* dspac...@googlegroups.com > *Subject:* Re: [dspace-tech] jQuery 1.6.2 > > Hi Ilja, > > Yes, we'd encourage a Pull Request if you are willing. Thanks for making > us aware of this. > > - Tim > > On 3/8/2016 6:55 AM, Ilja Sidoroff wrote: > > At routine system scan by our IT department noticed, that mirage theme > uses jQuery version 1.6.2, which is vulnerable to a XSS attack [1]. I don't > know if this actually exploitable in DSpace, but anyway it seems that this > is fixable by simple bumping the version to 1.6.4. Is it worth of making a > pull request to fix this? > > Ilja Sidoroff > Information Specialist > University of Eastern Finland, Library > > [1] CVE-2011-4969 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4969 > -- > 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...@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] jQuery 1.6.2
Thanks for the pointers - the issue I found was in Mirage 1, where the jQuery version was hardcoded in the source code. I'll try to look into making a pull request later today or tomorrow. Ilja lauantai 12. maaliskuuta 2016 0.43.25 UTC+2 Hardy Pottinger kirjoitti: > > Hi, Ilja, alas we manage our JS dependencies a bit differently than our > Java dependencies. [1] In the case of Mirage2, Bower is used to fetch > jQuery, and the version is specified with a tilde, which according to NPM > translates to "close enough to."[2][3] > > I have made a Jira ticket for upgrading our jQuery version with the UIs we > have right now [4]. As Tim said previously, we welcome a pull request to > address this. > > --Hardy > > [1] https://github.com/DSpace/DSpace/search?q=jquery > [2] > http://stackoverflow.com/questions/19541494/bower-dependency-tilde-in-node > [3] https://github.com/npm/node-semver > [4] https://jira.duraspace.org/browse/DS-3099 > > -- > *From:* dspac...@googlegroups.com [dspac...@googlegroups.com > ] on behalf of Tim Donohue [tdon...@duraspace.org > ] > *Sent:* Thursday, March 10, 2016 1:59 PM > *To:* dspac...@googlegroups.com > *Subject:* Re: [dspace-tech] jQuery 1.6.2 > > Hi Ilja, > > Yes, we'd encourage a Pull Request if you are willing. Thanks for making > us aware of this. > > - Tim > > On 3/8/2016 6:55 AM, Ilja Sidoroff wrote: > > At routine system scan by our IT department noticed, that mirage theme > uses jQuery version 1.6.2, which is vulnerable to a XSS attack [1]. I don't > know if this actually exploitable in DSpace, but anyway it seems that this > is fixable by simple bumping the version to 1.6.4. Is it worth of making a > pull request to fix this? > > Ilja Sidoroff > Information Specialist > University of Eastern Finland, Library > > [1] CVE-2011-4969 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4969 > -- > 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...@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] Re: jQuery 1.6.2
tiistai 8. maaliskuuta 2016 14.55.23 UTC+2 Ilja Sidoroff kirjoitti: > > At routine system scan by our IT department noticed, that mirage theme > uses jQuery version 1.6.2, which is vulnerable to a XSS attack [1]. I don't > know if this actually exploitable in DSpace, but anyway it seems that this > is fixable by simple bumping the version to 1.6.4. Is it worth of making a > pull request to fix this? > > Ilja Sidoroff > Information Specialist > University of Eastern Finland, Library > > [1] CVE-2011-4969 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4969 > -- 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] jQuery 1.6.2
At routine system scan by our IT department noticed, that mirage theme uses jQuery version 1.6.2, which is vulnerable to a XSS attack [1]. I don't know if this actually exploitable in DSpace, but anyway it seems that this is fixable by simple bumping the version to 1.6.4. Is it worth of making a pull request to fix this? Ilja Sidoroff Information Specialist University of Eastern Finland, Library [1] CVE-2011-4969 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4969 -- 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: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload
torstai 25. helmikuuta 2016 13.46.28 UTC+2 Claudia Jürgen kirjoitti: > > Hello Ilja, > > I think this is correct behaviour especially with regards to the legal > aspects. > The submitter grants the license agreement for the file(s) in the item > he submitted. > So no one should be able to change these. > > Claudia Jürgen > Yes, I can see that it would be the normal case. I'm however building a system that will get automatic submissions for metadata, but the actual content (files) is added only at the review-phase, so I needed the ability to upload files later. I see that the default use-case/workflow would indeed call for unmodified files. And it turns out that I was mistaken about the Sherpa/Romeo misplacement - it is indeed working as it should be. Ilja -- 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: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload
Ok, digging into the source code I found (thanks to jkesanie):
dspace-xmlui...UploadStep.java: boolean disableFileEditing = (submissionInfo
.isInWorkflow()) && !ConfigurationManager.getBooleanProperty("workflow",
"reviewer.file-edit");
So it seems to be configurable, intended behaviour, although undocumented?
Seems still, that there are two minor bugs
* Sherpa/Romeo information getting into different views on submit & review
steps
* gettings stuck in the upload step with no files & upload.required set to
true
--
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: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload
It seems that Sherpa/Romeo isn't the thing to blame (expect for perhaps showing up in the wrong page). There doesn't seem to be a possibility to upload new files when reviewing and editing items in the workflow phase. It seems that the code for initial submission and reviewing are almost, but not quite the same. Has anyone got any pointers, where I this happens in the source code, so I could take a look? I will probably be filing a bug on this, after I pinpoint the cause, as I don't think this is the intended behaviour. -- 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: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload
I changed dspace.cfg not to require uploads webui.submit.upload.required = false And I didn't get stuck on the "Upload" page anymore. However, Sherpa/Romeo information still gets printed in the wrong page. Also, upload page doesn't display any possibilities to actually upload any files, so it still seems to be broken. -- 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] Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload
Hello, I have encountered a possible bug in DSpace in workflow's edit metadata phase, where editing metadata gets stuck in "upload" phase. Here's how I get the error: 1) I have created a collection, and assigned groups to Administrators, Submitters and Accept/Reject/Edit metadata step. 2) I upload new metadata from csv file, with --workflow -option and Submissions pool shows the imported items correctly 3) When I take an item from the pool and select "Edit metadata", first two "Describe" pages work as intended, but "Access Settings" page does not show Sherpa/Romeo information - I have configured embargo and Sherpa/Romeo integration, but haven't otherwise modified the submission process. 4) When proceeding to the "Upload" page, I get the Sherpa/Romeo information and list of Files Uploaded, which is empty. Now Previous/Save&Exit/Next buttons, nor the Item submission page buttons don't work anymore. When clicking them I get back to the "Upload" page, but the browser URL changes, for example: http: //localhost:8080/handle/123456789/2/submit/7c6e545d25467463746a2e197e0d073357374e8c.continue http: //localhost:8080/handle/123456789/2/submit/1f243c8b11525c2e11387d6e280e1d737a5e0d55.continue I.e. some sort of cookie stored in the URL changes. dspace.cfg option for file upload is the default, I'll try with false here soon, but it seems that there might be also some other problems, at least the Sherpa/Romeo information showing up in the wrong place might suggest so. webui.submit.upload.required = true Does anyone have similar experiences? Should I file a bug report or might this be some misconfiguration related to BTE import, Sherpa/Romeo-integration or something else? br, Ilja Sidoroff Information Specialist University of Eastern Finland, Library -- 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.
