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

Matthew Neely

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

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

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

1. This ticket is requesting a spreadsheet import or RDE function to create container profiles. Agree this would be very helpful and save a great deal of time. Suggest this needs a specification and then community development? Ticket is also requesting this for locations but batch location creation functionality already exists in the SUI and CSV import available from ASpace 3.0 onwards.

2. This ticket is requesting a CSV import function to bulk update top containers and locations across multiple resources. Agree this would be highly useful. Suggest requesting a specification.

3. This ticket is requesting an update to the Top Container CSV import template so that locations can also be imported and associated with resource and accession records. Recommend this is useful functionality and pass this.

Keli Schmid

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

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

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

1. This should move forward with… medium? priority. It is not critical to the functionality of ASpace, but would make a world of difference and would be extremely beneficial

2. Absolutely. This is not just a staff issue and is not limited to identifier searches. Even when the sort by relevancy option is selected, the most relevant search results are often far down on the results page. Again, not a critical fix, but would produce a “works as expected” result

3. Agreed - location search results do not appear according to relevancy, but rather are in alpha/numerical order. Sometimes the desired location does not appear at all. Adding a [space] after the search term narrows down the search results, but they are still displayed in alpha/numerical order. It seems the majority of users expect their search results to display according to relevance

Matt Strauss

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

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

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

1.Ticket previously discussed at September meeting.  Requester has subsequently provided more details about their use case.  They are using classifications for different collecting areas (i.e. college archives, Quaker collections, etc.) and would like users to be able to limit their search within a classification.  Repositories can be searched in this manner. This feature ability could also be useful to other organizations using classifications in this way.  I’d recommend passing, but with perhaps low priority.

2. Requester would like an email to be automatically sent to the staff member identified in the “who needs to review” field in an assessment record.  Seems like a very specific use case. Simplest option would be for the user’s organization to outline this workflow in their local documentation.  Assuming there aren’t a ton of other users interested in a feature like this, I’d recommend looking into a plug-in or community development if possible.

Althea Topek

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

Tom Steele

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

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

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

Daniel Michelson

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

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

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

1. This ticket wants the collection organization sidebar to include “container information (i.e. box & folder number; accession number, etc.).” Since the purpose of the sidebar is for navigation, it is intentionally sparse in what it displays. Further, it’s not clear what is meant by “container information”, since accession number is not part of the data model for top containers. In sum, this is a request for something that is specific to as single implementation and I suggest closing it and recommending they pursue a plugin if this feature is desirable.

2. The bulk import spreadsheet does not require an exact match of top container information, which can result in incorrect matches under certain circumstances. I recommend passing for development to have the import only match with a top container if the container type and container indicator field in the spreadsheet is an exact match.

3. Ampersands aren’t escaped during EAD export if it is within content with embedded <p> tags. This was clearly done intentionally based on the comments in the linked code, but I’m not clear on why that would be the case.