Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Who

Item

Notes

Decision

Announcements/Questions/Old Business?

Move this to Closed? Lora Woodford

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-422

ANW-422 can be closed!

Laney/Lora

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-834


Not sure this is ASpace thing as opposed to a local thing. Laney will follow-up with Blake.

Status: Awaiting More Info.

Laney/Lora

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-277

Will clarify that it's a manual message that can be set and how to engage.

Status: Ready for Implementation.

Bill

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-789

Bill

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-773

Bill

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-741

Edgar

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-823

Can confirm this is still an issue I recommend we pass.

Status: Ready for Implementation.

Edgar

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-458

I recommend we pass this.

Might need a partner institution to test this with.

Edgar and Maggie will bring up during Integrations meeting and Lydia during UAC meeting. And find out what has been done – individual institutions are doing this. Can we find partners to work on this plugin? Could Edgar and NW help out?

Status: Awaiting More Info.

Edgar

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-606

I recommend we continue to wait for more information. I have pinged the submitter on the ticket.

Ticket is old and likely that some issues here have been fixed. Reporter not responsive. “Closing this ticket but please let us know if this issue still persists.”

Status: Close.

Lydia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-671

Of course, as the submitter of this ticket, I like these ideas - what do you all think? :)

#1: Chevrons sound ok. #2: “Results” sound good, but is in the yaml and easy to customize #3: needs more detail/a decision on how to sort. Also needs more investigation on tech difficulty.

Split into separate tickets and revisit.

Lydia

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-345

[It seems like the ASpace sandbox is slow today]

Can replicate. Why is selecting an extent type only allowable? Perhaps this should be updated so that the two of them are required together and update the tooltip to say so?

Also, if there is an error in saving, the error message is off the visible screen. It would be helpful if any error message (or at least something indicating that there is an error) is displayed within the screen view.

Rec: Pass

SkipTrivial priority.

Rec: Ready for Implementation.

Lydia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-791

There’s currently a way to sort Collection Management by processing status. CMs could be applied to Accessions, Resources, etc much more specifically, so I think we should CLOSE this ticket.

Functionality is already there.

Rec: Close.

Alicia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-555

Alicia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-281

Alicia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-426

Maggie

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-736

Could not replicate. Is linked to ANW-608 and some comments suggest that there may be a few different but related issues going on with reordering.

Q for Lora: Does this ticket have enough info? Should we solicit more feedback from the listserv?

Rec: pass (given the thorough descriptions of the issue which specifically mention that it is difficult to replicate.)

More details are how users are seeing it in their specific environments. Very slippery, looking for points of commonality.

Maggie will post message to listserv.

Status: Ready for Implementation.

Maggie

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-161

Didn’t get to this one, sorry! Next time

Maggie

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-691

Tested and confirmed – added note to ticket.

Q: Do we expect that we should be able to search for a full identifier string using a hyphen between id components? Or period, space, no space?

Red: pass, however it seems a decision might need to be made about how to search for multi-part ids (if possible several ways should work as in keyword searching)

Typeahead would expect it to find it whether it has a hyphen, period, space, or no space between components.

Status: Ready for Implementation.

Terra

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-824

Is exporting in EAD in sandbox, but does not show a Note heading on PUI. example: http://test.archivesspace.org/repositories/2/resources/276

Rec: Pass update for PUI issue

Related to ANW-344.

Status: Ready for Implementation.

Terra

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-446

Repository details are there, but not header/footer option. Can this be done locally?

Rec: Repository details are on each collection--if header/footer can be added by institution, I recommend closing ticket.

Similar to recent ticket about adding contact link in a page footer. Can be done locally.

Status: Close.

Terra

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-453

Not sure about this one!

Q: What are the things that separate the id components? Should be able to do this through the API.

Add an option on the importer/background jobs to specify under condition under which to break up id strings: “Break up my ids by [insert character].”

Status: Ready for Implementation.

Julia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-621

Julia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-620

Julia

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-341

Patrick

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-557

Need more contextual information about what would "look better".

Also need clarity on on the "add into the Edit Basic Information the Resource or Accession number and links back to the component". Do they just want links back to the linked resource/accession?

Patrick

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-814

Patrick

Jira Legacy
serverSystem JIRA
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-819

...