Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - Two new part attribute encumbrance actions #3536

Closed
krgomez opened this issue Mar 23, 2021 · 25 comments
Closed

Feature Request - Two new part attribute encumbrance actions #3536

krgomez opened this issue Mar 23, 2021 · 25 comments
Labels
Administrative How the community functions - these issues may be transferred to internal repos Collection Type - Cultural Collections Art, Ethnography, etc collection related Enhancement I think this would make Arctos even awesomer! Priority-High (Needed for work) High because this is causing a delay in important collection work..

Comments

@krgomez
Copy link

krgomez commented Mar 23, 2021

Describe what you're trying to accomplish
An clear and concise overview of the goals; why are you asking for this?
We need to encumber preservation need and condition report part attributes for the UAM:Art collection. As we see it, the primary reason for needing to encumber these part attributes is that without the aid of interpretation by a museum professional there is concern for misinterpretation of this data. We can find no other examples where this level of information about artworks is shared publicly online by other museums. For more context, see #1908.

Describe the solution you'd like
How might we accomplish your goals?
Create two new encumbrance actions:
mask part attribute condition report
mask part attribute preservation need

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I don't think there's any other way...

Priority
Please assign a priority-label. Unprioritized issues gets sent into a black hole of despair.
High

@krgomez krgomez added the Enhancement I think this would make Arctos even awesomer! label Mar 23, 2021
@dustymc
Copy link
Contributor

dustymc commented Mar 23, 2021

can find no other examples where this level of information

That's why we built Arctos!

concern for misinterpretation

Everything (ish, probably) that's subject to interpretation is presented as a determination rather than a fact. (And you can always blame "unknown.")

I don't think there's anything technical or wrong here so I'm not exactly objecting, but this sounds like the opposite of "research grade." If those data were out there, maybe someone would do something awesome with them. If they're not, you'll never know. Arctos has been a driver of innovation, feedback from users has been used to make Arctos better, and none of that can work if we're arbitrarily withholding data.

@dustymc dustymc added this to the Needs Discussion milestone Mar 23, 2021
@AJLinn
Copy link

AJLinn commented Mar 24, 2021

I've always been in favor of transparency in this and all data that does not infringe upon privacy concerns. I will always make my condition reports visible to the public as a way of providing full disclosure on how stable they are, especially if individuals are hoping to examine for research or request for a loan. My 2-cents.

@marecaguthrie
Copy link

marecaguthrie commented Apr 7, 2021 via email

@marecaguthrie
Copy link

marecaguthrie commented Apr 30, 2021 via email

@Jegelewicz
Copy link
Member

@dustymc any objections?

@marecaguthrie
Copy link

marecaguthrie commented Aug 16, 2021 via email

@Jegelewicz Jegelewicz added Priority-High (Needed for work) High because this is causing a delay in important collection work.. Collection Type - Cultural Collections Art, Ethnography, etc collection related labels Aug 16, 2021
@Jegelewicz
Copy link
Member

@dustymc I don't know how much work this entails, but this is important to the art collections. I think everyone who is using these part attributes has commented here.

@dustymc
Copy link
Contributor

dustymc commented Aug 16, 2021

how much work

A fair bit IIRC, plus some long-term costs (payable in CPU cycles). I'm wondering if we could just not display some list/category/something of part (and maybe other??) attributes? That's probably more work in some way, but the next similar request (which seems likely) should more than make up for that if the idea's not too out there. I don't have anything specific in mind, but it seems worth exploring.

And I'd still like some full-AWG feedback on #3536 (comment); those may not be unrelated ideas (eg, maybe we need "research" and "curatorial" attributes or something, IDK).

@Jegelewicz
Copy link
Member

I'm wondering if we could just not display some list/category/something of part (and maybe other??) attributes?

That was going to be my suggestion, but @AJLinn said:

I've always been in favor of transparency in this and all data that does not infringe upon privacy concerns. I will always make my condition reports visible to the public as a way of providing full disclosure on how stable they are, especially if individuals are hoping to examine for research or request for a loan. My 2-cents.

Which says to me she would prefer these part attributes be displayed.

I don't think any of the biological collections care about this (although they should and they should make better use of it), but I am going to take the side of transparency here. We are public institutions holding objects in the public trust. There doesn't seem to be a good reason to hide condition or preservation need from the very people who are paying/might pay for it and we should always be prepared for misinterpretation - that is half of what museums do - interpret.

I will place this on the next AWG Issues Agenda, unfortunately, we aren't getting through much each meeting. @marecaguthrie if this is really important to you, maybe you can come to the meeting to offer me an excuse to bring it up? Meeting is 2021-09-02 at 10:30 am PST.

@ewommack
Copy link

I second that @marecaguthrie! If you can come to the meeting, that would help a ton with the discussion, and you could also pull the item up to the top of the agenda for consideration. It's always really helpful to have a range of thoughts and experiences in the discussions.

