search

ycba-cia / blacklight-collections2

5 stars 2 forks source link

Vend On-site Access facet values to LUX PoC #264

Closed edgartdata closed 1 year ago

edgartdata commented 4 years ago

This issue is related to https://github.com/ycba-cia/blacklight-collections2/issues/218 Come up with a brief definition of the values in the On-site Access facet that would be visible on hover over.

edgartdata commented 4 years ago

@EdwardTown1 @flapka Just checking that for P&D objects, in the LIDO XML we want to replace Not on View with Accessible by request in the Study Room? If yes, then only objects in storage will have the Not on View access status. If not, the LIDO schema can accommodate for multiple access values.

flapka commented 4 years ago

@edgartdata Yes, that sounds right to me. If, for P&D objects, you were to vend both values to the LIDO xml, is it possible to associate type attributes, e.g. "Not on view" has type "gallery" and "Accessible by ..." has type "studyRoom"?

edgartdata commented 4 years ago

@flapka I checked and LIDO validates when there are multiple values for this element

LIDO also accommodate for attribute types:

Not on view Accessible by request in the Study Room @EdwardTown1 @mxgold Can we please discuss tomorrow to double check if we want this double on-site access status for P&D and RBMS items. Would it be confusing/not helpful to have these objects under 2 facet values? Also, I like the idea of aligning more with LUX on access and usage but maybe we can tighten our language?
yulgit1 commented 4 years ago

current LIDO->solr indexing logic for reference:

Screen Shot 2020-09-24 at 2 32 26 PM

edgartdata commented 4 years ago

Currently P&D items only get the status "Accessible by request in the Study Room" when they are in the Study Room. When they are in the public galleries they get "On view".

@edgartdata to work with David on adding the status "Not on view" to P&D objects either in the public galleries, in storage or on loan outside of the YCBA building.

@edgartdata @flapka @BaylaArietta Instead of the label Gallery and Study Room (as in Not on view/On view; and lido:label="Study room">Accessible by request in the Study Room), would it be helpful to use the lido label Location for "Not on view/On view" and Access for "Accessible by request in the Study Room"?

yulgit1 commented 4 years ago

@edgartdata To be clear as I'm not sure where your going with this. LIDO currently has either "on view" or "not on view". The code snippet above translates these depending on each collection to what appears as facet values.

I guess my question is for PD objects in the public galleries, in storage or on loan outside of the YCBA building, you're saying these should be "not on view". But what are they currently?

edgartdata commented 4 years ago

@yulgit1 I am interesting in replacing your logic above that generates the transformation of "P&D item not on view" into "Accessible by request in the Study Room" by having a LIDO element for these objects that explicitly says "Accessible by request in the Study Room" (in addition to a LIDO element for "Not on view").

The use case is three-fold:

  1. I want to map "[P&D object] Accessible by request in the Study Room" to the "by appointment" value in the LUX Access in Repository facet.
  2. Make this additional access value of "[P&D object] Accessible by request in the Study Room" available to services that harvest our LIDO
  3. With the logic worked out before BL, hopefully you don't have to maintain the script above (instead BL would map to this additional LIDO element)

For info, right now the values in the LUX facet are:

To your last question @yulgit1:

@yulgit1 I hope this makes more sense now? Any concerns about any of this?

yulgit1 commented 4 years ago

Makes sense. LIDO=BL=LUX globally in terms of the controlled vocab:

On View Not On View Accessible by request in the Study Room Accessible in the Reference Library Accessible by appointment in the Study Room

Correct?