Dear people Anybody knows if is there some way to enhace the management of the input-forms.xml? I have a case where the repository has a complex comm/colls structure with a lot of collections and several input sheets. I wish to know if is there a way to divide the input-forms.xml and import litlle ones. Also could be good if I can apply some general rules for the collections, for instance to say handle=10665/33* will use the form X.
The use of one only and monolithic input-forms.xml really seems to be very uncomfortable when the repository grows. The same under the idea to maintain the vocabularies inside... Any idea will be appreciated ------------------------------------ In dspace users list I've obtained the follwing answers: * You can break down the input-forms.xml in several files, e.g.: the form map and different forms define and include these and only keep the stuff applying to various forms like value pairs list in the input-forms itself. *You could try XInclude. I don't know whether it will work in this context. https://en.wikipedia.org/wiki/XInclude http://www.w3.org/TR/xinclude/ ------------------------------------------ It looks very promising to use xinclude. Somebody has any experience doing something like this? Regards & thanks German
------------------------------------------------------------------------------
_______________________________________________ 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
