Matt, our proof-of-concept repository is running DSpace v1.7.2. I just set
our controlled vocabulary field choices.closed.dc.subject=true and
restarted DSpace, then tried to submit an item. Just as you're seeing, I
was able to type a bogus value for the subject field and DSpace allowed me
to add
Hello,
I work for a city school district. My objective is to implement Dspace as a
repository for teacher lesson plans. The meta data has been modified to
reflect the current standards that are in use. We have created several
controlled vocabularies for this purpose.
I am currently having a
Hi Matt,
If you just want to have a dropdown of values available, then you might
find it easier to just configure a dropdown (and its possible values)
via the [dspace]/config/input-forms.xml' configuration file.
Documentation is available at:
Tim,
Thank you for your response. I greatly appreciate any assistance on this.
Unfortunately the data structure that we have is much more complex than a
drop down menu. At the end of this e-mail is a partial example of one of
the kentucky core content standards.
An end user needs to be able
Hello Matt,
I can't answer your question about changing already added values, but if
you set choices.closed.dc.* to true in dspace.cfg, it should prevent
users from adding values that are not in the controlled vocabulary. For
example, if the metadata field in question is subject, the config
...@duraspace.orgmailto:tdono...@duraspace.org,
dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net
dspace-tech@lists.sourceforge.netmailto:dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] FW: How to limit user selection ONLY to choice drop
down
Hello Matt,
I can't answer
6 matches
Mail list logo
