Hey Ray, Thank you for the elegant and clear explanation of how a *single records search* varies from an *all records search*. I was not aware that there was a difference. This makes sense now. I'll add this to the questions forum in the wiki in hopes that it helps others. Thanks for your help! -Yousuf On Thu, Dec 22, 2016 at 2:03 AM, Ray Lee <rhlee@berkeley.edu> wrote: > Hi Yousuf, > Have you regenerated the services layer config? This is one of those cases > where you have to: > > https://wiki.collectionspace.org/display/DOC/Configuring+ > CollectionSpace%27s+Application+Layer+-+An+Overview# > ConfiguringCollectionSpace'sApplicationLayer-AnOverview- > GenerateequivalentServiceslayerfilesandcopyingthemtotheColle > ctionSpaceserver > > Here's why the all record types search is different than the cataloging > records search: > > On the cataloging records search, the app layer makes a request to the > REST API to the /cspace-services/collectionobjects endpoint. If you look > at the response, you'll see the fields returned for each record: > > <fieldsReturned> > csid|uri|refName|updatedAt|workflowState|objectNumber|objectName|title| > responsibleDepartment > </fieldsReturned> > > The app layer/UI layer maps the desired fields into the number and summary > columns. The services layer doesn't care which ones they are. That's the > case for search on any single record type. > > On the all record types search, the app layer is not making separate > requests to the REST API for each record type. It's making a request to a > special "all records" endpoint, which is /cspace-services/servicegroups/common/items. > If you look at that response, you'll see these fields returned for each > record: > > <fieldsReturned> > csid|uri|updatedAt|workflowState|refName|docName|docNumber|docType > </fieldsReturned> > > In this case, you're searching across records with different schemas, so > the services layer can only return fields that it knows are common to all > record types (basically stuff in collectionspace_core), with two > exceptions: the docNumber and docName fields (also referred to as > meta-number and meta-name) are configured for each record type, so the > services layer knows which fields in each record type to map to them. This > configuration is generated from the app layer configuration, depending on > what you've specified as mini="number" and mini="summary". So for all > records search, you need to regenerate the services layer config when > you've changed mini="number" and mini="summary". > > Ray > > > > On Wed, Dec 21, 2016 at 3:52 PM, Yousuf Nejati <yousuf.cspace@gmail.com> > wrote: > >> Hi all, >> >> In the App layer configuration files (https://wiki.collectionspace. >> org/display/DOC/Default+configuration+files+in+the+Application+layer), >> what field and corresponding parameter dictates what populates the >> 'summary' field in *Find & Edit > All Record Types* only search? >> >> Currently, a *Find & Edit > Cataloging Record* summary field is >> correctly populated after modifying the 'mini' attribute, however, this is >> NOT the case for *Find & Edit > All Record Types*. Why is this? >> >> https://wiki.collectionspace.org/display/DOC/How+to+change+t >> he+columns+in+the+search+results >> >> https://wiki.collectionspace.org/display/collectionspace/Summary+Fields >> >> Thanks, >> >> Yousuf >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists >> .collectionspace.org >> >> >

