Hi There, In QAing our Botanical Garden's tenant, I noticed what seems like undesirable behavior for the autocomplete component's 'Add to' feature, and am also seeing this on Nightly. For most (if not all) vocabulary item records (concept, location, org, person, place, taxon), the term status field defaults to 'provisional' only if the record is created through create new and the record editor screen. In some authority types, there are a few other fields that are drop downs with default values: salutation defaults to 'Dear', in person, for example. If, however, the record is created through the 'Add to' feature in the autocomplete widget, these default values don't get saved. What is most misleading is that when the record editor is pulled up for a record created through 'Add to', the default values are displayed as if they had been saved. In order to actually save the default values though, a user must change the value away from the default, and then change the value back to the default, and save the record. This is particularly frustrating for a field like 'term status', which could be used in advanced search to find all vocabulary items in a particular authority and vocabulary that were created on the fly, but also has implications for reporting as well for fields like 'Salutation'. Is this something I should create a JIRA for? Thanks, Amy

File a JIRA? I would say so, yes. Thanks - Patrick Amy Wieliczka <amywieliczka@berkeley.edu> wrote: >Hi There, > >In QAing our Botanical Garden's tenant, I noticed what seems like >undesirable behavior for the autocomplete component's 'Add to' feature, >and >am also seeing this on Nightly. > >For most (if not all) vocabulary item records (concept, location, org, >person, place, taxon), the term status field defaults to 'provisional' >only >if the record is created through create new and the record editor >screen. >In some authority types, there are a few other fields that are drop >downs >with default values: salutation defaults to 'Dear', in person, for >example. >If, however, the record is created through the 'Add to' feature in the >autocomplete widget, these default values don't get saved. > >What is most misleading is that when the record editor is pulled up for >a >record created through 'Add to', the default values are displayed as if >they had been saved. In order to actually save the default values >though, a >user must change the value away from the default, and then change the >value >back to the default, and save the record. > >This is particularly frustrating for a field like 'term status', which >could be used in advanced search to find all vocabulary items in a >particular authority and vocabulary that were created on the fly, but >also >has implications for reporting as well for fields like 'Salutation'. > >Is this something I should create a JIRA for? > >Thanks, >Amy > > >------------------------------------------------------------------------ > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.