Saul,
This generally takes some minor detective work within the main dspace.log
files. If you know the item ID, that makes it easier.
In Linux, I would do something along the lines of:
grep "delete_item:item_id=12345" dspace.log.2020.06.26
Only substitute the item ID and only search the
Is DS-4066 not related?
https://jira.lyrasis.org/browse/DS-4066
This patch will be introduced with the 6.4 rollout despite much earlier target
dates.
https://wiki.lyrasis.org/display/DSPACE/DSpace+6.4+Release+Status
There will be a new command for migrating pre-6.x statistics:
Jose,
The most common problem I've seen with this is related the pgcrypto extension
being installed with a superuser account and database that aren't the same as
what's being used by the DSpace installation. The documentation isn't explicit
about this as I recall.
For instance, if your
any issues with email between DSpace 1.x - 5.x. Only 6.
-Jeff
From: Tim Donohue
Sent: Monday, February 3, 2020 1:38 PM
To: Jeffrey Sheldon; dspace-tech@googlegroups.com
Subject: Re: Workflow email notices rejected
Hi Jeffrey,
You might want to look more
All,
I recently upgraded to DSpace 6 and have noticed different behavior with
respect to email configuration as seen in DSpace 5.
I'm using a trusted and open SMTP relay which doesn't require authentication.
Therefore, I have mail.server populated and mail.server.username and
Michael,
Glad to hear that things have improved!
xmlui.force.ssl should only apply to content through the web frontend if you
have an SSL cert configured for your webserver software. Setting that
attribute to "true" makes it automatically kick in following the independent
process of making
Michael,
Although I'm sure you've verified all the config aspects, does your LDAP server
use SSL?
authentication-ldap.provider_url = ldaps://intranet.mpba.mp.br:636/
I don't believe there are any case-specific issues with respect to
search_context, but every example I've seen (and used) had
Evelthon,
Are you using ModProxy with Apache HTTPD? It sounds like the IP information
isn't being handed over properly. If this is the case, as it once was for me,
search dspace.cfg for "useProxies". You can read more on this here:
https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics
at debugging this, but any thoughts which can help me
narrow the scope are appreciated.
-Jeff
From: dspace-tech@googlegroups.com <dspace-tech@googlegroups.com> on behalf of
Jeffrey Sheldon <jshel...@ksu.edu>
Sent: Wednesday, May 24,
Folks,
Our usage statistics abruptly stopped working yesterday despite no major
changes having taken place in our DSpace 5.3/XMLUI installation. If I choose
to view statistics, nothing is displayed. Rather, I receive the following
errors in catalina.out after clicking on the associated
dspace-tech,
I periodically revisit my postgres.conf file and find myself re-researching
ideal parameters for configuration.
This document has always been useful towards that end:
https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
However, I don't recall seeing a breakdown of
Don,
I would recommend enabling both LDAP and Password authentication, at least long
enough to log in under the older administrator account and promote any accounts
created through LDAP logins (or create a temporary one to feel things out).
You can configure for both like so in
As a follow-up to Tim's comments, note that there's no easy way to delete or
hide thumbnails on a large scale once created. Use this feature judiciously as
once you have them, they become part of your site identity.
-Jeff
On Jun 7, 2016, at 09:04, Tim Donohue
Back in December, I emailed here about a missing chunk of statistics. helix84
gave a hopeful response:
https://groups.google.com/d/msg/dspace-tech/-FRxo2TXoJw/Pg7Rh2FVCAAJ
However, I'm confused about what stats-log-converter and stats-log-importer are
actually doing.
I was able to use
This might answer my question:
https://wiki.apache.org/solr/SchemaXml#Default_query_parser_operator
Is this the "correct" way to specify this change?
-Jeff
From: dspace-tech@googlegroups.com <dspace-tech@googlegroups.com> on be
Folks,
I noticed that the search.operator attribute in dspace.cfg became depreciated
with Discovery. However, I don't see a provision to define default search
boolean logic. Perhaps I'm missing something obvious?
Example searches (showing that SOLR honors capital boolean arguments included
Folks,
Some of our faculty are experimenting with metadata searches where the data
contains a backslash. In both Lucene and SOLR, backslashes are a reserved
character which need to be escaped (ie. search\\term) or, with the entire
search term, wrapped in quotes (ie. "search\term").
This is
.com <ivan.ma...@gmail.com> on behalf of helix84
<heli...@centrum.sk>
Sent: Tuesday, December 22, 2015 8:13 PM
To: Jeffrey Sheldon
Cc: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] Direct SOLR query returns "0" for Item page views
Hi, just a few superficial observati
ituations like
yours where the 5.x migration doesn't go as smoothly as expected. But,
we hope automating these database migrations will help us to *avoid*
these database-level oddities in the future (the manual process was just
too prone to human accidents or errors).
Good luck,
Tim
On 11/18/2015 3:32 PM,
19 matches
Mail list logo