Yousuf, Thanks a ton for adding to the Questions pages (https://wiki.collectionspace.org/questions) on the wiki!!! Doing so is extremely helpful and important. -Richard ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Yousuf Nejati <yousuf.cspace@gmail.com> Sent: Thursday, December 22, 2016 8:59 AM To: Ray Lee Cc: CollectionSpace Talk List Subject: Re: [Talk] Changing the Find & Edit, All Record Types, summary field Hey Ray, Thank you for the elegant and clear explanation of how a single records search varies from an all records search. I was not aware that there was a difference. This makes sense now. I'll add this to the questions forum in the wiki in hopes that it helps others. Thanks for your help! -Yousuf On Thu, Dec 22, 2016 at 2:03 AM, Ray Lee <rhlee@berkeley.edu<mailto:rhlee@berkeley.edu>> wrote: Hi Yousuf, Have you regenerated the services layer config? This is one of those cases where you have to: https://wiki.collectionspace.org/display/DOC/Configuring+CollectionSpace%27s+Application+Layer+-+An+Overview#ConfiguringCollectionSpace'sApplicationLayer-AnOverview-GenerateequivalentServiceslayerfilesandcopyingthemtotheCollectionSpaceserver Here's why the all record types search is different than the cataloging records search: On the cataloging records search, the app layer makes a request to the REST API to the /cspace-services/collectionobjects endpoint. If you look at the response, you'll see the fields returned for each record: <fieldsReturned> csid|uri|refName|updatedAt|workflowState|objectNumber|objectName|title|responsibleDepartment </fieldsReturned> The app layer/UI layer maps the desired fields into the number and summary columns. The services layer doesn't care which ones they are. That's the case for search on any single record type. On the all record types search, the app layer is not making separate requests to the REST API for each record type. It's making a request to a special "all records" endpoint, which is /cspace-services/servicegroups/common/items. If you look at that response, you'll see these fields returned for each record: <fieldsReturned> csid|uri|updatedAt|workflowState|refName|docName|docNumber|docType </fieldsReturned> In this case, you're searching across records with different schemas, so the services layer can only return fields that it knows are common to all record types (basically stuff in collectionspace_core), with two exceptions: the docNumber and docName fields (also referred to as meta-number and meta-name) are configured for each record type, so the services layer knows which fields in each record type to map to them. This configuration is generated from the app layer configuration, depending on what you've specified as mini="number" and mini="summary". So for all records search, you need to regenerate the services layer config when you've changed mini="number" and mini="summary". Ray On Wed, Dec 21, 2016 at 3:52 PM, Yousuf Nejati <yousuf.cspace@gmail.com<mailto:yousuf.cspace@gmail.com>> wrote: Hi all, In the App layer configuration files (https://wiki.collectionspace.org/display/DOC/Default+configuration+files+in+the+Application+layer), what field and corresponding parameter dictates what populates the 'summary' field in Find & Edit > All Record Types only search? Currently, a Find & Edit > Cataloging Record summary field is correctly populated after modifying the 'mini' attribute, however, this is NOT the case for Find & Edit > All Record Types. Why is this? https://wiki.collectionspace.org/display/DOC/How+to+change+the+columns+in+the+search+results https://wiki.collectionspace.org/display/collectionspace/Summary+Fields Thanks, Yousuf _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

P.S. I'm working on search results now for the new UI. It will be easy to add/remove/relabel/reorder the columns displayed in the search results for each record type. Look for a blog post about this in the new year. Ray On Thu, Dec 22, 2016 at 8:59 AM, Yousuf Nejati <yousuf.cspace@gmail.com> wrote: > Hey Ray, > > Thank you for the elegant and clear explanation of how a *single records > search* varies from an *all records search*. I was not aware that there > was a difference. This makes sense now. I'll add this to the questions > forum in the wiki in hopes that it helps others. > > Thanks for your help! > > -Yousuf > > > On Thu, Dec 22, 2016 at 2:03 AM, Ray Lee <rhlee@berkeley.edu> wrote: > >> Hi Yousuf, >> Have you regenerated the services layer config? This is one of those >> cases where you have to: >> >> https://wiki.collectionspace.org/display/DOC/Configuring+Col >> lectionSpace%27s+Application+Layer+-+An+Overview#Configurin >> gCollectionSpace'sApplicationLayer-AnOverview-Generateequiva >> lentServiceslayerfilesandcopyingthemtotheCollectionSpaceserver >> >> Here's why the all record types search is different than the cataloging >> records search: >> >> On the cataloging records search, the app layer makes a request to the >> REST API to the /cspace-services/collectionobjects endpoint. If you look >> at the response, you'll see the fields returned for each record: >> >> <fieldsReturned> >> csid|uri|refName|updatedAt|workflowState|objectNumber|object >> Name|title|responsibleDepartment >> </fieldsReturned> >> >> The app layer/UI layer maps the desired fields into the number and >> summary columns. The services layer doesn't care which ones they are. >> That's the case for search on any single record type. >> >> On the all record types search, the app layer is not making separate >> requests to the REST API for each record type. It's making a request to a >> special "all records" endpoint, which is /cspace-services/servicegroups/common/items. >> If you look at that response, you'll see these fields returned for each >> record: >> >> <fieldsReturned> >> csid|uri|updatedAt|workflowState|refName|docName|docNumber|docType >> </fieldsReturned> >> >> In this case, you're searching across records with different schemas, so >> the services layer can only return fields that it knows are common to all >> record types (basically stuff in collectionspace_core), with two >> exceptions: the docNumber and docName fields (also referred to as >> meta-number and meta-name) are configured for each record type, so the >> services layer knows which fields in each record type to map to them. This >> configuration is generated from the app layer configuration, depending on >> what you've specified as mini="number" and mini="summary". So for all >> records search, you need to regenerate the services layer config when >> you've changed mini="number" and mini="summary". >> >> Ray >> >> >> >> On Wed, Dec 21, 2016 at 3:52 PM, Yousuf Nejati <yousuf.cspace@gmail.com> >> wrote: >> >>> Hi all, >>> >>> In the App layer configuration files (https://wiki.collectionspace. >>> org/display/DOC/Default+configuration+files+in+the+Application+layer), >>> what field and corresponding parameter dictates what populates the >>> 'summary' field in *Find & Edit > All Record Types* only search? >>> >>> Currently, a *Find & Edit > Cataloging Record* summary field is >>> correctly populated after modifying the 'mini' attribute, however, this is >>> NOT the case for *Find & Edit > All Record Types*. Why is this? >>> >>> https://wiki.collectionspace.org/display/DOC/How+to+change+t >>> he+columns+in+the+search+results >>> >>> https://wiki.collectionspace.org/display/collectionspace/Summary+Fields >>> >>> Thanks, >>> >>> Yousuf >>> >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists >>> .collectionspace.org >>> >>> >> >

Thanks, Ray! This will be a very big enhancement over the current UI. Chris On Dec 22, 2016, at 1:21 PM, Ray Lee <rhlee@berkeley.edu> wrote: P.S. I'm working on search results now for the new UI. It will be easy to add/remove/relabel/reorder the columns displayed in the search results for each record type. Look for a blog post about this in the new year. Ray On Thu, Dec 22, 2016 at 8:59 AM, Yousuf Nejati <yousuf.cspace@gmail.com> wrote: > Hey Ray, > > Thank you for the elegant and clear explanation of how a *single records > search* varies from an *all records search*. I was not aware that there > was a difference. This makes sense now. I'll add this to the questions > forum in the wiki in hopes that it helps others. > > Thanks for your help! > > -Yousuf > > > On Thu, Dec 22, 2016 at 2:03 AM, Ray Lee <rhlee@berkeley.edu> wrote: > >> Hi Yousuf, >> Have you regenerated the services layer config? This is one of those >> cases where you have to: >> >> https://wiki.collectionspace.org/display/DOC/Configuring+Col >> lectionSpace%27s+Application+Layer+-+An+Overview#Configurin >> gCollectionSpace'sApplicationLayer-AnOverview-Generateequiva >> lentServiceslayerfilesandcopyingthemtotheCollectionSpaceserver >> >> Here's why the all record types search is different than the cataloging >> records search: >> >> On the cataloging records search, the app layer makes a request to the >> REST API to the /cspace-services/collectionobjects endpoint. If you look >> at the response, you'll see the fields returned for each record: >> >> <fieldsReturned> >> csid|uri|refName|updatedAt|workflowState|objectNumber|object >> Name|title|responsibleDepartment >> </fieldsReturned> >> >> The app layer/UI layer maps the desired fields into the number and >> summary columns. The services layer doesn't care which ones they are. >> That's the case for search on any single record type. >> >> On the all record types search, the app layer is not making separate >> requests to the REST API for each record type. It's making a request to a >> special "all records" endpoint, which is /cspace-services/servicegroups/common/items. >> If you look at that response, you'll see these fields returned for each >> record: >> >> <fieldsReturned> >> csid|uri|updatedAt|workflowState|refName|docName|docNumber|docType >> </fieldsReturned> >> >> In this case, you're searching across records with different schemas, so >> the services layer can only return fields that it knows are common to all >> record types (basically stuff in collectionspace_core), with two >> exceptions: the docNumber and docName fields (also referred to as >> meta-number and meta-name) are configured for each record type, so the >> services layer knows which fields in each record type to map to them. This >> configuration is generated from the app layer configuration, depending on >> what you've specified as mini="number" and mini="summary". So for all >> records search, you need to regenerate the services layer config when >> you've changed mini="number" and mini="summary". >> >> Ray >> >> >> >> On Wed, Dec 21, 2016 at 3:52 PM, Yousuf Nejati <yousuf.cspace@gmail.com> >> wrote: >> >>> Hi all, >>> >>> In the App layer configuration files (https://wiki.collectionspace. >>> org/display/DOC/Default+configuration+files+in+the+Application+layer), >>> what field and corresponding parameter dictates what populates the >>> 'summary' field in *Find & Edit > All Record Types* only search? >>> >>> Currently, a *Find & Edit > Cataloging Record* summary field is >>> correctly populated after modifying the 'mini' attribute, however, this is >>> NOT the case for *Find & Edit > All Record Types*. Why is this? >>> >>> https://wiki.collectionspace.org/display/DOC/How+to+change+t >>> he+columns+in+the+search+results >>> >>> https://wiki.collectionspace.org/display/collectionspace/Summary+Fields >>> >>> Thanks, >>> >>> Yousuf >>> >>> >>> >>> _______________________________________________ >>> 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