Empathy List Archives

YN

Yousuf Nejati

Thu, Feb 16, 2017 9:11 PM

Hi all,

Is it possible to change a static dropdown field, which is statically
defined in the field configuration file of a record type (Cataloging,
Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a
vocabulary/authority? For example, Record Status (which does't seem to be)
versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to
change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/

Hi all, Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field? If possible, what are the necessary steps, beginning at the Services layer? How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method. What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field? Thanks for your time, -Yousuf https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists -- *Yousuf Nejati* CollectionSpace Service Provider www.yousufnejati.com/collectionspace www.collectionspace.org/find-a-registered-service-provider/

JL

John Lowe

Thu, Feb 16, 2017 11:21 PM

Yousuf,

There is a LOT of interest in this question, both at UCB and I think
elsewhere.

We are in the process here of developing a "cookie-cutter" process to
"converting static vocabularies to dynamic vocabularies", and I understand
that the next version of CSpace will have most static vocabularies changed
to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have
someone else "from the outside" try this out -- collaboration is most
welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati yousuf.cspace@gmail.com
wrote:

Hi all,

Is it possible to change a static dropdown field, which is statically
defined in the field configuration file of a record type (Cataloging,
Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a
vocabulary/authority? For example, Record Status (which does't seem to be)
versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to
change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/
changing-dropdown-fields-such-as-collection-and-responsible-
department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_
lists.collectionspace.org

Yousuf, There is a LOT of interest in this question, both at UCB and I think elsewhere. We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic... Also see: https://issues.collectionspace.org/browse/PAHMA-1095 and related JIRAs. You can see some *provisional* code and documentation here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter (Caveat lector: this is a work in progress!) Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome! John On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com> wrote: > Hi all, > > Is it possible to change a static dropdown field, which is statically > defined in the field configuration file of a record type (Cataloging, > Procedural, and Vocabulary), to an autocomplete field? > > If possible, what are the necessary steps, beginning at the Services layer? > > How do we ensure that the fields are backed by the Services layer as a > vocabulary/authority? For example, Record Status (which does't seem to be) > versus Field Collection Method. > > What issues may arise when altering these fields, and is it a bad idea to > change all of the dropdown fields to an autocomplete field? > > Thanks for your time, > > -Yousuf > > https://wiki.collectionspace.org/questions/165216711/ > changing-dropdown-fields-such-as-collection-and-responsible- > department-to-dynamic-lists > > -- > *Yousuf Nejati* > CollectionSpace Service Provider > www.yousufnejati.com/collectionspace > www.collectionspace.org/find-a-registered-service-provider/ > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > >

RJ

Rick Jaffe

Thu, Feb 16, 2017 11:54 PM

Two things to add:

First, the work in progress that John mentions has been ably led by two UC
Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats
to them!

Second: that work converts static lists -- defined in configuration -- to
dynamic lists, which can be modified by the user (with proper permissions)
in the Admin Tab of the web UI.

Yousef, you seem to want do something else: create authorities that contain
those terms. Fields tied to authorities auto-complete; dynamic lists appear
as pulldowns, just as static lists do. Authority terms each have a record
page containing additional information about the term.

Are you truly asking about creating authorities?

Rick (Jaffe)

On Thu, Feb 16, 2017 at 3:21 PM, John Lowe jblowe@berkeley.edu wrote:

Yousuf,

There is a LOT of interest in this question, both at UCB and I think
elsewhere.

We are in the process here of developing a "cookie-cutter" process to
"converting static vocabularies to dynamic vocabularies", and I understand
that the next version of CSpace will have most static vocabularies changed
to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/
scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have
someone else "from the outside" try this out -- collaboration is most
welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati yousuf.cspace@gmail.com
wrote:

Hi all,

Is it possible to change a static dropdown field, which is statically
defined in the field configuration file of a record type (Cataloging,
Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services
layer?

How do we ensure that the fields are backed by the Services layer as a
vocabulary/authority? For example, Record Status (which does't seem to be)
versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to
change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/changin
g-dropdown-fields-such-as-collection-and-responsible-dep
artment-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists
.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_
lists.collectionspace.org

Two things to add: First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them! Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI. Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. Are you truly asking about creating authorities? - Rick (Jaffe) On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu> wrote: > Yousuf, > > There is a LOT of interest in this question, both at UCB and I think > elsewhere. > > We are in the process here of developing a "cookie-cutter" process to > "converting static vocabularies to dynamic vocabularies", and I understand > that the next version of CSpace will have most static vocabularies changed > to dynamic... > > Also see: > > https://issues.collectionspace.org/browse/PAHMA-1095 > > and related JIRAs. > > You can see some *provisional* code and documentation here: > > https://github.com/cspace-deployment/Tools/tree/master/ > scripts/dynamic-converter > > (Caveat lector: this is a work in progress!) > > Hopefully some otherwise will jump in and comment, but we'd love to have > someone else "from the outside" try this out -- collaboration is most > welcome! > > John > > > On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com> > wrote: > >> Hi all, >> >> Is it possible to change a static dropdown field, which is statically >> defined in the field configuration file of a record type (Cataloging, >> Procedural, and Vocabulary), to an autocomplete field? >> >> If possible, what are the necessary steps, beginning at the Services >> layer? >> >> How do we ensure that the fields are backed by the Services layer as a >> vocabulary/authority? For example, Record Status (which does't seem to be) >> versus Field Collection Method. >> >> What issues may arise when altering these fields, and is it a bad idea to >> change all of the dropdown fields to an autocomplete field? >> >> Thanks for your time, >> >> -Yousuf >> >> https://wiki.collectionspace.org/questions/165216711/changin >> g-dropdown-fields-such-as-collection-and-responsible-dep >> artment-to-dynamic-lists >> >> -- >> *Yousuf Nejati* >> CollectionSpace Service Provider >> www.yousufnejati.com/collectionspace >> www.collectionspace.org/find-a-registered-service-provider/ >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists >> .collectionspace.org >> >> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > >

RM

Richard Millet

Fri, Feb 17, 2017 12:03 AM

Yousuf,

John's ALMOST right when he says "the next version CSpace will have most static vocabularies changed to dynamic..." Actually, the next version (v4.5) won't, but we're planning for v5.0 to have most static vocabularies changed to dynamic. A lot will depend on the success that UCB has converting existing static term lists (aka vocabularies) to dynamic term lists for some of its current existing deployments. This involves non-trivial data migration for existing systems.

Also, I'm not sure John and I interpreted your question the same way. I thought you were asking if you could configure the existing UI to perform autocomplete on a static list? If that's your question, I don't know the answer. I doubt it, but Ray Lee would know for sure.

-Richard

From: Talk talk-bounces@lists.collectionspace.org on behalf of John Lowe jblowe@berkeley.edu
Sent: Thursday, February 16, 2017 3:21 PM
To: Yousuf Nejati
Cc: CollectionSpace Talk List
Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists

Yousuf,

There is a LOT of interest in this question, both at UCB and I think elsewhere.

We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com mailto:yousuf.cspace@gmail.com> wrote:

Hi all,

Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace http://www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/http://www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Yousuf, John's ALMOST right when he says "the next version CSpace will have most static vocabularies changed to dynamic..." Actually, the next version (v4.5) won't, but we're planning for v5.0 to have most static vocabularies changed to dynamic. A lot will depend on the success that UCB has converting existing static term lists (aka vocabularies) to dynamic term lists for some of its current existing deployments. This involves non-trivial data migration for existing systems. Also, I'm not sure John and I interpreted your question the same way. I thought you were asking if you could configure the existing UI to perform autocomplete on a static list? If that's your question, I don't know the answer. I doubt it, but Ray Lee would know for sure. -Richard ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of John Lowe <jblowe@berkeley.edu> Sent: Thursday, February 16, 2017 3:21 PM To: Yousuf Nejati Cc: CollectionSpace Talk List Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists Yousuf, There is a LOT of interest in this question, both at UCB and I think elsewhere. We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic... Also see: https://issues.collectionspace.org/browse/PAHMA-1095 and related JIRAs. You can see some *provisional* code and documentation here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter (Caveat lector: this is a work in progress!) Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome! John On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com<mailto:yousuf.cspace@gmail.com>> wrote: Hi all, Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field? If possible, what are the necessary steps, beginning at the Services layer? How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method. What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field? Thanks for your time, -Yousuf https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists -- Yousuf Nejati CollectionSpace Service Provider www.yousufnejati.com/collectionspace<http://www.yousufnejati.com/collectionspace> www.collectionspace.org/find-a-registered-service-provider/<http://www.collectionspace.org/find-a-registered-service-provider/> _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

YN

Yousuf Nejati

Fri, Feb 17, 2017 4:14 AM

Hi all,

Thanks for your reply and I apologize for the confusion. I believe everyone
is correct.

The goals are to take a dropdown list like Record Status, Field Collection
Method, or Collection, for example:

<field id="collection" ui-search="repeatable"

seperate_ui_container="true">
<selector>object-identification-collection</selector>
<options>
<option id="">Please select a value</option>
<option id="library-collection">Library collection</option>
<option id="permanent-collection">Permanent collection</option>
<option id="study-collection">Study collection</option>
<option id="teaching-collection">Teaching collection</option>
</options>
</field>

, and either allow addition to this list through the Administrative panel
of the UI, or convert them to auto-complete fields, where the user can add
a new option similar to adding a new Person or Place authority.

We are talking about a fresh instance and tenant with no data. Given this,
the best option is to use the base-instance-vocabularies.xml to help
initialize these converted fields. Does this sound correct?

Thanks,

Yousuf

On Thu, Feb 16, 2017 at 4:03 PM, Richard Millet richard.millet@lyrasis.org
wrote:

Yousuf,

John's ALMOST right when he says "the next version CSpace will have most
static vocabularies changed to dynamic..." Actually, the next version
(v4.5) won't, but we're planning for v5.0 to have most static vocabularies
changed to dynamic. A lot will depend on the success that UCB has
converting existing static term lists (aka vocabularies) to dynamic term
lists for some of its current existing deployments. This involves
non-trivial data migration for existing systems.

Also, I'm not sure John and I interpreted your question the same way. I
thought you were asking if you could configure the existing UI to perform
autocomplete on a static list? If that's your question, I don't know the
answer. I doubt it, but Ray Lee would know for sure.

-Richard

From: Talk talk-bounces@lists.collectionspace.org on behalf of John
Lowe jblowe@berkeley.edu
Sent: Thursday, February 16, 2017 3:21 PM
To: Yousuf Nejati
Cc: CollectionSpace Talk List
Subject: Re: [Talk] Changing dropdown fields, such as Collection and
Responsible Department, to dynamic lists

Yousuf,

There is a LOT of interest in this question, both at UCB and I think
elsewhere.

We are in the process here of developing a "cookie-cutter" process to
"converting static vocabularies to dynamic vocabularies", and I understand
that the next version of CSpace will have most static vocabularies changed
to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/
scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have
someone else "from the outside" try this out -- collaboration is most
welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com<
mailto:yousuf.cspace@gmail.com>> wrote:

Hi all,

Is it possible to change a static dropdown field, which is statically
defined in the field configuration file of a record type (Cataloging,
Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a
vocabulary/authority? For example, Record Status (which does't seem to be)
versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to
change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/
changing-dropdown-fields-such-as-collection-and-responsible-
department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace<http://www.yousufnejati.com/
collectionspace>
www.collectionspace.org/find-a-registered-service-provider/<
http://www.collectionspace.org/find-a-registered-service-provider/>

Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_
lists.collectionspace.org

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/

Hi all, Thanks for your reply and I apologize for the confusion. I believe everyone is correct. The goals are to take a dropdown list like Record Status, Field Collection Method, or Collection, for example: <field id="collection" ui-search="repeatable" seperate_ui_container="true"> <selector>object-identification-collection</selector> <options> <option id="">Please select a value</option> <option id="library-collection">Library collection</option> <option id="permanent-collection">Permanent collection</option> <option id="study-collection">Study collection</option> <option id="teaching-collection">Teaching collection</option> </options> </field> , and either allow addition to this list through the Administrative panel of the UI, or convert them to auto-complete fields, where the user can add a new option similar to adding a new Person or Place authority. We are talking about a fresh instance and tenant with no data. Given this, the best option is to use the base-instance-vocabularies.xml to help initialize these converted fields. Does this sound correct? Thanks, Yousuf On Thu, Feb 16, 2017 at 4:03 PM, Richard Millet <richard.millet@lyrasis.org> wrote: > Yousuf, > > John's ALMOST right when he says "the next version CSpace will have most > static vocabularies changed to dynamic..." Actually, the next version > (v4.5) won't, but we're planning for v5.0 to have most static vocabularies > changed to dynamic. A lot will depend on the success that UCB has > converting existing static term lists (aka vocabularies) to dynamic term > lists for some of its current existing deployments. This involves > non-trivial data migration for existing systems. > > Also, I'm not sure John and I interpreted your question the same way. I > thought you were asking if you could configure the existing UI to perform > autocomplete on a static list? If that's your question, I don't know the > answer. I doubt it, but Ray Lee would know for sure. > > -Richard > ________________________________________ > From: Talk <talk-bounces@lists.collectionspace.org> on behalf of John > Lowe <jblowe@berkeley.edu> > Sent: Thursday, February 16, 2017 3:21 PM > To: Yousuf Nejati > Cc: CollectionSpace Talk List > Subject: Re: [Talk] Changing dropdown fields, such as Collection and > Responsible Department, to dynamic lists > > Yousuf, > > There is a LOT of interest in this question, both at UCB and I think > elsewhere. > > We are in the process here of developing a "cookie-cutter" process to > "converting static vocabularies to dynamic vocabularies", and I understand > that the next version of CSpace will have most static vocabularies changed > to dynamic... > > Also see: > > https://issues.collectionspace.org/browse/PAHMA-1095 > > and related JIRAs. > > You can see some *provisional* code and documentation here: > > https://github.com/cspace-deployment/Tools/tree/master/ > scripts/dynamic-converter > > (Caveat lector: this is a work in progress!) > > Hopefully some otherwise will jump in and comment, but we'd love to have > someone else "from the outside" try this out -- collaboration is most > welcome! > > John > > > On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com< > mailto:yousuf.cspace@gmail.com>> wrote: > > Hi all, > > Is it possible to change a static dropdown field, which is statically > defined in the field configuration file of a record type (Cataloging, > Procedural, and Vocabulary), to an autocomplete field? > > If possible, what are the necessary steps, beginning at the Services layer? > > How do we ensure that the fields are backed by the Services layer as a > vocabulary/authority? For example, Record Status (which does't seem to be) > versus Field Collection Method. > > What issues may arise when altering these fields, and is it a bad idea to > change all of the dropdown fields to an autocomplete field? > > Thanks for your time, > > -Yousuf > > https://wiki.collectionspace.org/questions/165216711/ > changing-dropdown-fields-such-as-collection-and-responsible- > department-to-dynamic-lists > > -- > Yousuf Nejati > CollectionSpace Service Provider > www.yousufnejati.com/collectionspace<http://www.yousufnejati.com/ > collectionspace> > www.collectionspace.org/find-a-registered-service-provider/< > http://www.collectionspace.org/find-a-registered-service-provider/> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > > > -- *Yousuf Nejati* CollectionSpace Service Provider www.yousufnejati.com/collectionspace www.collectionspace.org/find-a-registered-service-provider/

CH

Chris Hoffman

Fri, Feb 17, 2017 4:37 PM

One comment on Rick’s comment:

Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists.

If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students.

Cheers,
Chris

On Feb 16, 2017, at 3:54 PM, Rick Jaffe rjaffe@berkeley.edu wrote:

Two things to add:

First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them!

Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI.

Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

Are you truly asking about creating authorities?

Rick (Jaffe)

On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu mailto:jblowe@berkeley.edu> wrote:
Yousuf,

There is a LOT of interest in this question, both at UCB and I think elsewhere.

We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095 https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com mailto:yousuf.cspace@gmail.com> wrote:
Hi all,
Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field?
If possible, what are the necessary steps, beginning at the Services layer?
How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method.
What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field?
Thanks for your time,
-Yousuf

https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace http://www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/ http://www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

One comment on Rick’s comment: > Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists. If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students. Cheers, Chris > On Feb 16, 2017, at 3:54 PM, Rick Jaffe <rjaffe@berkeley.edu> wrote: > > Two things to add: > > First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them! > > Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI. > > Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. > > Are you truly asking about creating authorities? > > - Rick (Jaffe) > > > > On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu <mailto:jblowe@berkeley.edu>> wrote: > Yousuf, > > There is a LOT of interest in this question, both at UCB and I think elsewhere. > > We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic... > > Also see: > > https://issues.collectionspace.org/browse/PAHMA-1095 <https://issues.collectionspace.org/browse/PAHMA-1095> > > and related JIRAs. > > You can see some *provisional* code and documentation here: > > https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter <https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter> > > (Caveat lector: this is a work in progress!) > > Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome! > > John > > > On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com <mailto:yousuf.cspace@gmail.com>> wrote: > Hi all, > Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field? > If possible, what are the necessary steps, beginning at the Services layer? > How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method. > What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field? > Thanks for your time, > -Yousuf > > https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists <https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists> > > -- > Yousuf Nejati > CollectionSpace Service Provider > www.yousufnejati.com/collectionspace <http://www.yousufnejati.com/collectionspace> > www.collectionspace.org/find-a-registered-service-provider/ <http://www.collectionspace.org/find-a-registered-service-provider/> > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

RM

Richard Millet

Fri, Feb 17, 2017 4:51 PM

Sorry for repeating this point. Since Yousuf is deploying a NEW instance, he should feel free to make the change via a custom tenant configuration. There's no need to wait for the UCB work.

From: Talk talk-bounces@lists.collectionspace.org on behalf of Chris Hoffman chris_h@berkeley.edu
Sent: Friday, February 17, 2017 8:37 AM
To: Rick Jaffe
Cc: Yousuf Nejati; CollectionSpace Talk List
Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists

One comment on Rick’s comment:
Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists.

If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students.

Cheers,
Chris

On Feb 16, 2017, at 3:54 PM, Rick Jaffe <rjaffe@berkeley.edu mailto:rjaffe@berkeley.edu> wrote:

Two things to add:

First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them!

Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI.

Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

Are you truly asking about creating authorities?

Rick (Jaffe)

On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu mailto:jblowe@berkeley.edu> wrote:
Yousuf,

There is a LOT of interest in this question, both at UCB and I think elsewhere.

We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com mailto:yousuf.cspace@gmail.com> wrote:
Hi all,

Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace http://www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/http://www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Sorry for repeating this point. Since Yousuf is deploying a NEW instance, he should feel free to make the change via a custom tenant configuration. There's no need to wait for the UCB work. ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Chris Hoffman <chris_h@berkeley.edu> Sent: Friday, February 17, 2017 8:37 AM To: Rick Jaffe Cc: Yousuf Nejati; CollectionSpace Talk List Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists One comment on Rick’s comment: Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists. If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students. Cheers, Chris On Feb 16, 2017, at 3:54 PM, Rick Jaffe <rjaffe@berkeley.edu<mailto:rjaffe@berkeley.edu>> wrote: Two things to add: First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them! Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI. Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. Are you truly asking about creating authorities? - Rick (Jaffe) On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu<mailto:jblowe@berkeley.edu>> wrote: Yousuf, There is a LOT of interest in this question, both at UCB and I think elsewhere. We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic... Also see: https://issues.collectionspace.org/browse/PAHMA-1095 and related JIRAs. You can see some *provisional* code and documentation here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter (Caveat lector: this is a work in progress!) Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome! John On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com<mailto:yousuf.cspace@gmail.com>> wrote: Hi all, Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field? If possible, what are the necessary steps, beginning at the Services layer? How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method. What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field? Thanks for your time, -Yousuf https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists -- Yousuf Nejati CollectionSpace Service Provider www.yousufnejati.com/collectionspace<http://www.yousufnejati.com/collectionspace> www.collectionspace.org/find-a-registered-service-provider/<http://www.collectionspace.org/find-a-registered-service-provider/> _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

RM

Richard Millet

Sat, Feb 18, 2017 1:37 AM

Yousuf,

Here is a link to a GitHub commit showing how to reconfigure the testsci tenant's cataloging record's "collection" field to reference a dynamic term list (aka, vocabulary) rather than a static term list:

https://github.com/collectionspace/application/commit/d5e4ae71f126e0fdddf5d7d0076914a4b30af1b4

Changes are needed ONLY in the Application layer's configuration for the testsci tenant.

Remember, this is a tenant-specific customization of the field and that you should do this only for brand new deployments. If you need/want to do this for an existing deployment with existing data, you'll need to perform steps similar to the ones documented here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

-Richard

From: Talk talk-bounces@lists.collectionspace.org on behalf of Richard Millet richard.millet@lyrasis.org
Sent: Friday, February 17, 2017 8:51 AM
To: Chris Hoffman
Cc: Yousuf Nejati; CollectionSpace Talk List
Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists

Sorry for repeating this point. Since Yousuf is deploying a NEW instance, he should feel free to make the change via a custom tenant configuration. There's no need to wait for the UCB work.

From: Talk talk-bounces@lists.collectionspace.org on behalf of Chris Hoffman chris_h@berkeley.edu
Sent: Friday, February 17, 2017 8:37 AM
To: Rick Jaffe
Cc: Yousuf Nejati; CollectionSpace Talk List
Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists

One comment on Rick’s comment:
Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists.

If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students.

Cheers,
Chris

On Feb 16, 2017, at 3:54 PM, Rick Jaffe <rjaffe@berkeley.edu mailto:rjaffe@berkeley.edu> wrote:

Two things to add:

First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them!

Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI.

Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term.

Are you truly asking about creating authorities?

Rick (Jaffe)

On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu mailto:jblowe@berkeley.edu> wrote:
Yousuf,

There is a LOT of interest in this question, both at UCB and I think elsewhere.

We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic...

Also see:

https://issues.collectionspace.org/browse/PAHMA-1095

and related JIRAs.

You can see some provisional code and documentation here:

https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter

(Caveat lector: this is a work in progress!)

Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome!

John

On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com mailto:yousuf.cspace@gmail.com> wrote:
Hi all,

Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field?

If possible, what are the necessary steps, beginning at the Services layer?

How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method.

What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field?

Thanks for your time,

-Yousuf

https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists

--
Yousuf Nejati
CollectionSpace Service Provider
www.yousufnejati.com/collectionspace http://www.yousufnejati.com/collectionspace
www.collectionspace.org/find-a-registered-service-provider/http://www.collectionspace.org/find-a-registered-service-provider/

Talk mailing list
Talk@lists.collectionspace.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Yousuf, Here is a link to a GitHub commit showing how to reconfigure the testsci tenant's cataloging record's "collection" field to reference a dynamic term list (aka, vocabulary) rather than a static term list: https://github.com/collectionspace/application/commit/d5e4ae71f126e0fdddf5d7d0076914a4b30af1b4 Changes are needed ONLY in the Application layer's configuration for the testsci tenant. Remember, this is a tenant-specific customization of the field and that you should do this only for brand new deployments. If you need/want to do this for an existing deployment with existing data, you'll need to perform steps similar to the ones documented here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter -Richard ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Richard Millet <richard.millet@lyrasis.org> Sent: Friday, February 17, 2017 8:51 AM To: Chris Hoffman Cc: Yousuf Nejati; CollectionSpace Talk List Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists Sorry for repeating this point. Since Yousuf is deploying a NEW instance, he should feel free to make the change via a custom tenant configuration. There's no need to wait for the UCB work. ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Chris Hoffman <chris_h@berkeley.edu> Sent: Friday, February 17, 2017 8:37 AM To: Rick Jaffe Cc: Yousuf Nejati; CollectionSpace Talk List Subject: Re: [Talk] Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists One comment on Rick’s comment: Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. It’s true that fields tied to authorities allow the true auto-complete data entry. However, the dropdown lists also allow you to “type ahead” in order to select the entry in the list that you want to use. I guess that’s true for both static lists and dynamic lists. If the goal is to be able to manage the list of values in a dropdown easier, then conversion to dynamic lists is now becoming a more straightforward reality thanks to the work of our UCB students. Cheers, Chris On Feb 16, 2017, at 3:54 PM, Rick Jaffe <rjaffe@berkeley.edu<mailto:rjaffe@berkeley.edu>> wrote: Two things to add: First, the work in progress that John mentions has been ably led by two UC Berkeley student interns, Jennifer Be and Cesar Villalobos-Huizar. Congrats to them! Second: that work converts static lists -- defined in configuration -- to dynamic lists, which can be modified by the user (with proper permissions) in the Admin Tab of the web UI. Yousef, you seem to want do something else: create authorities that contain those terms. Fields tied to authorities auto-complete; dynamic lists appear as pulldowns, just as static lists do. Authority terms each have a record page containing additional information about the term. Are you truly asking about creating authorities? - Rick (Jaffe) On Thu, Feb 16, 2017 at 3:21 PM, John Lowe <jblowe@berkeley.edu<mailto:jblowe@berkeley.edu>> wrote: Yousuf, There is a LOT of interest in this question, both at UCB and I think elsewhere. We are in the process here of developing a "cookie-cutter" process to "converting static vocabularies to dynamic vocabularies", and I understand that the next version of CSpace will have most static vocabularies changed to dynamic... Also see: https://issues.collectionspace.org/browse/PAHMA-1095 and related JIRAs. You can see some *provisional* code and documentation here: https://github.com/cspace-deployment/Tools/tree/master/scripts/dynamic-converter (Caveat lector: this is a work in progress!) Hopefully some otherwise will jump in and comment, but we'd love to have someone else "from the outside" try this out -- collaboration is most welcome! John On Thu, Feb 16, 2017 at 1:11 PM, Yousuf Nejati <yousuf.cspace@gmail.com<mailto:yousuf.cspace@gmail.com>> wrote: Hi all, Is it possible to change a static dropdown field, which is statically defined in the field configuration file of a record type (Cataloging, Procedural, and Vocabulary), to an autocomplete field? If possible, what are the necessary steps, beginning at the Services layer? How do we ensure that the fields are backed by the Services layer as a vocabulary/authority? For example, Record Status (which does't seem to be) versus Field Collection Method. What issues may arise when altering these fields, and is it a bad idea to change all of the dropdown fields to an autocomplete field? Thanks for your time, -Yousuf https://wiki.collectionspace.org/questions/165216711/changing-dropdown-fields-such-as-collection-and-responsible-department-to-dynamic-lists -- Yousuf Nejati CollectionSpace Service Provider www.yousufnejati.com/collectionspace<http://www.yousufnejati.com/collectionspace> www.collectionspace.org/find-a-registered-service-provider/<http://www.collectionspace.org/find-a-registered-service-provider/> _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

talk@lists.collectionspace.org

Changing dropdown fields, such as Collection and Responsible Department, to dynamic lists