This bug seams related to `bugfest_q3.1.2019` - and I can not reproduce it in the current version of Bugfest - https://bugfest.folio.ebsco.com/

The resource type 'omappad, odefinerad' does not exist in Bugfest Q1 2020 version, so then I did the combination: Language: English, Resource type: Other. All works fine.

https://bugfest.folio.ebsco.com/inventory/view/64cc438d-f2a2-4ff8-94ed-5d4d55b2cb85?filters=language.eng%2Cresource.9228e131-9711-4c3f-82e7-6c5a31ae1356&sort=Title

Open

I'll close the ticket.

Fix should be the same as https://folio-org.atlassian.net/browse/UIU-1596#icft=UIU-1596

I see you sorted it out without me.

The key solution sure makes sense to me. Code for End-user-display and key for the technical stuff.

Sorry, I think the cut-and-paste from the RFC was unclear. Pipe is not unreserved and never has been. The original unreserved characters are

and the current unreserved characters are

Note that the comma was never technically available. It works fine because we're exploiting a loophole, not because it's a legit option. If we can tolerate percent-encoding the URL, then we can use essentially anything we want, but if we want clean looking URLs I strongly recommend sticking to these lists with preference to the latter. Also, it would be fine to use a multi-character delimiter, e.g !! or ___, if we are concerned about individual characters showing up in the values.

Finally, what about using the key attribute instead of the name attribute and restricting the value to letters and numbers?

Hi @Khalilah Gambrell and @Zak Burke - I think we can use pipe – but please note that | sometimes is used as MARCtag subfield delimiter - so this might give us a value problem when we later have MARCcat in the FOLIO environment:

Open