> does that mean I can use the property setting like below?
>
> oai.harvester.acceptedHandleServer = hdl.handle.net,
> repository.university.edu
>
> Thanks again,
> euler
>
> On Thursday, January 19, 2017 at 3:33:54 PM UTC+8, Kim Shepherd wrote:
>>
>> Hi euler,
>
Hi Peter,
When you were first installing DSpace, did you manually copy the webapps
you wanted to deploy over to that apache-tomcat-8.5.4 path? If so, you'll
have to perform that copy from $dspace/webapps again.
Also, it might pay to clear the XMLUI cache, usually found in
Hi euler,
Is it possible that, at least for the sidebar issue, you could use
HierarchicalSidebarFacetConfiguration to end up with terms split on the
semicolon, and also displayed in a hierarchy so people have to click eg.
"technical report" first, then the series number they're interested in?
Hi Nico, it's hard to diagnose this problem exactly... although the problem
seems to be that you're getting back a null Hibernate session for the
context, I'd say your postgres database connections should be OK since your
ant fresh_install finished successfully, which includes lots of db writes
Hi Ron, can you sure some more details from logs and a screenshot of the
error you encountered when adding a collection?
If Solr indexing is the issue, there is some good documentation to help you
make sure Solr Discovery is set up
at https://wiki.duraspace.org/display/DSDOC6x/Discovery
Hi euler,
I haven't done harvesting in DIM format, I'd probably need to see your
ingest crosswalk to know exactly what to expect from that method, but
you're onto something with your second question - if your source repository
is serving up identifier URIs prefixed with
Hi Donald,
I'd recommend reading in the URL via ConfigurationManager (or in 6.x and
newer, the DSpaceConfigurationService) and reading the label in from the
i18n Messages file so it can be translated if needed.
In 5.x and previous, you could import org.dspace.core.ConfigurationManager
in
Hi Andy,
It looks like the request to get current items from the OAI solr core /
index is failing, perhaps because Solr isn't available at that address, the
index doesn't exist yet, or the core hasn't deployed properly.
Are you able to check that your "solr" webapp is deployed and working by
Hi Keith,
Is this an item that has been archived already? Typically, the ability to
edit items once they're archived is managed by a set of permissions
inherited from the owning communities/collections rather than who submitted
it. Even if the previous submitter did happen to have edit
Hi Freddy,
Take a look at the "webui.itemdisplay.default" configuration property in
your dspace.cfg file. You can use this property to list the fields, in
order, that you'd like displayed in the item summary view in JSPUI.
There's also a helpful wiki page
at
Hi Shaun,
Hm, these scripts were definitely written with just 'statistics' in mind
(hence the names of the commands)... I like the idea of trying them out to
do exports/imports of other solr indexes but I'm not surprised that a few
things aren't working properly there will be some
Another option is that the database and db user might not be created on
this host yet?
Maybe refer back
to
https://wiki.duraspace.org/display/DSDOC4x/Installing+DSpace#InstallingDSpace-Installation
and make sure all the prerequisite steps are done.
If you still have authentication issues
Hi both (cc Hardy),
A colleague of mine encountered this issue a while back, too... I think it
seemed SSL-certificate-related at the time, but I can't recall all the
details...
Hardy made a PR that might resolve this issue by telling puppet-librarian
not to use v1 API:
warded message --
From: Kim Shepherd <k...@shepherd.nz>
Date: 18 May 2018 at 09:39
Subject: DSpace 6.3 Status Update - Release target May 21
To: DSpace Developers <dspace-de...@googlegroups.com>, DSpace Technical
Support <dspace-tech@googlegroups.com>, DSpace C
Hi all,
We are still on track for a May 21 (UTC) release date of DSpace 6.3. Thanks
to all those who have chipped in and helped with pull requests, code
reviews, testing, and joining the conversation.
We've made good progress on testing and merging code contributions, and now
that we're a few
Hi all,
Due to some important fixes for ORCID integration (updating to the new
ORCIDv2 API) that will take a little longer to test, the release date for
6.3 is being pushed to May 21.
We discussed this during the last developer meeting, so if you'd like to
see more you can scroll up in #dev-mtg
;http://www.dspace.org/ns/sword/1.3.1;
> version="1.3"/>
>1999
>
> The sword server log shows the atom entry.
>
> I've tried several settings of Tomcat as maxPostSize, others related to
> uploads, tried with Tomcat 8 and 7 and same results.
> The stra
Hi Germán,
There could be a few reasons for this -- perhaps a timeout somewhere during
the upload (ie. the larger files aren't causing an issue directly, but take
longer and so trigger a timeout) though that typically wouldn't be a
"connection reset" error... another option could be that the
Hi Ying,
Just to help properly reproduce your conditions, could you confirm what
"load the collection" refers to and which UI you're using? Which specific
page(s) will trigger the load times? Is it the collection home page, a
search/browse of (or scoped to) the collection, etc? Administrative
Hi Bill and Ying, just a note to say I haven't managed to reproduce /
investigate this problem thoroughly yet -- i keep getting sidetracked with
other work! And I'm struggling a bit to reproduce with test data now that
Bill is reporting the same problem with a fairly small / typical amount of
Hi all,
Progress is being made toward DSpace 6.3, but it's becoming obvious that a
lot of existing contributions made for the DSpace 6.x codebase will have to
be postponed for 6.4 in order to release 6.3 in a timely manner.
We are currently aiming for a release on May 1st, which probably means a
classificação conforme OS PRESI 01/2015)
>
>
> Dear Kim Shepherd,
>
> I hope this finds you well.
>
> I am a librarian at the Brazilian Development Bank and we use DSpace to
> support our institutional repository. Actually, we are updating from 1.6 to
> 6.0 version.
Hi Subhash,
(snipping the rest of this thread and subject as it does not seem related
to the other messages about maven errors)
You need to be in the main DSpace source directory when you run maven
commands. So for example, if you extracted the DSpace 6.2 release package
into
Hi all,
It's been a while since DSpace 6.2 was released, and in that time a lot of
fixes and improvements have been identified.
There's currently a push to get a version 6.3 released soon. But we can't
do it alone!
If you know of an open JIRA issue or contribution that you really want to
see
Hi Paul,
Very belated reply to this but thought I might as well chip in since I i
just encountered the same problem! ;)
The problem is that classes in org.dspace.app.webui.jsptag use jsp-api as
well as servlet-api, but jsp-api isn't included as a dependency in the
pom.xml for the jspui
It might also end up easier (and more consistent in terms of queries /
logic used, compared to the overall 'statistics' report) to modify the
Statistics report to accept start / end date ranges, rather than try to
generate all the old monthly reports.
I've done this for the Workflow stats page
-org.slack.com)
Cheers!
Kim Shepherd
(on behalf of the DSpace 6.4 release team / DSpace committers)
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed
Hi all,
We're still working on getting reviews, tests and merges done for DSpace
6.4, and inevitably a few improvements have cropped up that would be
*really* nice to get into this release, but are a bit larger than a typical
bugfix and so need a bit more attention.
eg.
28 matches
Mail list logo
