Filtering on location

[kzarft]

Is there any way we can limit on location like we can in iLink Advanced search? For example we often want to limit our search to items in our Juvenile or Easy Reading collections.

[ghost]

We should talk about how this will work. There are two issues I see with using that as a facet, as I see it:

1) The name "location" is likely to be confusing, given that we already have an "institution" and a "library" facet. We could name this facet "collection" or something. 2) The data in that field is not particularly user-friendly and contains a lot of staff-facing information ("Being repaired") and some of it is outright confusing ("Floor 1", "Floor 2", etc). It's also a very long list of values. Is there some other way we could present just the information we want to present? I.e. would it make sense to create a "collection" facet with just the collections users will be interested in?

[kzarft]

1. Yes sometimes the Location is “On Shelf” and if the item is out, it is “Checked Out”. Ebooks have the location “Internet”. It is a mix of collections and statuses like Hold, Lost, In Process, etc. Maybe Item Location or just Collection would work?
2. That might work as well if can determine which ones are likely to be used. We could definitely drop the Missing, Lost, etc. that are shadowed.

[ghost]

Sam will get the master list of "locations" from Elaine and this group will determine which entries can/should be exposed as "collections". Sam will build this in as a facet and then we can make sure it's working as expected.

[ghost]

Talk to Cataloguing about whether this list is built off home or current location. What problems are caused by this one way or the other.

[ghost]

There may be another problem with this idea. If the collection is built using item-level data, then this isn't indexed, so we can't build a facet on it. I'm not sure what the options are in that case, but I need to talk to Cataloguing some more.

[ghost]

It looks like this might be possible to do with the 590 field, but I'm not 100% positive. I'll have to investigate some more.

[ghost]

This will be completed for September/public launch, but we're OK with the staff launch for now. The workaround is to do a phrase search for a collection name (assuming the location name is also included in a 590 note field).

[kzarft]

@redlibrarian Here are a few of the cat keys from titles in our Easy Reading Collection: 7185824 7185832 6236524 6235473 6783608 5270112 Let me know if you need any more examples. I could pull some from our Juvenile collection as well.

[ghost]

Thanks @kzarft - I looked at the MARC record and the status (EASY_READ) shows up in the 926 field, which according to LOC is for local use. I'll check with our cataloguers, but maybe the 926 is a field I can use to build this facet. Thanks.

[ghost]

I've added 926l to the indexing for solr (that's in UAL's discovery repo). Once it's in there, we can look at the collection facet - I think it might need some data cleanup, but at least we'll have something to work with.

[ghost]

Due to our indexing procedures, the 926l solution isn't realistically going to get finished before I go on leave. The DI developers are working on the potential 590 field solution (as part of the UAL Discovery work), so that's probably the best bet, but I'm not sure when that's going to be accomplished. I'm going to move this issue out of the current milestone.

[ghost]

After the discussion the other day, and Sandra's reminder that the 926 isn't a good/stable field to use for this information, I think we're back to the drawing board. It's something @seanluyk can think about and maybe kick around with cataloguing and the symphony team to see what the best solution is. / @kzarft

[kzarft]

@redlibrarian Okay, I will follow up with @seanluyk later. Did Sandra say why the 926 isn't a good/stable field?

[ghost]

Something about how that field is populated when new records are ordered or created, but never updated. We can ask her over email.

[seanluyk]

Adding another use case from RDC. They use call numbers to limit items in their makerspace, e.g. http://www.library.ualberta.ca/permalink/opac/8228100/WUAARCHIVE

Since a starting with search is not possible in BL, this is another thing that could be achieved if we could filter by location

[seanluyk]

Spike for next sprint