Hey, all.
Our institution has many groups collaborating on one DSpace repository and
we have many sets of metadata terms. In the beginning we thought it was
clever to add them to input-forms.xml, but now this file is nearly 6,000
lines, which is a pain to manage and causes problems when we rebase on top
of new upstream DSpace releases in git. :)
I had a look at the "controlled vocabulary" functionality, which allows you
to break out terms to separate XML files, but this has the unfortunate side
effect of then storing the values as a hierarchy, for example,
"Organization A::Subjects::Subject A", as opposed to just "Subject A". This
breaks basically everything that relies on metadata aggregation or
searching (not to mention it is ugly).
Is there some way to split up input-forms.xml? What are other DSpace users
at large institutions doing? For the record, we're using DSpace 4.3.
Thanks,
Alan
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
