...
Who | Item | Notes | Decision | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Announcements/Questions? |
| ||||||||||||||||||||
Terra |
| Would be a helpful feature but not necessarily high prioritization. | Awaiting more info - will link to ticket re: having the updates to the controlled values in the SUI also update the YML file, which it currently doesn’t (
| ||||||||||||||||||
Terra |
| field desc: A code compliant with ISO/DIS 15511 Information and Documentation International Standard Identifier for Libraries and Related Organizations (ISIL). For United States institutions, this includes codes from the MARC Organization Code list. I agree with Lora’s comment, more context is needed on how to use the current Org/Agency Code field. Pass | Awaiting more info Needs clarification on how it should be used, especially to prioritize in cases when both fields are provided. Will tag Sue Luftshein and Cory Nimer for their input on MARC | ||||||||||||||||||
Terra |
| Contact info is included in Repository Details. Low prioritization | Close - Will not do The labels can be customized per repository, possibly changing “Repository Detail” to “Contact” or other. | ||||||||||||||||||
Maggie |
| Duplicated bug in test instance: http://test.archivesspace.org/staff/top_containers/10287 | pass | ||||||||||||||||||
Maggie |
[Revisiting from last time - there was some confusion about it (Notes: Patrick Galligan (Unlicensed)suggest that this is a bug and not shouldn’t be a feature request
| Ack, my agents weren’t published last time! Uploaded new screenshot on ticket. Rec: Pass. Think it does make more sense for Agents-as-Subjects to appear in Related Names section, as described in ticket. PUI: http://test.archivesspace.org/repositories/2/resources/345 | Awaiting More Info Will reach out to Sue and Cory again. | ||||||||||||||||||
Maggie |
| Seems reasonable, especially since the temporary location controlled value list is configurable. However not sure it is necessary to require the type of temp location specified. Q: If we change this now, what happens to instances that have temp locations without a specified type? Thoughts from others? Related issue: When I created a location indicated "temporary", the temporary checkbox status inconsistently holds when opened the location again (link to video). Mentioned in ANW-755 Temporary Location logic and navigation confusing (also agree with Lydia in renaming the second “Temporary” field to function/temporary type/etc.) | Closed - will not do Maggie will pursue creating the other tickets | ||||||||||||||||||
Julia |
| ||||||||||||||||||||
Julia |
| ||||||||||||||||||||
Julia |
| ||||||||||||||||||||
Bill |
| ||||||||||||||||||||
Bill |
| ||||||||||||||||||||
Bill |
| ||||||||||||||||||||
Lora/Laney |
| Awaiting More Info Any additional feedback beyond Lora’s comments to add? | |||||||||||||||||||
Laney/Lora |
| Keep in Awaiting More Info and wait for more activity on the ticket. | |||||||||||||||||||
Lydia |
| [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 | |||||||||||||||||||
Lydia |
| Seeking community feedback about whether this is a good move. Obviously importing dummy dates isn’t good, but neither is not having good documentation on collections. Thoughts? | Pass and ping Alicia for updating tech docs | ||||||||||||||||||
Lydia |
| Seeking feedback, especially from Laney McGlohon (Unlicensed) Lora Woodford about mapping since this is shoehorning it from a different field. “Undated” would be nice to avoid typos/save time but some repositories may prefer to use “not dated” or “unknown.” If there could be a controlled vocab, perhaps it should be repository configurable and drop down from the date expression field? Seeking more info/feedback. I think we need more information on this one - stuff like how it would be mapped, how it works with date expression, and how any migration would work | Close it because it’s messing with a data field and because of different repository preference in wording | ||||||||||||||||||
Alicia |
| Confirmed this is still an issue in 2.5.2. Seems like logical, desired behavior. Rec: pass | Pass - low priority | ||||||||||||||||||
Alicia |
| The screenshot for this ticket shows that the HTML <a> tag is being used to encode the URL, but (I think) only EAD markup is accepted in note fields (<extref> or <ref> for URLs - though extref is deprecated in EAD3 so should use ref). Confirmed that both ref and extref work as expected in 2.4.x. So is this a problem? Rec: close | close | ||||||||||||||||||
Alicia |
| The default ‘admin’ user can view system info, including logs, but users with admin privileges cannot. I would expect that a user with admin privileges should be able to see system logs and other info, but some institutions may allocate privileges differently than others and would not want this behavior. Perhaps make the ability to view system info an option in Manage Groups or Manage Users menus? Rec: pass with suggested changes | Pass with Alicia’s recs | ||||||||||||||||||
Patrick |
| Was not able to duplicate on test.archivesspace.org using : http://test.archivesspace.org/staff/resources/45#tree::resource_45 Could use more information about specifics to trigger action. | Close | ||||||||||||||||||
Patrick |
| Changing defaults seems to make sense to me as the image does look like a broken link. Should be a fairly easy switch to have a different default image. | Close | ||||||||||||||||||
Patrick |
| 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? | |||||||||||||||||||
Edgar |
| I have confirmed that 700 field is placed first as Creator while 110 field is second. 7xx are Contributors not Creators. 1xx are Creators. http://test.archivesspace.org/staff/jobs/2153 Rec: Pass | Pass | ||||||||||||||||||
Edgar |
| This is a strange behavior for a drop down list and adds an unnecessary extra step. Also when choosing an Agent, the behavior of that drop down is slightly different as there is a browsing feature also the X/delete is within the box and not the down arrow as with Agent Relator. Is there a known reason for the behavior or deleting the choice first? The benefit seems to be a faster way to clear out a selection. It appears that it isn’t a drop down but a complex text box with some sort of ajax autocompleter so how easy would it be to replace this with a static drown down? Rec: Probably Won’t do. | Close | ||||||||||||||||||
Edgar |
| Is this here?: https://archivesspace.github.io/archivesspace/doc/alpha_index.html If so, then this would be super helpful for developers. Rec: Pass | Pass |
Action items
Decisions
...