Normalize LC control numbers (024 in authorities)

[jenniferward]

Maybe a minor point but I keep finding instances like this. Some LC control numbers have spaces: n 87114605. If you copy and paste an LC control number from the LC authorities page into Muscat, the space is changed to a % when the link resolves:
https://muscat.rism.info/admin/works/37437
https://lccn.loc.gov/n%2087114605

But this is not the same URL as given by the LC Authorities page:
https://lccn.loc.gov/n87114605

They have a routine for normalizing: https://lccn.loc.gov/lccnperm-faq.html

How does LCCN Permalink work?
LCCN Permalinks are constructed using the following syntax:
https://lccn.loc.gov/ followed by the normalized LCCN
Examples: https://lccn.loc.gov/2003556443 or https://lccn.loc.gov/n79018774

and then a whole table of normalizing that has to be done (under How does LCCN Permalink normalize LCCNs?).

Should we normalize the LC control numbers in Muscat?

[xhero]

There is no way to automatically normalise a field when saving in Muscat. What I can do is make a regex that will fail validation if there is a n followed by a space, so the user can correct it by hand. To fix the ones already there (remove the space after the n) we can make a small script.