...
Topic / Who | Tickets | Notes | Decision | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Matthew Neely / All | Welcome | Dev Pri will be leading discussion at November UAC meeting | |||||||||||||||||
| In the interest of accessibility, I recommend passing this request. It seems straightforward and appears to be the last contrast edit needed in the ASpace interface | ||||||||||||||||||
| Tried to replicate a few times in 3.4.1 and the calculate extents function does not appear to be generating any blank sub records as it did for users in 3.4.0. Suggest reaching out to see if an instance update has resolved their issue. | ||||||||||||||||||
| Ticket reporting that CSV exports from search results are not exporting all data in column results, specifically identifiers for subjects. Also diacritics not exporting correctly. Succesfully replicated this in the 3.4 test instance. Identifier issue seems to work fine for archival objects and is limited to subjects. Suggest passing but this might be fixed by
| ||||||||||||||||||
| Feature calls for a loosening of controls on embedding EAD XML in note fields. Doing so could speed data entry for advanced users, but the application might be unable to validate the XML due to the differences in in-line encoding practice between EAD 2002 and EAD3. This may also present challenges for users unfamiliar with EAD tagging. Recommend gathering more information about alternative approaches, such as importing XML snippets or CSV files into the various list subrecords in Resource record notes. | ||||||||||||||||||
| This seems pretty straightforward. When in edit mode on an accession record, there is not a “close record” button like there is on resource records or digital objects. Without a “close record” button, users would have to either click the back button or click the accession title in the breadcrumbs. Recommend passing. | ||||||||||||||||||
| |||||||||||||||||||
| |||||||||||||||||||
| Tested with a few records, found that only some fields had the error. 245 field and 650 field were fine, 524 had the error. further testing recommended, pass. | ||||||||||||||||||
| Confirmed behavior in latest AS version. Recommend passing. |
...