Hi everyone-
Apologies if this issue already came up in a previous thread that I may have missed, but I wanted to see if anyone else has noticed an issue with the interface associated with the spawning feature which basically
renders the feature unusable. The particular scenario my colleagues and I have encountered is trying to spawn an archival object from an accession record. The issue seems to perhaps relate to indexing within the application. Princeton is currently using version
4.2 though we’ve noticed similar issues in previous versions as well with the spawning interface and with indexing within the application generally.
When searching for a collection using its title or call number, the correct collection typically does not appear in the search results. It’s somewhat difficult to see from this screenshot, but a search for C1771 (Princeton University Library Collection of Single
Item Acquisitions) does not yield a successful result.

Selecting the Next Page of the search results just brings the user to an alphabetical listing of all collections; the initial list of results disappears. Also, the column headings switch around and data within those columns switches/ changes/ displays the wrong information.


Trying to select one of the filters from the Select dropdown menu yields an error page.

Any thoughts or suggestions about this issue would be greatly appreciated. Princeton staff use the spawning feature regularly.
Thanks,
Faith Charlton
Faith Charlton (she/her)
Lead Processing Archivist, Special Collections Firestone
Princeton University Library
Hi Valerie-
Using quotes for the call number doesn’t appear to be effective, but in trying the search again, using quotes with the collection title did work. Thanks!
Best,
Faith
Jaime L. Margalotti
(she/her/hers)
Associate Librarian / Archival Metadata Librarian
Special Collections and Museums
University of Delaware Library, Museums & Press
181 South College Ave.
Newark, DE 19717