Re: [Dspace-tech] Split up input-forms.xml?
Hi Alan Glad to help. When you get it working can you put it into a PDF and post on the list so that we can also learn. Capture of metadata using the input forms is a very dear topic for the librarians and information specialists! So are the indexes by the way ;-)) Cheers hg *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 On 13 March 2015 at 10:53, Alan Orth alan.o...@gmail.com wrote: Hey, Hilton and Claudia. That's great, so we can just use pure XML semantics to do this... good idea. Also, Bram Luyten pointed out to me that I could use hierarchical Discovery facets: https://wiki.duraspace.org/display/DSDOC4x/Discovery#Discovery-Hierarchical%28taxonomiesbased%29sidebarfacets Thanks for the advice, I'll play around and see what I can come up with. Cheers, Alan On Thu, Mar 12, 2015 at 5:18 PM, Claudia Jürgen claudia.juer...@ub.tu-dortmund.de wrote: Hey Alan, we did split the input forms up into different forms - using quite a variety and both in English and German, the form map etc. Here ist how you can do it input-forms.xml ?xml version=1.0 encoding='iso-8859-1' ? !DOCTYPE input-forms SYSTEM input-forms.dtd [ !ENTITY map SYSTEM path to the form map !ENTITY basic SYSTEM path to the form basic ... ] input-forms map; form-definitions basic; /form-definitions ... /input-forms We are using 4.2. Hope this helps Claudia Jürgen Am 12.03.2015 um 14:07 schrieb Alan Orth: 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 -- 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 -- Alan Orth alan.o...@gmail.com https://alaninkenya.org https://mjanja.ch In heaven all the interesting people are missing. -Friedrich Nietzsche GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 -- 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
Re: [Dspace-tech] Split up input-forms.xml?
Hey, Hilton and Claudia. That's great, so we can just use pure XML semantics to do this... good idea. Also, Bram Luyten pointed out to me that I could use hierarchical Discovery facets: https://wiki.duraspace.org/display/DSDOC4x/Discovery#Discovery-Hierarchical%28taxonomiesbased%29sidebarfacets Thanks for the advice, I'll play around and see what I can come up with. Cheers, Alan On Thu, Mar 12, 2015 at 5:18 PM, Claudia Jürgen claudia.juer...@ub.tu-dortmund.de wrote: Hey Alan, we did split the input forms up into different forms - using quite a variety and both in English and German, the form map etc. Here ist how you can do it input-forms.xml ?xml version=1.0 encoding='iso-8859-1' ? !DOCTYPE input-forms SYSTEM input-forms.dtd [ !ENTITY map SYSTEM path to the form map !ENTITY basic SYSTEM path to the form basic ... ] input-forms map; form-definitions basic; /form-definitions ... /input-forms We are using 4.2. Hope this helps Claudia Jürgen Am 12.03.2015 um 14:07 schrieb Alan Orth: 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 -- 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 -- Alan Orth alan.o...@gmail.com https://alaninkenya.org https://mjanja.ch In heaven all the interesting people are missing. -Friedrich Nietzsche GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 -- 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
Re: [Dspace-tech] Split up input-forms.xml?
Hi Alan Perhaps this will work: http://xml.silmaril.ie/includes.html See: http://www.w3.org/TR/xinclude/ Cheers hg *Hilton Gibson* Ubuntu Linux Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 On 12 March 2015 at 15:07, Alan Orth alan.o...@gmail.com wrote: 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 -- 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
Re: [Dspace-tech] Split up input-forms.xml?
Hey Alan, we did split the input forms up into different forms - using quite a variety and both in English and German, the form map etc. Here ist how you can do it input-forms.xml ?xml version=1.0 encoding='iso-8859-1' ? !DOCTYPE input-forms SYSTEM input-forms.dtd [ !ENTITY map SYSTEM path to the form map !ENTITY basic SYSTEM path to the form basic ... ] input-forms map; form-definitions basic; /form-definitions ... /input-forms We are using 4.2. Hope this helps Claudia Jürgen Am 12.03.2015 um 14:07 schrieb Alan Orth: 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 -- 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
[Dspace-tech] Split up input-forms.xml?
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
