Topic / Who | Tickets | Notes | Decision |
---|
Keli Schmid | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-436 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1427 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-31 |
---|
|
| Aside from accidental deletion when selecting multiple events, I don’t see a reason this request shouldn’t move forward. Perhaps though, the problem lies more with why erroneous events are being created rather than how they can easily be deleted. It sounds like Benn Joseph has identified the issue (see comment on August 22, 2022 at 12:45 PM). Certain UTF-8 diacritics are not accepted by the import mechanism, even though those UTF-8 diacritics were generated by a database query. However, I am not sure he and Trevor Thornton (March 11, 2022) are experiencing the same problem. It does seem to warrant further testing. I’m not sure the Repository Profile report (as suggested) would fulfill the original request of Chris Fitzpatrick, but both reports seem useful.
| |
Randy Kuehn | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1508 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1398 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1580 |
---|
|
| Close Complete (see Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1396 |
---|
| )
| Continue discussion
|
|
Matt Strauss | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1592 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1591 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1509 |
---|
|
| 1.Workaround: increase the amount of search results that will display by modifying the config file. That said, the ability to increase the search results to different predefined amounts (30, 50, 100, etc.) directly from the staff interface would be useful. 2. Issue seems to be resolved with the updated Bulk Import AO XLSX available through ArchivesSpace 3.3.0 3. Replicated - pass | |
Althea Topek | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1589 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1582 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1203 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1055 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1285 |
---|
|
| Can the hover text move up or down? Could not replicate Replicated - pass From Usability - questions: Can the filing title note take the place of the finding aid title (stated in comment from June 2022)? Is it possible to add “publish” options for each element? What fields can be modified in the XSLT stylesheet (staff HTML export)?
From Usability - pass
| |
Tom Steele | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1607 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1609 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1619 |
---|
|
|
| |
Daniel Michelson | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-380 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1543 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1614 |
---|
|
| This ticket wants to split the existing date expression field into a date begin expression and a date end expression following the model of agent records, with existing data parsed as was done in the agent record implementation. I’m not clear how that parsing was previously done. It’s also not clear to me how useful having more ways to break out dates in a way that isn’t machine-actionable really is, but that is supported by EAD3, so I don’t object to passing this. I do recommend lowering the priority to minor and explicitly stating that this ticket should not be completed until more important date related tickets (specifically ANW-1475 and ANW-1273) are complete so that we continue to encourage people to use machine-actionable dates over date expressions.
| |
Matthew Neely | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1496 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1562 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1622 |
---|
|
|
| |