Dear DSpace people,
Recently I noticed that our PDFs were not getting thumbnails generated for
them. I ran the filter-media script manually and saw an error like this:
org.im4java.core.InfoException: org.im4java.core.CommandException:
org.im4java.core.CommandException: identify: not authorized
Kia ora koutou,
Dspace 5.6
Postgres 8.4.20
Redhat Enterprise Server 6.9
I am setting up DOI minting using datacite. I am getting the following
error, but not consistently. Is there a way to see the transaction between
dspace and datacite to further debug?
We are thinking of migrating to
I am occasionally seeing errors like this in the catalina.out file:
Error using query type: 2
[WARN] deprecation - The 'component-configurations' section in the sitemap
is deprecated. Please check for alternatives.
Error using query *:*
Error using query statistics_type:workflow AND
Hi Peter,
The "description.xml" file is populated automatically from your
configurations (in dspace.cfg and/or oai.cfg). Here's the original
"description.xml" in our codebase -- notice the "${variable}" placeholders,
which are filled out (during the "ant update" step) based on your
Hi Paul,
I meant description.xml in dspace/config/crosswalks/oai.
If I change oai prefix in oai.cfg, do I need to change it in
description.xml too? This description.xml file is referenced in oai.xml's
"oai.description.file".
Peter
W dniu środa, 10 października 2018 15:48:50 UTC+1 użytkownik
In DSpace, full-text indexing does not occur automatically. Instead, you
must run (or schedule) the "[dspace]/bin/dspace filter-media" script. This
script will look for files that DSpace is able to fulltext index (e.g.
PDFs, HTML, Microsoft office), extract the text and indexes it.
Here's the
Dear sir,
I have installed dspace and created community, collection
into that community. And imported some PDFs in collection. But full text
search is not working.
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct:
On our DSpace 6.3 instance we're seeing an authorization error on the
license.txt bitstreams when we run `oai import`. The license bundles and
bitstreams don't have any authorization policies attached to them. I know
I've seen a few Jira issues related to this issue with code that has been
Hi Peter,
I don't know which 'description.xml' you point to, but in
'[dspace]/config/modules/oai.cfg' you could customise the
'oai.identifier.prefix'.
Kind regards,
Paul Münch
Am 10.10.2018 um 00:19 schrieb admin:
> Hi,
>
> Can repositoryIdentifier located in description.xml be something else
On Wednesday, October 10, 2018 at 1:44:22 AM UTC-4, an...@kila.ac.in wrote:
>
> 2018-10-10 00:00:01,876 WARN
> org.apache.commons.configuration.DefaultConfigurationBuilder @ Internal
> errororg.apache.commons.configuration.ConfigurationException: Cannot locate
> configuration source local.cfg
10 matches
Mail list logo
