I think this user is wanting to download agent information from the Browse → Agents page. There is a “Download CSV” option, but it downloads all agents. The checkboxes to the left of the Agent Type on the page seem to have no effect…I can’t tell what they are for.
It seems this user is first viewing all items of a singular value from System → Manage Controlled Value Lists → List Name. From there, “Filter by text” creates a new search that is not limited to the extent type previously viewed. I don’t think this is a bug; I think this is a case of the user not going about the search in the right way. Instead of first searching through the controlled value list and then filtering by text, they could perform a text search that includes their keyword and their extent type. i.e. “minidisc arto” would bring up the results they are looking for
Awaiting more information. Need to have more details about use case (is requestor looking to export the info for one agent or many. Pass along custom report method suggested by Christine as a potential solution.
Pass. Include current workaround solution in a comment. Also in a comment, indicate the expected behavior here and note that this problem might be more widespread than just the use case described in the ticket.
There is something weird happening here, though I’m still not positive what’s happening. It appears that text formatting in notes breaks when the note is not expanded. When the text is expanded, it appears as the author intended. There was discussion about similar issues with line breaks and text formatting in notes in an ArchivesSpace user groups listserv--I suggested they share their examples on the ticket. Regardless, I recommend passing for development since so many users have experienced the same or similar issue.
User wants to be able to link archival objects to accession records through the spreadsheet importer. I don’t believe the functionality exists to link to archival objects in any of the bulk import templates. My institution does not make use of the bulk accession import template, so I’d be curious to know how many people would use this functionality. If this would be a simple lift (my instinct is that it’s not), I recommend passing. If not, I recommend getting community feedback to determine how desirable it is.
Confirmed this issue. Would be a good thing to fix.
Has been awaiting more information since 2020. Pinged the requester via a comment to see if they had any additional feedback to provide. This could be a “nice to have” feature but probably not at the expense of overall performance or if it required substantial development work.
Pass
Close ticket. Implementing this would negatively affect overall performance.
Confirmed Issue and agree that this would be a needed update. Currently the Digital Object module opens in a new tab, but any external links or internal links to other collections open in the same tab which could be confusing for users. Recommend passing. Carried over from last meeting.
Added for March meeting: Brianna found a good resource from W3C school on guidelines for opening in a new tab and shared in a comment on the ticket. TLDR: best to open in same tab but if must open in new tab should have the little symbol with alt text stating that is what is happening. This symbol is already utilized within ASpace with regards to digital objects and so wouldn’t be foreign should we elect to do that. I believe that external doc and digital objects are the majority if not only examples of outside materials hyperlinked in ASpace, so it probably would be best to have those items handled uniformly?
I was unable to easily replicate this issue. It would be helpful if we could get a sample spreadsheet from the reporter that would be helpful in replicating as my attempts threw errors.
This issue was mentioned on the listserv 10/16/2023. What is the technical impact of changing API behavior? Should there be a larger community discussion about what data should and shouldn’t be made available via unauthenticated API requests?
Is there an existing, easier way to get this data? If yes, this may be a documentation issue. If no, is this easy to implement?
Awaiting more info. The ArchivesSpace team will look into this and decide how to move it forward.
Pass, but Bonnie will add concerns via a comment on the ticket.
Not able to replicate this in testing sandbox using the default values. Possible only impacting on ticket creator. Suggest asking for full list of default values to see if can replicate.
Ticket is asking for notifications for several ASpace functions and also customised reporting (this may now be satisfied by new functionality). Suggest closing this ticket and comment that each area be broken down into several tickets reflecting each feature. In principle, think requested functionality is good but ticket now 4 years old and no response / comments following review by Dev Pri in May 2021.
Awaiting more Info. Matthew will gather additional details from requestor.
Close this ticket. Dev/Pri will work on submitting individual tickets for the different features requested.
Tested, it’s true it doesnt recognize missing quotes in a URL. Pass
Tom Adams was asked for further information, yet still hasn’t answered. Randy Kuehn asked for a detailed specification. It’s been almost 3 years, recommend close. I don’t see a reason overall to always keep fields from a merged agent. could result in bad data.
This appears to be working as anticipated based on ANW-1209 requirement 4. More information may be needed from the reporter to determine what change to the current functionality is desired.