Well, I think that is because the correct DC qualifier is advisOr, not
advisEr (it is so in my instance and it works).
Moreover, you should add these lines in your local messages.xml (under
the modules directory):
<message
key="xmlui.ArtifactBrowser.Navigation.browse_advisor">Advisor</message>
<message
key="xmlui.ArtifactBrowser.ConfigurableBrowse.title.metadata.advisor">Advisor</message>
<message
key="xmlui.ArtifactBrowser.ConfigurableBrowse.trail.metadata.advisor">Advisor</message>
<message
key="xmlui.ArtifactBrowser.ConfigurableBrowse.advisor.column_heading">Advisor</message>
<message key="xmlui.dri2xhtml.METS-1.0.item-advisor">Advisor</message>
If that doesn't help, make sure you did the change in the correct file
- ideal is to have a custom theme overriding the default theme
(Reference), in that case you would have to copy the entirety of the
itemSummaryView-DIM-fields template into your theme's xsl file.
The last thing to remember is to change the numbering of other rows
and changing the total row count at the end:
<!-- IMPORTANT: This test should be updated if clauses are
added! -->
<xsl:if test="$clause < 13">
You will also want to add that field into indices to allow searching
and browsing on it (in dspace.cfg; mind the numbering of indices):
search.index.2 = advisor:dc.contributor.advisor
webui.browse.index.3 = advisor:metadata:dc.contributor.advisor:text
and then run
[dspace]/bin/dspace index-init
to recreate the indices.
Let us know if that helped.
Regards,
~~helix84
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
