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
nue 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 thi
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,
Ilj
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 <dspace-tech@googlegroups.com> on
requests would
take.
Ilja
From: Monika Mevenkamp <mome...@gmail.com>
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
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
U
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 licen
raspace.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
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 S
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 any
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&q
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
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
13 matches
Mail list logo
