Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Very confusing ticket but I think I figured out what they are talking about and reproduced a failed merge in the Subject Source controlled value list (latest version sandbox). Agree better error messaging would be useful.
Tested, verified that I cannot get a <emph>tag to render properly when nested within a title tag. Nesting is possible using only the <emph> tags, but breaks when enclosing a title. Tested in 3.3.1 and newest version in sandbox
Tested on sandbox and confirmed reported behavior. The steps followed in the ticket match how the endpoint is documented, so the endpoint as-is is nonfunctional.
Tested and confirmed that this occurs. Running the search starts what looks like an infinite redirect loop. Recommend passing, since this crashes the browser.
Recommend Pass
Recommend Pass. Could replicate on numerous browsers (but not Firefox).
CSV currently defaults with an example that uses “indirect”. The proposed fix will work. Just to confirm we want to use the keys, not the translations for CSV imports?
This ticket comes out of discussing https://archivesspace.atlassian.net/browse/ANW-939 - The issue as stated there assumes that ordering of resources within a classification works similarly to general search or browse results; however, resources within a classification work more similarly to AOs within a resource – i.e. the order is intentional – so adding a sorting option in the PUI would require a reimagining of how classifications work. This new ticket describes an issue where the order of resources determined in the SUI is not reflected in the PUI.
I agree this would be very useful functionality. An additional case would be with rolling restrictions (e.g. 50 years after creation). Needs more discussion about how restrictions work in general - I’m not sure how this will interact with how local access restrictions flag an entire container as restricted if even only one linked object is, for instance. For this use case, where would the restriction info be stored? Can you restrict a child instance or a whole container?
Recommend pass.
Awaiting for more info. Will send out for community feedback
Confirmed bug. Seems pretty straightforward and ticket is well documented. Recommend passing.
Requestor wants the sidebar for SUI classifications to be left-side configurable like collection organization is now. I think this is a good idea for the same reasons outlined in https://archivesspace.atlassian.net/browse/ANW-769. However, it’s worth discussing if every sidebar should be configurable to be on the left, as well.
Responses were very mixed about this ticket. The responses I got skewed positive towards adding extents to browse/search results. Many folks requested this be configurable if we pass it for development.
Recommend passing.
Recommend passing. Let’s extend the ticket to all side bars.
Recommend pass. Good feedback, most in favor, but will make sure it’s configurable.