Hello Daniel,
as you mentioned below this seems to be a CRIS issue.
I tried it on a vanilla 6.x instance with jspui and it works just fine
in all variations (enumeration, each on a seperate line etc.).
Hope this helps
Claudia
Am 11.07.2017 um 11:08 schrieb danielKim:
Thanks for reading this question.
Our library repository uses custom metadata filed so I have added following
lines in the local.cfg configuration file.
webui.itemdisplay.default = dc.title, dc.title.alternative,
dc.contributor.*, \
dc.subject(nobreakline), dc.date.issued(date),
dc.publisher, \
dc.identifier.citation,
dc.relation.ispartofseries, \
dc.description.abstract, dc.description, \
dc.identifier.govdoc, dc.identifier.uri(link),\
dc.identifier.isbn, dc.identifier.issn, \
dc.identifier.ismn, dc.identifier, \
dc.subject.keywords, dc.rights.uri
So far I know without this, the default metadata will be displayed in the
web interface.
The problem is 'webui.itemdisplay.default' will only accept one parameter
and ignore parameters after on.
For example, if I change first line of this configuration,
webui.itemdisplay.default = dc.subject.keywords, dc.title.alternative,
dc.contributor.*, \
The web interface will be look like this:
<https://lh3.googleusercontent.com/-F7ZZ-BVt9no/WWSTVaS_Z2I/AAAAAAAAGn4/35tq3i29yv8ka80X4D6EMnetPcIa2gY-gCLcBGAs/s1600/shit1.png>
So if I change config like this:
webui.itemdisplay.default = dc.title, dc.title.alternative,
dc.contributor.*, \
*......*
*Below are the same as above*
web interface will show the title correctly.
<https://lh3.googleusercontent.com/-xcYB10LHDPU/WWSTYNzkZ1I/AAAAAAAAGn8/NcbTiIp7ICky7jlRSb4DnFANru_xlsJ_QCLcBGAs/s1600/shit2.png>
So it seems webui.itemdisplay.default accepts only one parameter from the
config file but it should read whole configuration and change metadata
display to users.
This is my dspace version information.
<https://lh3.googleusercontent.com/--t7o7A98W8M/WWSUvndE2cI/AAAAAAAAGoI/KQo83X3cUEUaL6T7HZsRphpKp79A_UvqgCLcBGAs/s1600/shit3.png>
I have another dspace server which is running original 6.0 release. (So
this server is made for using CRIS version of dspace)
That old server correctly shows all metadata information as we change
related configurations at local.cfg file.
Do you think this is the bug of CRIS version ? or should I made some
mistake which prevents to dspace can't recognize configurations correctly?
Thanks in advance!
--
Claudia Juergen
Eldorado
Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund
Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
[email protected]
www.ub.tu-dortmund.de
Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen
Schriftstücks per Telefax erfolgen.
Important note: The information included in this e-mail is confidential. It is
solely intended for the recipient. If you are not the intended recipient of
this e-mail please contact the sender and delete this message. Thank you.
Without prejudice of e-mail correspondence, our statements are only legally
binding when they are made in the conventional written form (with personal
signature) or when such documents are sent by fax.
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.