Hi Bill,
Thanks for your response.
I think I got my terminology mixed up - I was referring to Authority Control
and Choice
Management<https://wiki.duraspace.org/display/DSPACE/Authority+Control+of+Metadata+Values>.
You're right, the input-forms.xml file would be sufficient, but we have several
different controlled vocabularies which may end up being quite long. We
anticipate implementing our controlled vocabularies in a way similar to the way
controlled Subject and Keyword listings are displayed (using a Suggest-like
mechanism for the longest ones, and drop-downs or AJAX overlays for shorter
ones where appropriate). Our difficulty is that the .xml file for the Subject
and Keyword list is not administrable by a logged-in user of the repository.
The UI for the XMLUI hasn't been written yet as far as I can tell.
The Initial Questions we wanted to use haven't been well thought-out at this
point. We were thinking something like "In which language is the content of the
resource?" The language would be selectable from a list (?) of ISO639-3
language codes and names. A related question might be "Is the metadata being
entered in this language?" This would set the metadata language field to that
language rather than "en_US."
The other option I thought of is to skip the Initial Questions page altogether
and have the Describe step spit out all of the form fields we anticipate
needing. We could use CSS/JS to hide some of the not-so-common fields like
Alternate Title. The user would just have to click a hyperlink to expand the
hidden form field and enter its metadata.
Sincerely,
Jay Clark
Application Support Specialist
Mission Aviation Fellowship
Learning Technologies Division
www.maf.org<http://www.maf.org> & www.maflt.org<http://www.maflt.org>
-----Original Message-----
From: William Hays [mailto:[email protected]]
Sent: Friday, March 25, 2011 11:17 AM
To: Jay Clark
Subject: [Dspace-tech] Workflows in DSpace 1.7, XMLUI
Jay,
I'm guessing by the term Choice Control that the functionality would be covered
by the multi-value lists for dropdown input controls in Input Forms. The
online documentation for DSpace Input Forms should explain things and the
default inputforms.xml in the config directory has examples.
The original questions is actually a problem. The data elements behind the
answers to those two questions are maintained values in the data model, which
cause problems when items are ingested from systems other than the online
webapp, e.g. SWORD. I would advise against altering the data model since it
might lead to other problems, including upgrading to new versions of DSpace.
Here at MIT, we have begun work on expanding the ingest model that can provide
for extensibility beyond just two questions without affecting the data model.
I'd be curious to know what additional questions you had in mind to see if what
we're working would cover them. If you can share that information, it would be
appreciated. This would also help to answer the question as to how to provide
the functionality you're looking for without altering the data model.
On your third point, I can only wish you good luck in working with Manakin,
especially with submissions where keeping track of the DSpace API, the XMLUI
API, the XMLUI webapp code and the submission javascript code (which contains a
lot of functionality) can be challenging.
--Bill
Date: Fri, 25 Mar 2011 09:47:30 -0600
From: Jay Clark<[email protected]>
Subject: [Dspace-tech] Workflows in DSpace 1.7, XMLUI
To:"[email protected]"
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hello,
I asked this question for the discussion of workflows in DSpace on the
dspace-general list and want to ask over here on the tech list as well. I have
several questions as I am new to DSpace.
My colleagues and I are investigating DSpace as a solution to a large
repository of digital resources to be made available for translation.
Translated resources will then be re-submitted to the Library with metadata
that indicates the translation relationship. There are future plans for the
repository to be served in multiple user interface languages. We are using
DSpace 1.7 with the XMLUI and a customized theme based on Mirage.
Here are some things we are interested in doing. We think they are
theoretically possible, but would like to find some real-world examples of how
to do them.
* We are interested in changing the workflow to add a few more Initial
Questions. How would one add two or three more Initial Questions to the
submission workflow?
* We would like to derive a new Item from an existing item. Ideally
this would be implemented with a "Submit a New Translation" button on an
existing DSpace Item. In the process, we want to copy some of the source Item's
metadata into the new derived Item (dc.relation information) and display some
of the source Item's metadata adjacent to the metadata entry fields so a
submitter can see the source's title and translate it appropriately into the
language of the new Item. How might this be accomplished?
* We plan to use Choice Control extensively throughout the metadata
entry process. We've managed to setup some sample Choice Controlled fields, but
find that the way to setup these files is cumbersome. Is there a way in the
XMLUI to edit the many Choice Control lists we may have?
We do have more questions, but these may be the most important at the moment.
Sincerely,
Jay Clark
Application Support Specialist
Mission Aviation Fellowship
Learning Technologies Division
www.maf.org<http://www.maf.org<http://www.maf.org%3chttp:/www.maf.org>> &
www.maflt.org<http://www.maflt.org<http://www.maflt.org%3chttp:/www.maflt.org>>
-------------- next part --------------
An HTML attachment was scrubbed...
--
------------
William Hays
Software Development& Analysis
MIT Libraries E25-131
617.324.5682 (phone)
[email protected]<mailto:[email protected]>
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
