Julia: Limit RDE: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-522 |
---|
|
Archival Objects advancing bug Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-736 |
---|
|
Physical Storage info in Resource tree? Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-301 |
---|
|
Alicia: Losing Items when Editing Ordered Lists https://archivesspace.atlassian.net/browse/ANW-635 Date string https://archivesspace.atlassian.net/browse/ANW-172 Keyboard shortcuts: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-539 |
---|
|
Search the collection in all views of PUI: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-682 |
---|
|
William: Is this already done? PUI Values vs Translation https://archivesspace.atlassian.net/browse/ANW-604 Finding aid status https://archivesspace.atlassian.net/browse/ANW-603 finding aid status (duplicate of earlier ticket?) Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-312 |
---|
|
Terra: Citation Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-288 |
---|
|
(Recommend: identifier is still missing--move to ready for implementation?) Biog-Hist out of fold: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-297 |
---|
|
Collection Organization: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-759 |
---|
|
(Recommend: I agree it would be nice to customize those sections/components as particular institutions deem necessary. Maybe survey more users? Low prioritization) Events: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-358 |
---|
|
Events 2: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-509 |
---|
|
Maggie: Error messaging https://archivesspace.atlassian.net/browse/ANW-251 Rec: Update error messaging for invalid machine actionable dates on Conditions Governing Access and Conditions Governing Use notes to something useful, e.g. "Error: Machine actionable restriction dates must be formatted as YYYY-MM-DD." Consider adding greyed out example text below fields (as found in archival object dates sub-records) that says "YYY-MM-DD only". CUIs again Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-770 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-780 |
---|
|
Boolean technicality https://archivesspace.atlassian.net/browse/ANW-171 See all records created by particular user: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-744 |
---|
|
Edgar: RDE template bug https://archivesspace.atlassian.net/browse/ANW-278 Location logic and navigation: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-755 |
---|
|
See last used identifier Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-226 |
---|
|
Lydia: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-380 |
---|
|
Rec: Ready for Implementation. Cory (who was earlier on Dev. Pri.) already scoped out this ticket and it sound like adding adding beginning and end date expressions would help with mapping the data. However, should there be a way to configure this in case an individual repository doesn’t want to add another field for their staff? Because it’s part of aligning with national/international data structure standards, I think this is worth being part of the main code, although I am not sure how many other institutions actually are planning to use this feature (not mine). Export list of top containers: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-695 |
---|
| Rec: pass with Adrian's recs - is there currently a plugin available like this?Search terms in context Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-363 |
---|
| Next time - Rec: pass with Mark Custer's input considered as examplesPDF non-latin characters issue: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-758 |
---|
| Rec: pass. Confirmed issueData clean up of Agents and Subjects Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-795 |
---|
|
Scope and Contents heading in PUI: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-296 |
---|
| Rec: pass because it is such a common terminology in archives and used in archives research instruction.Box folder item labels: Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-466 |
---|
| Rec: even though I personally would like this feature, I think there are too many complications with potentially mapping it flexibly with the variety of label templates and personal repository preferences. I think it should be a plug in or else spit out some sort of intermediate adaptable file. |