SDMoM asked if the createdBy and createdAt fields could be searchable in
the advanced search screen.  That seems like a reasonable request, so I
modified the application core-fields.xml to make them searchable (mirroring
the attributes in the updatedBy/updatedAt fields):

https://github.com/collectionspace/application/compare/v4.2...cherryhill:sdmom_v4.2-core-fields

...and copied the advanced search configuration for updatedBy/updatedAt,
replacing with createdBy/createdAt:

https://github.com/cherryhill/sdmom-tenant-config/blob/c8a0b2fe7764f5068765082f9028812edafc16c3/ui/html/components/SearchFieldsTemplate-cataloging.html#L236-L264

What is happening in the UI, though, is that I'm not getting the
appropriate entries in the 'uispec' JSON (so there are no field labels and
field decorators).  I would expect to see:

     * .csc-collection-object-createdAt-label
     * .csc-collection-object-createdAtEnd
     * .csc-collection-object-createdAtEnd-label
     * .csc-collection-object-createdAtStart
     * .csc-collection-object-createdAtStart-label
     * .csc-collection-object-createdBy
     * .csc-collection-object-createdBy-label

...in the 'uispec' JSON to match the corresponding updatedAt/updatedBy
entries.  I have rebuilt/redeployed the application, service and UI WARs
and am running the browser with caching turned off.

Thoughts?  Is there something special about the core fields?

Peter

Peter Murray
Dev/Ops Lead and Project Manager, Cherry Hill Company
Blogger, Disruptive Library Technology Jester - http://dltj.org/

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

On Dec 21, 2015, at 6:43 PM, Ray Lee rhlee@berkeley.edu wrote:

Hi Peter,
We made createdAt searchable, and it looks like we did exactly what you did.

Ray

On Mon, Dec 21, 2015 at 2:51 PM, Peter Murray <jester@dltj.org mailto:jester@dltj.org> wrote:
SDMoM asked if the createdBy and createdAt fields could be searchable in the advanced search screen.  That seems like a reasonable request, so I modified the application core-fields.xml to make them searchable (mirroring the attributes in the updatedBy/updatedAt fields):

https://github.com/collectionspace/application/compare/v4.2...cherryhill:sdmom_v4.2-core-fields https://github.com/collectionspace/application/compare/v4.2...cherryhill:sdmom_v4.2-core-fields

...and copied the advanced search configuration for updatedBy/updatedAt, replacing with createdBy/createdAt:

https://github.com/cherryhill/sdmom-tenant-config/blob/c8a0b2fe7764f5068765082f9028812edafc16c3/ui/html/components/SearchFieldsTemplate-cataloging.html#L236-L264 https://github.com/cherryhill/sdmom-tenant-config/blob/c8a0b2fe7764f5068765082f9028812edafc16c3/ui/html/components/SearchFieldsTemplate-cataloging.html#L236-L264

What is happening in the UI, though, is that I'm not getting the appropriate entries in the 'uispec' JSON (so there are no field labels and field decorators).  I would expect to see:

     * .csc-collection-object-createdAt-label
     * .csc-collection-object-createdAtEnd
     * .csc-collection-object-createdAtEnd-label
     * .csc-collection-object-createdAtStart
     * .csc-collection-object-createdAtStart-label
     * .csc-collection-object-createdBy
     * .csc-collection-object-createdBy-label

...in the 'uispec' JSON to match the corresponding updatedAt/updatedBy entries.  I have rebuilt/redeployed the application, service and UI WARs and am running the browser with caching turned off.

Thoughts?  Is there something special about the core fields?

Peter