@krgomez
Copy link
Author

krgomez commented Mar 12, 2022

I am not sure when the next AWG meeting is, but I think Mareca can look into attending to discuss this issue. She did contact the collections stewardship listserv to gather thoughts from the museum community on this, with some helpful perspectives gleaned. I know this needs more discussion, but in the meantime I have a practical question.

We created the part attribute condition report because it is valuable to record the agent and date along with the text, and to be able to distinguish one report from another instead of having one long stream of everything in the part condition field. Another reason was to be able to encumber the information. Once this part attribute was created, I went ahead and copied over the condition data in the part condition field into this new part attribute, and so currently this data is duplicated in two places. What I want to do is replace all text in every object part condition field for the UAM:Art collection with "see condition report(s)". I don't see a way to do this other than going through records one-by-one. Is there a simple way to do this?

@Jegelewicz
Copy link
Member

What I want to do is replace all text in every object part condition field for the UAM:Art collection with "see condition report(s)". I don't see a way to do this other than going through records one-by-one. Is there a simple way to do this?

@dustymc can probably magic this for you.

@ewommack
Copy link

ewommack commented Mar 12, 2022

@krgomez and @marecaguthrie the AWG meetings are on the 4th Thursday of every month at 12pm MT for 2022, and the AWG Issues meetings are on the 1st Thursday of every month at 12pm MT for 2022. So the next AWG meeting will be on the 24th of March.
You can find the info in the Arctos google calendar. Let us know if you need help finding it.

@Jegelewicz
Copy link
Member

Bring this to the AWG - how many encumbrances do we need? What is the policy for hiding Arctos data.

@Jegelewicz Jegelewicz added the Administrative How the community functions - these issues may be transferred to internal repos label Sep 15, 2022
@Jegelewicz
Copy link
Member

Removing from the Code Table Project - this is a broader community issue and I am not certain it has been resolved.

@marecaguthrie
Copy link

marecaguthrie commented Nov 14, 2022 via email

@Jegelewicz
Copy link
Member

@marecaguthrie we had a long discussion about encumbrances at the October AWG meeting - see the notes here. This topic was then placed on the Officer's Meeting Agenda (October 28) and there it was suggested it be added to the next Board Meeting, which will be in January.

@Jegelewicz
Copy link
Member

UGH - this was never added to the Advisory Committee Agenda.

@Jegelewicz Jegelewicz modified the milestones: Next AWG Meeting, Next Advisory Committee Meeting Jan 25, 2023
@mkoo
Copy link
Member

mkoo commented Jan 26, 2023

We can discuss today at the AWG meeting but reading this thread, my main question to be discussed is whether this information needs to be simply "private" for curatorial eyes only or truly "encumbered" which has implication beyond the collection and Arctos wide. Is there a middle ground we need? Let's discuss

@dustymc
Copy link
Contributor

dustymc commented Jan 26, 2023

simply "private"

Yes, that is worth discussing. I don't have anything specific in mind, but encumbrances are expensive (in code, maintenance, and CPU - and 'financially' should be added to the list) and just making some things internal by decree might be a simplification for all (or a horrible complicating mistake, IDK, needs discussed).

today

I'm not sure this is priority??

@campmlc
Copy link

campmlc commented Jan 26, 2023

I support having the option of "private" for curatorial eyes only, because there are certain data in our collections that are exactly that, and we don't want to have them suddenly unencumbered in 5 years because someone didn't read a notification.

@mkoo
Copy link
Member

mkoo commented Jan 26, 2023

AWG discussion: new issue needed to proposed which components of a record that could be public or private under curatorial management.

@dustymc dustymc modified the milestones: Next Advisory Committee Meeting, Needs Discussion Feb 27, 2023
@Jegelewicz
Copy link
Member

I'm wondering if we could just not display some list/category/something of part (and maybe other??) attributes?

Could we have curatorial attributes? A list of attributes that are always private? Some of these may be the same information as existing attributes, but selecting the curatorial version means keeping the information out of the public interface.

@dustymc
Copy link
Contributor

dustymc commented May 3, 2024

curatorial attributes

As an addition: I don't think that's at all sustainable, I already struggle with the resources to deal with attributes, adding a multiplier does not sound like fun for anyone.

As a replacement: Worth a hard look.

@mkoo
Copy link
Member

mkoo commented Nov 26, 2024

This issue is stale at this point-- I am closing and creating a new issue (#8338) with the current proposal summary from this thread.

@mkoo mkoo closed this as completed Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administrative How the community functions - these issues may be transferred to internal repos Collection Type - Cultural Collections Art, Ethnography, etc collection related Enhancement I think this would make Arctos even awesomer! Priority-High (Needed for work) High because this is causing a delay in important collection work..
Projects
None yet
Development

No branches or pull requests

8 participants