Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

specifing multiple xPath queries for a single field by separating them with a comma breaks xpath expressions that include a comma. #3

Open
adamshire123 opened this issue Aug 15, 2023 · 1 comment

Comments

@adamshire123
Copy link

adamshire123 commented Aug 15, 2023

local marcSets = Utility.StringSplit(',', target.Value );

Specifing multiple xPath queries for a single field by separating them with a comma makes it so that xpath expressions that include a comma cannot be used.

An expression like this //datafield[@tag='035'][subfield[text()[contains(.,'(OCoLC)')]]][1] won't work because of the comma in the contains function

It is already possible to use xpath syntax to specify multiple xpath queries for a single field, like this
//datafield[@tag='100' or @tag='110' or @tag='111']/subfield[@code='a' or @code='b']

@adamshire123 adamshire123 changed the title delimiting multiple xpath expressions with a comma prevents breaks xpath expressions that include a comma. delimiting multiple xpath expressions with a comma breaks xpath expressions that include a comma. Aug 15, 2023
@adamshire123 adamshire123 changed the title delimiting multiple xpath expressions with a comma breaks xpath expressions that include a comma. specifing multiple xPath queries for a single field by separating them with a comma breaks xpath expressions that include a comma. Aug 15, 2023
@adamshire123
Copy link
Author

see this commit MITLibraries/AlmaPrimoVECatalogAddon@1577868

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant