You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Treatment of special signs in title and signature has to be re-evaluatedand corrected. For example there are problems if the signature contains slashes "/"
The text was updated successfully, but these errors were encountered:
Lots of problems with characters that would need speacial treatment and elaborate escape mechanisms when used for filenames.
Just to list a few notable problem chars:
Already mentioned: / is a problem, because it's a path separator in unix.
Actually, everything beyond 7-bit-ascii gets blown up to its html representation. Used as part of a filename this doesn't look particularly nice. See both examples below for illustration.
Depending on local configuration, sublibraries or their circulation desks might have excessively long names, blowing up the filename to unwieldy proportions. At least in our case, the naming of sublibraries and their circulation desks was not done with the restrictions of pathnames in mind, see No. 2 below for a particularly cumbersome example.
Examples of filenames that have been particularly ugly or failed for obvious reasons:
So our solution to this was to add a bunch of replacement rules to the filtering script to catch the worst of these offenders. These rules are quite specific to our configuration, since they have the added task of shortening the lengthy descriptions as well.
We've already switched to using barcodes instead of signatures, since these have proved too much of a headache to escape around - some examples from the call_number fields of recent resource requests:
Zp 6657:2:'10':F8
5/2265 - 3,1'a'.2'a'
SA/EU 422 B466 B623 B4(3)
GB 3024 B432(3)+2
SOA/EF 34112 Å165 Å466(.003) ( Å expands to Å, the call_number field however displays it as shown in this example)
Tatjana Heuser (Universitätsbibliothek der Humboldt-Universität zu Berlin)
Treatment of special signs in title and signature has to be re-evaluatedand corrected. For example there are problems if the signature contains slashes "/"
The text was updated successfully, but these errors were encountered: