Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

\uD83D\uDDD3 Date



https://lyrasis.zoom.us/j/89240269444?pwd=Mld5cTFSMU9aY3FuY3B2S3liQmRxUT09

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Topic / Who

Tickets

Notes

Decision

Matthew Neely

  1. ANW-1433 - Getting issue details... STATUS

  2. ANW-309 - Getting issue details... STATUS

  3. ANW-768 - Getting issue details... STATUS

  1. This ticket is requesting that the extent calculator also creates a further extent for digital objects linked to the record. I can see a practical use for this but wonder if it would duplicate extents created in resource records for digital material? Might be useful for users know that there are X number of digital objects linked to a resource record.


Daniel Michelson

  1. ANW-1260 - Getting issue details... STATUS

  2. ANW-1417 - Getting issue details... STATUS

  3. ANW-1423 - Getting issue details... STATUS

  1. Metadata Standards just issue a call for feedback on extents for the MARC importer, so I suggest moving this ticket to awaiting more information.

  2. Deaccession subrecord publishing is currently an all or nothing affair governed by a config setting. This ticket would like a publish checkbox added to the subrecord in order to selectively publish deaccession subrecords. I support this ticket, but I think the tooltip for the publish checkbox should note that it will only be published if the config option is also enabled.

  3. This ticket is asking for four additional features for the Collection Management subrecords:

    1. Implement the download CSV feature from the browse view. Since this capability is already present in most browse views, it seems like it would be straightforward to do.

    2. Enable the Collection Management subrecord on archival objects, as well as resources, accessions, and digital objects. I think this is a great idea, it makes the subrecord much more flexible.

    3. Ability to set a Collection Management subrecord as completed or inactive. This functionality already exists in more flexible manner than suggested by using the “Processing Status” field.

    4. Add a “Supplies Used” field. I don’t see any downside to adding this.


saron tran

  1. ANW-621 - Getting issue details... STATUS

  2. ANW-1462 - Getting issue details... STATUS

  3. ANW-608 - Getting issue details... STATUS

Angela White

  1. ANW-666 - Getting issue details... STATUS

  2. ANW-889 - Getting issue details... STATUS

  3. ANW-10 - Getting issue details... STATUS

  1. I recommend closing this ticket per commentary of the metadata standards subcommittee on ANW-320 - Getting issue details... STATUS .

  2. This looks like it’s been taken care of--users are able to set preferences for top container columns and indicate the default sort column. Close.

  3. This is a very old ticket that I think is mostly resolved? The new reports feature allows custom reports for classifications. Also, classifications can be assigned to digital objects, which was another issue that came up. Close.

Tom Steele

  1. ANW-1458 - Getting issue details... STATUS

  2. ANW-538 - Getting issue details... STATUS

  3. ANW-358 - Getting issue details... STATUS

Althea Topek

  1. ANW-1464 - Getting issue details... STATUS

  2. ANW-562 - Getting issue details... STATUS

  3. ANW-996 - Getting issue details... STATUS

Randy Kuehn

  1. ANW-334 - Getting issue details... STATUS

  2. ANW-309 - Getting issue details... STATUS

  3. ANW-917 - Getting issue details... STATUS

✅ Action items

  •  

⤴ Decisions

  • No labels