having leading/trailing whitespace causes problems in some functions of app ( imports, for example).
Let's remove those and make sure they never have them .
This is a huge issue for me. Whether by human error in data entry or by copying and pasting existing inventories, these extra spaces happen and it would be GREAT to have an automated way to clean up the data. Attached is a screen shot of a finding aid a student cut-and-pasted from an HTML legacy inventory. Note the weird box that is created because of that empty space. When doing data clean up in ead/xml files, the equivalent script would be Find " </unittitle>
Replace "</unittitle>" I don't want to have to do this with all 700 collections we have!
- this issue is specifically for removing leading/trailing whitespace from entries in controlled value lists (helper lists like extent type or agent relator). I'm just curious if what's in the screenshot above is from a list like that or something else. It sounds like you're talking about folder titles/other entries in an inventory, which wouldn't be helped by fixing this issue as described.
Certainly the function that can remove whitespace from a string (text) in a controlled value list could also be applied elsewhere in the code for other kinds of strings (text). There are some things built into ArchivesSpace's importers to remove this kind of thing from titles - but perhaps not when they're created in ArchivesSpace.
Thanks for the clarification. This screenshot is from a student data entry project where they were copying-and-pasting text from another document into ArchivesSpace. Whether it's copying-and-pasting or keying in data, it just seems to be a human habit to continue a title with a space and I constantly have to remind our student, volunteers, and sometimes staff about this issue which happens ALL THE TIME. It would be amazing if there was a way to automatically eliminate trailing whitesspace for titles (in all levels of hierarchy), as long as it is possible to override the autocorrect if the title - for some reason - calls for that extra space.
What would be the best way to pursue this idea? Should I create a new JIRA or bring this to SIEWG? Thanks!
Definitely create a new JIRA for it. If you think you still have time to discuss in SIEWG before issuing the final recommendations, that would be one way to start an initial discussion of priority. If not, it will go in the regular queue for consideration.