Is there some kind of database transaction leaking issue with DSpace,
particularly the XMLUI? Basically, I find that it doesn't matter what I my
pool size is. Eventually it always gets full. Sometimes it takes a few
days, sometimes it happens a few times in one day. Today I saw this in
Hello Yanan,
According to the bug report for that ImageMagick security issue, it looks
like this issue has been fixed
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3714
On the page above, I see a notice that says it only affected "ImageMagick
before 6.9.3-10 and 7.x before 7.0.1-1"
If you have the DSpace 6 REST API enabled, you can run a report to retrieve
this information.
Here is an example on demo.dspace.org pulling items from 2016, 2017, and
2018.
Based on the folks who expressed interest in the Developer Show and Tell
Meeting, I have created a Doodle Poll to find the best date and time for
our initial meeting.
If you are interested in attending, please indicate the times that would
work for you. The agenda and Doodle Poll link are
Hello Lewatle,
you may query the database, this is our query for accessioned (5.4) but should
work:
SELECT to_char(date_trunc('year', t1.ts), '') AS year, count(*) FROM
(SELECT to_timestamp(text_value, '-MM-DD') AS ts FROM metadatavalue WHERE
metadata_field_id = 12) t1 GROUP BY
Dear All,
I am using DSpace 6.2 on both xmlui and jspui interface, I would like to
know how can I see total number of items submitted in the year 2016 and
2017.
When I check *dc. date. accessioned metadata *field might assist, I am
using out of box DSpace interface which doesn't have *dc.
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
