Hilton,
I followed the steps for configuring SOLR Discovery and adapted it to our
repository. It worked correctly to add the new index browse.
But now, I wonder if it is possible to hide the index when you are in a
collection page where this index is not necessary. I don't know if this
could be
Hi,
DSpace v4.1 and JSPUI.
I've been having a look at Google Analytics and I'm interested in embedding
Analytics data into Item View pages (or elsewhere in DSpace).
I've done a bit of googling and can see a number of discussions/solutions to
this from a few years ago and for older versions of
I came across this code. It runs a query against everything. However, I'm
interested in querying two fields such as author and title only. How would I
have to change the code to accomplish that?
div id=aspect.discovery.SiteViewer.div.front-page-search-custom
interactive=yes rend=primary
Hi all,
I'm wondering if there is someone on the list who is running DSpace 3.1+ and
has a collection being properly harvested by Library and Archives Canada's ETD
harvesting program. We recently upgraded from DSpace 1.8 to 3.1 and the LAC
harvesting apparently stopped working. Any pointers
https://jira.duraspace.org/browse/DS-740
I see there is a pull request on this from May 28th. What are the chances that
this will make it into the next release? Just curious as this is a feature I
am very interested in as well. Our marketing department would like to load
photos, and use the
I like the functionality of this pull request as well. If it doesn't get
incorporated, you can implement public thumbnails without too much pain by
creating a new MediaFilter like:
package org.dspace.app.mediafilter;
// imports ...
public class ThumbnailFilter extends JPEGFilter {
public
Hello all,
We recently upgraded our DSpace installation from 1.7 to 3.2 and switched
to Discovery. On the majority of pages discovery works and displays
correctly, but on pages where we have custom sub-themes, discovery does not
display correctly.
Correct display:
Maura,
I discovered some similar circumstance s in which my css and js was not
loading properly.
I do not know if you circumstances are the same as mine, but the following
change to my sitemap.xmap helped
map:match pattern=themes/**/static/**.js
Since upgrading the DSpace 3.x, I have found the OAI service much easier to
troubleshoot by navigating the browser-friendly OAI service.
//yourrepository/oai/request?verb=Identify
Does your collection/item metadata look good through that service?
I believe that the naming conventions for
When you create your collection, you can set up a default read access
permission for the collection which can be assigned to a specific group.
This will create a default item read policy and a default bitstream
read policy for the collection.
If you wish to have different rules for the
10 matches
Mail list logo
