As part of the services part of the work on various improvements (preferred / non-preferred terms, multiple vocabularies in an authority, etc.) in CollectionSpace's forthcoming release v2.4, we're planning to remove legacy code around computed (synthesized) display names for authority items. To the best of our knowledge, we don't believe anyone - outside of automated tests of CollectionSpace's services layer - is likely to be using this computed displayname functionality. However, if you *do* happen to use it, or were expecting to use it, please respond here on the Talk list right away. (More details about this functionality appear below.) Thank you, Aron Roberts -- This code synthesizes display names, *if* a 'computed' flag is set in the payload, in requests made to the services REST APIs on creating or updating an authority item. For instance, it synthesizes display names for person records by concatenating forename, initials, and surname, etc. Ripping out this code will significantly simply framework code and reduce maintenance costs; it will also streamline work on authorities improvement in v2.4. My understanding is that this was never used in any production context in a full CollectionSpace system. It's not used by the system's application or UI layers (and hence never used by an end user of the system), isn't used when bulk importing records via the Imports service, etc. As mentioned above, it would only be used by someone sending create or update requests directly to the Services REST APIs, with a Boolean flag of "displayNameComputed" set to "true" in the request payloads.

Does that mean the display name computed flag will go away? Susan On 04/30/2012 03:08 PM, Aron Roberts wrote: > As part of the services part of the work on various > improvements (preferred / non-preferred terms, multiple > vocabularies in an authority, etc.) in CollectionSpace's > forthcoming release v2.4, we're planning to remove > legacy code around computed (synthesized) display > names for authority items. > > To the best of our knowledge, we don't believe > anyone - outside of automated tests of > CollectionSpace's services layer - is likely to be > using this computed displayname functionality. > > However, if you *do* happen to use it, or were > expecting to use it, please respond here on > the Talk list right away. > > (More details about this functionality appear below.) > > Thank you, > Aron Roberts > > -- > > This code synthesizes display names, *if* a 'computed' flag > is set in the payload, in requests made to the services REST > APIs on creating or updating an authority item. For instance, > it synthesizes display names for person records by > concatenating forename, initials, and surname, etc. > > Ripping out this code will significantly simply framework > code and reduce maintenance costs; it will also streamline > work on authorities improvement in v2.4. > > My understanding is that this was never used in any > production context in a full CollectionSpace system. > It's not used by the system's application or UI layers > (and hence never used by an end user of the system), > isn't used when bulk importing records via the Imports > service, etc. As mentioned above, it would only be used > by someone sending create or update requests directly > to the Services REST APIs, with a Boolean flag > of "displayNameComputed" set to "true" in the > request payloads. > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

On Mon, Apr 30, 2012 at 3:12 PM, Susan Stone <sstone@socrates.berkeley.edu> wrote: > Does that mean the display name computed flag will go away? Yes, that's correct, AFAIK. > > Susan > > > On 04/30/2012 03:08 PM, Aron Roberts wrote: >> >> As part of the services part of the work on various >> improvements (preferred / non-preferred terms, multiple >> vocabularies in an authority, etc.) in CollectionSpace's >> forthcoming release v2.4, we're planning to remove >> legacy code around computed (synthesized) display >> names for authority items. >> >> To the best of our knowledge, we don't believe >> anyone - outside of automated tests of >> CollectionSpace's services layer - is likely to be >> using this computed displayname functionality. >> >> However, if you *do* happen to use it, or were >> expecting to use it, please respond here on >> the Talk list right away. >> >> (More details about this functionality appear below.) >> >> Thank you, >> Aron Roberts >> >> -- >> >> This code synthesizes display names, *if* a 'computed' flag >> is set in the payload, in requests made to the services REST >> APIs on creating or updating an authority item.  For instance, >> it synthesizes display names for person records by >> concatenating forename, initials, and surname, etc. >> >> Ripping out this code will significantly simply framework >> code and reduce maintenance costs; it will also streamline >> work on authorities improvement in v2.4. >> >> My understanding is that this was never used in any >> production context in a full CollectionSpace system. >> It's not used by the system's application or UI layers >> (and hence never used by an end user of the system), >> isn't used when bulk importing records via the Imports >> service, etc.  As mentioned above, it would only be used >> by someone sending create or update requests directly >> to the Services REST APIs, with a Boolean flag >> of "displayNameComputed" set to "true" in the >> request payloads. >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >