talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsCollection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging Form, the select elements for are not being populated with options from vocabulary instances, nor with options defined in the App layer field definition. I've tried with and without custom selectors (since many of the collection-object fields seem to have custom selectors) but it has not helped.
The vocabulary terms have been initialized and can be retrieved via the cspace-service/vocabularies service endpoint, so they are are making it into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the logs but haven't found anything indicating what the error could be, so any help would be greatly appreciated.
Thanks,
Chad
Hi All,
Thanks to Jesse for pointing out some errant closing brackets in my app layer config. Fixed those, but, unfortunately, the problem of fields not being populated with the vocabulary on inline data persists.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of Chad Nelson chad.nelson@lyrasis.org
Sent: Tuesday, March 31, 2015 11:45 AM
To: talk@lists.collectionspace.org
Subject: [Talk] Collection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging Form, the select elements for are not being populated with options from vocabulary instances, nor with options defined in the App layer field definition. I've tried with and without custom selectors (since many of the collection-object fields seem to have custom selectors) but it has not helped.
The vocabulary terms have been initialized and can be retrieved via the cspace-service/vocabularies service endpoint, so they are are making it into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the logs but haven't found anything indicating what the error could be, so any help would be greatly appreciated.
Thanks,
Chad
Hi Chad,
Have you tried clearing your browser cache?
Ray
On Tue, Mar 31, 2015 at 12:08 PM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi All,
Thanks to Jesse for pointing out some errant closing brackets in my app
layer config. Fixed those, but, unfortunately, the problem of fields not
being populated with the vocabulary on inline data persists.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of Chad
Nelson chad.nelson@lyrasis.org
Sent: Tuesday, March 31, 2015 11:45 AM
To: talk@lists.collectionspace.org
Subject: [Talk] Collection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging
Form, the select elements for are not being populated with options from
vocabulary instances, nor with options defined in the App layer field
definition. I've tried with and without custom selectors (since many of the
collection-object fields seem to have custom selectors) but it has not
helped.
The vocabulary terms have been initialized and can be retrieved via the
cspace-service/vocabularies service endpoint, so they are are making it
into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other
procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the
logs but haven't found anything indicating what the error could be, so any
help would be greatly appreciated.
Thanks,
Chad
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chad,
One thought: have you already looked at the merged config files in the
App layer? That might be a way to make sure that, at least in that layer,
the relevant vocabularies a) made it through the merge process and b) are
associated with the correct field(s). More on this:
A merge issue, if present, might be consistent with being able to
access this vocabulary via a Services REST API call, but not seeing it show
up in the UI layer.
GL!
Aron
On Tue, Mar 31, 2015 at 12:08 PM, Chad Nelson chad.nelson@lyrasis.org
wrote:
Hi All,
Thanks to Jesse for pointing out some errant closing brackets in my app
layer config. Fixed those, but, unfortunately, the problem of fields not
being populated with the vocabulary on inline data persists.
Chad
From: Talk talk-bounces@lists.collectionspace.org on behalf of Chad
Nelson chad.nelson@lyrasis.org
Sent: Tuesday, March 31, 2015 11:45 AM
To: talk@lists.collectionspace.org
Subject: [Talk] Collection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging
Form, the select elements for are not being populated with options from
vocabulary instances, nor with options defined in the App layer field
definition. I've tried with and without custom selectors (since many of the
collection-object fields seem to have custom selectors) but it has not
helped.
The vocabulary terms have been initialized and can be retrieved via the
cspace-service/vocabularies service endpoint, so they are are making it
into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other
procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the
logs but haven't found anything indicating what the error could be, so any
help would be greatly appreciated.
Thanks,
Chad
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Ray,
Yeah, on each iteration I'm clearing the browser cache. Also dropping the DBs and recreating to flush out any data.
Chad
From: Ray Lee rhlee@berkeley.edu
Sent: Tuesday, March 31, 2015 3:38 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Collection Object vocabularies not populating UI
Hi Chad,
Have you tried clearing your browser cache?
Ray
On Tue, Mar 31, 2015 at 12:08 PM, Chad Nelson <chad.nelson@lyrasis.orgmailto:chad.nelson@lyrasis.org> wrote:
Hi All,
Thanks to Jesse for pointing out some errant closing brackets in my app layer config. Fixed those, but, unfortunately, the problem of fields not being populated with the vocabulary on inline data persists.
Chad
From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of Chad Nelson <chad.nelson@lyrasis.orgmailto:chad.nelson@lyrasis.org>
Sent: Tuesday, March 31, 2015 11:45 AM
To: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: [Talk] Collection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging Form, the select elements for are not being populated with options from vocabulary instances, nor with options defined in the App layer field definition. I've tried with and without custom selectors (since many of the collection-object fields seem to have custom selectors) but it has not helped.
The vocabulary terms have been initialized and can be retrieved via the cspace-service/vocabularies service endpoint, so they are are making it into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the logs but haven't found anything indicating what the error could be, so any help would be greatly appreciated.
Thanks,
Chad
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Aron,
Well, I looked at the merge record for the collection-object config and it appears to be correct, as in the tags are where I expect them to be , though I'm not entirely sure what an error would look like here.
In the merged file, contentWorkType looks exactly the same as it does in the mmi-collection-object.xml file:
<field id="contentWorkType" autocomplete="vocab-contentworktype" ui-type="enum" section="mmi"><selector>object-description-contentWorkType</selector>
Same for the contentEntityType.
<field id="contentEntityType" section="mmi"> <selector>object-information-contentEntityType</selector> <options> <option id="">Please select a value</option> <option id="depicts">depicts</option> <option id="references">references</option> <option id="seealso">see also</option> </options> </field>Is something different supposed to happen? Doesn't seem like it.
Unless you are saying that there should be a merge record for the vocabularies.
I'm actually not merging the vocabularies, just overriding because trying to merge vocabularies always seemed to give an error about root elements not matching, and the examples I have been looking at took the same approach.
I've attached the merged file if you want to have a look at it to see if I have missed anything crucial.
Chad
From: aronroberts@gmail.com aronroberts@gmail.com on behalf of Aron Roberts aron@socrates.berkeley.edu
Sent: Tuesday, March 31, 2015 3:44 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] Collection Object vocabularies not populating UI
Hi Chad,
One thought: have you already looked at the merged config files in the App layer? That might be a way to make sure that, at least in that layer, the relevant vocabularies a) made it through the merge process and b) are associated with the correct field(s). More on this:
A merge issue, if present, might be consistent with being able to access this vocabulary via a Services REST API call, but not seeing it show up in the UI layer.
GL!
Aron
On Tue, Mar 31, 2015 at 12:08 PM, Chad Nelson <chad.nelson@lyrasis.orgmailto:chad.nelson@lyrasis.org> wrote:
Hi All,
Thanks to Jesse for pointing out some errant closing brackets in my app layer config. Fixed those, but, unfortunately, the problem of fields not being populated with the vocabulary on inline data persists.
Chad
From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of Chad Nelson <chad.nelson@lyrasis.orgmailto:chad.nelson@lyrasis.org>
Sent: Tuesday, March 31, 2015 11:45 AM
To: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: [Talk] Collection Object vocabularies not populating UI
Hi All,
I'm doing a bit of work adding local fields to collection object form.
While all the new fields I have added are appearing on the Cataloging Form, the select elements for are not being populated with options from vocabulary instances, nor with options defined in the App layer field definition. I've tried with and without custom selectors (since many of the collection-object fields seem to have custom selectors) but it has not helped.
The vocabulary terms have been initialized and can be retrieved via the cspace-service/vocabularies service endpoint, so they are are making it into the db.
Two examples:
Adding field contentWorkType
Adding field ContentEntityType
Also, I have successfully added fields with vocab lookups in other procedure forms, so generally it does work, just not in this instance.
Any ideas on what could be causing the issue? I've searched through the logs but haven't found anything indicating what the error could be, so any help would be greatly appreciated.
Thanks,
Chad
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org