Page Comparison

Randy Kuehn

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1508

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1398

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1580

1. Continue discussion

2. User expects a preference hierarchy and would like clarification & inconsistencies to be address - Agree, but needs more information

3. Needs more information

Donald Smith

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1205

Matthew Neely

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-121

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-922

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1079

1. Previously discussed and specification drawn up and attached to ticket. Recommend pass.

2. Search capability requested can be achieved via a plugin. Comments also recommend that user-defined fields (which would need to searched via a plugin) be included in Solr indexed fields as a configuration option for core ASpace code.

3. Ticket requesting display of ARKs in records. Cited as best practice to have ARKS displayed and currently not in ASpace. Agree and user-defined fields might be an option but would require every institution to configure this. Recommend drawing up a specification for this.

Keli Schmid

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1285

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1640

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1635

Matt Strauss

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1527

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1599

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1610

Tom Steele

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1645

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1600

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1647

Daniel Michelson

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1641

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1632

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1486

1. I think this ticket is saying that if you can’t merge the controlled values for subject sources if doing so will create duplicate subjects (because the subject source is part of the check for duplicates). I’m not sure that’s really a bug, since it makes sense to me that it works that way. I’m not sure how it might be improved other than doing something like having the source merge trigger merging of conflicting subject records (which sounds like a really bad idea).

2. This ticket wants the ability to include additional descriptive metadata elements to the bulk digital object importer. We’d previously been unwilling to make changes to the abilities to add descriptive metadata to digital objects, due to the question of whether such data should even be part of the digital object schema. With the recent community meeting on digital objects, are we at the point where we can make a decision?

3. This ticket is a little confusing. I think it’s basically just asking for the ability to bulk edit the File URI field in the file version subrecord in digital objects. I’ve asked the submitter to clarify on the ticket.