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?
Recommend Pass for uniformity
ANW-1783 - I was able to replicate the issue and seems pretty aesthetic in nature. I wonder if a possible solution would be to allow for the symbols included when the digital object is not marked “representative” to be the default unless otherwise clicked. The user suggested checking the “digital object type” as a potential solution, but this is an editable field and so wouldn’t be feasible across all instances (same with file format). As an institution that uses the digital object functionality to link to a digital repository the blank square also appears for us when we link in this way.
Recommend add “image” to Make Representative
Pass
Pass. Recommend that “Make Representative” be changed to “Representative Image”.
This is a two-part request. The first part is straightforward and has been requested in more than one ticket: On the Rapid Data Entry screen, can the add row button (green square with black X ) be moved to the left side of the screen instead of the right? Recommend passing.
The second part of the question asks for a line to be inserted (rather than adding it to the end?) when the user adds a row, but I believe this is already in place.
This ticket is alerting us to an issue where the height field of a new location profile record requires a digit to be typed before a decimal, even if that digit is 0 (0.2 rather than .2), whereas the container profile record does allow a decimal without a leading digit. To add to the confusion, the error message is inaccurate. Recommend passing to standardize the number entry format, and also to correct the error message
There are few different requests tied into this ticket about the PUI and SUI Advanced Search.
Add the inventory field to the search: field might be solved by the Extended Advanced Search plugin developed by Yale.
Ability to limit advanced search by record type: I think this achievable by using facets to narrow results.
Make the SUI Advanced Search the same as PUI Advanced Search: I’d like to hear more about the benefits of doing this and perhaps submitting a new ticket following the new template would generate this information.
I agree this is confusing. I think a warning that the box is not checked or vice versa is a good idea. Recommend passing.
Can confirm local restriction type is not importing. The reporter said that there was not an error indicating that the local restriction type did not import, but I am actually encountering what seems to be an unrelated error. I get the error “[Some system error has occurred [undefined method `title' for nil:NilClass].] when I am importing a local access restriction type with a date. The only difference between successful and unsuccessful imports is a date despite the error pointing to title. Very confusing! Recommend passing.
Previously reviewed for March 2024 Dev Pri meeting and was unable to replicate the issue. Contacted ticket creator to try and replicate their settings. Tried to replicate following update from ticket create but still not able to produce the error being reported. Contacted ticket creator to see if they could replicate in the test instance and share results.
Ticket is requesting a set default repository on login. ASpace will log you back into the previous repository if your browser history hasn’t been cleared or closed. I agree that this would be a useful feature and recommend passing with a minor priority if development is not overly complex.
Ticket is requesting more granular search options for Top Containers. Some of the issues raised in this ticket (e.g. how search works) could be resolved through updating the help pages. The Resource search has already been discussed in ANW-1197 by Dev Pri and closed. Agree that the facets for 4. Container Profile and 5. Location and 6. Combining this into the Location facet would be beneficial. 7. and 8 also agree that this is very useful. Recommend that most of the features being proposed should pass but consider whether this ticket needs to be broken down into the various aspects / consider Dev Pri editng this?
I’m very familiar with this one and prepared to talk at length about the difficulties on changing a subject to an agent or vice versa. These records are linked to multiple records and changing one means establishing all links again. I don’t know if there is a way to do this because it would mean to move all the links from the agent to the subject, or subject to agent, and establish a role for the subject being transferred to agent (probably subject as default?) More discussion needed. Another problem is what fields are kept. I made a similar ticket 4 years ago and wasn't able to answer questions about how to do it.
Confirmed that alt text does not appear in the staff user interface browse/search pages. To match the PUI view, the file version Caption field text from the digital object record might be used for this content.
Tested this on sandbox and found the same issue - the MARC included in OAI exports is incomplete. In addition to the leader and 008 fields, the 040 is also exporting as a blank node, despite having information in the non-OAI MARC. Recommend passing.
Tested on sandbox and confirmed the error. This appears to be an oversight from ASpace 3.0 development. Recommend passing.