xmlui | XML User Interface for Appcelerator

For my future reference, this is what I have made to show the thumbnails for harvested items.

This answer is based on DSpace 5x Mirage2 Theme but it can also be applied to DSpace 6x Mirage2.

In item-view.xsl, locate the block and then insert this code:

I really recommend you to improve this example, but this will do the work if you keep the structure. Translate: Te recomiendo que mejores el código, si sigues la estructura tal y como la definí va a funcionar, pero se puede mejorar.

Sorting via a list of metadataFields currently isn't possible in DSpace's Discovery module.

DiscoverySortFieldConfiguration only supports a single metadataField as noted in the documentation at: https://wiki.duraspace.org/display/DSDOC6x/Discovery#Discovery-Sortoptioncustomizationforsearchresults

You can also see that the code itself only supports one field: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/discovery/configuration/DiscoverySortFieldConfiguration.java#L17

The following code snippet might help. This code turns the subject field into a facet link. It will require a little modification to work for the author field.

i) Your query gets bitstream IDs, not the IDs of the owning item. For most downloaded items you'll want facet.field=owningItem, and possibly also an exclusion so you don't count thumbnails (something like &fq=bundleName:ORIGINAL - you'll need to adjust that if you have non standard bundle names).

ii) Looks good to me. You probably want something like to suppress the random XML junk you're seeing.

iii) I think it'll be better to get the metadata from the Discovery Solr core rather than trying to obtain the mets.xml file. You may be able to do a Solr join to the discovery core and get the title (or whatever other metadata you want) from there all in one query, but I'm not sure that works with faceting. You could, in your template, make a query to the Discovery core for each ID to get what you're after (eg http://localhost:8080/solr/search/select?q=*:*&fq=search.id=[id-goes-here]&rows=1&fl=title).

iv) Depends on whether you think writing Java code is easier ;) I have solved much the same issue locally in a two-step process: (a) query solr once per day with a query much like yours and write the results to a (JSON) file; (b) write Java code for a Cocoon transformer that loads the item IDs from the file, looks up the corresponding item's title then puts that into the page in a useful format. Not sure whether your approach is any better/worse! Though my approach avoids having to query Solr in real time, which we found to be quite resource intense.

Just for reference, my query for the JSON file mentioned in (iv) is http://localhost:8080/solr/statistics/select?q=*:*&fq=-isBot:true&fq=type:0&fq=statistics_type:view&facet=true&facet.field=owningItem&facet.limit=5&indent=true&rows=0&fq=time:[NOW/DAY-7DAYS+TO+NOW/DAY]&facet.mincount=5&fq=bundleName:ORIGINAL&wt=json&omitHeader=true

• get non-bot hits
• hits for bitstreams (type 0)
• where the statistics type is view (not workflow or whatever else there is)
• we want them grouped by the corresponding item's ID
• we only want 5
• we want this to be indented (this is just for optics)
• we want 0 rows of data (which would be in addition to the facets - we only care about facets)
• we want the last 7 full days
• we only want items whose files have been downloaded at least 5 times
• we only want ORIGINAL bundle, not thumbnails etc
• we want JSON format
• we want to skip some of the Solr results stuff that we don't care about

Comment out the following code to hide the display of that information. https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/xsl/aspect/artifactbrowser/community-list.xsl#L66-L73

If I open up your OAI landing page at https://repositorioaberto.uab.pt/oai/request?verb=Identify

I see that the links for the OAI verbs do not conform to the original URL

http://repositorioaberto.uab.pt/oaiextended/request?verb=ListSets

Can you explain why "oaiextended" is part of the path? Could this be the source of the problem?

No, there is no difference.

See https://msdn.microsoft.com/en-us/library/ms256086(v=vs.110).aspx

The expressions ./node and node are equivalent.

From the dspace.log output it looks like your authentication methods are not set up right. I believe swordv2 requires you to have password authentication enabled.