talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsCode contribution functional review request: Valuation procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core code. This procedure is based on the Spectrum valuation procedure. Please take some time to review the schema and user interface for this contribution and let us know your thoughts.
The schema for the procedure is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February 21st. Not sure what you're looking for? Check out our wiki page on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan?
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Hi Megan,
Nice to hear from you – it’s been a long period of silence. We are looking forward to see the development of CollectionSpace start up again once the organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure become part of CS Core. Here valuations are considered confidential information, that we don’t want all of our users to see. In addition to this the Danish State Archives recently required us to keep record of historical valuations; hitherto they were just overwritten when the valuations were changed. So the procedure Jesse has developed for the Walker Art Center would be very useful to us. It would require no extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dkhttp://smk.dk/
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core code. This procedure is based on the Spectrum valuation procedure. Please take some time to review the schema and user interface for this contribution and let us know your thoughts.
The schema for the procedure is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February 21st. Not sure what you're looking for? Check out our wiki page on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Great, thanks for the feedback, Kim.
I'd recommend a few small changes to the procedure as developed to make it align a little better with the Spectrum procedure & our current practices:
-
The "Object valuation renewal date" as recommended by Spectrum is not present
-
Put the "Currency" and "Value" fields into a repeatable group, to allow for recording multiple currencies
-
Link the "Source" field to the Person and Organization authorities
?
Thanks,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
From: Kim Brasen Kim.Brasen@smk.dk
Sent: Tuesday, February 11, 2014 3:39 AM
To: Megan Forbes
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] Code contribution functional review request: Valuation procedure
Hi Megan,
Nice to hear from you - it's been a long period of silence. We are looking forward to see the development of CollectionSpace start up again once the organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure become part of CS Core. Here valuations are considered confidential information, that we don't want all of our users to see. In addition to this the Danish State Archives recently required us to keep record of historical valuations; hitherto they were just overwritten when the valuations were changed. So the procedure Jesse has developed for the Walker Art Center would be very useful to us. It would require no extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
S?lvgade 48-50
DK-1307 K?benhavn K
T +45 3374 8494
F +45 3374 8404
smk.dkhttp://smk.dk/
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] P? vegne af Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core code. This procedure is based on the Spectrum valuation procedure. Please take some time to review the schema and user interface for this contribution and let us know your thoughts.
The schema for the procedure is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February 21st. Not sure what you're looking for? Check out our wiki page on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan?
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Megan,
This recommendation brings up some important implications. If you change the schema then a) someone has to do that work and b) anyone who has implemented the code that Jesse originally developed will have to perform some data migration in order to upgrade to the version of CSpace that incorporates the changed schema. We've come across these issues with our deployments at Berkeley, so I just ask that the core project keep these things in mind.
Thanks,
Chris
On Feb 11, 2014, at 6:10 AM, Megan Forbes wrote:
Great, thanks for the feedback, Kim.
I'd recommend a few small changes to the procedure as developed to make it align a little better with the Spectrum procedure & our current practices:
- The "Object valuation renewal date" as recommended by Spectrum is not present
- Put the "Currency" and "Value" fields into a repeatable group, to allow for recording multiple currencies
- Link the "Source" field to the Person and Organization authorities
Thanks,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
From: Kim Brasen Kim.Brasen@smk.dk
Sent: Tuesday, February 11, 2014 3:39 AM
To: Megan Forbes
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] Code contribution functional review request: Valuation procedure
Hi Megan,
Nice to hear from you – it’s been a long period of silence. We are looking forward to see the development of CollectionSpace start up again once the organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure become part of CS Core. Here valuations are considered confidential information, that we don’t want all of our users to see. In addition to this the Danish State Archives recently required us to keep record of historical valuations; hitherto they were just overwritten when the valuations were changed. So the procedure Jesse has developed for the Walker Art Center would be very useful to us. It would require no extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dk
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core code. This procedure is based on the Spectrum valuation procedure. Please take some time to review the schema and user interface for this contribution and let us know your thoughts.
The schema for the procedure is here:http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here:http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February 21st. Not sure what you're looking for? Check out our wiki page on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Megan,
I agree with you. It is important that we as close as possible adhere to the Spectrum standard, if that is what we say we do. However none of the additional fields are not requirements of ours. I would expect though to have the source fields linked to Name authorities as you suggest.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dkhttp://smk.dk/
Fra: Megan Forbes [mailto:megan.forbes@lyrasis.org]
Sendt: 11. februar 2014 15:10
Til: Kim Brasen
Cc: talk@lists.collectionspace.org
Emne: RE: [Talk] Code contribution functional review request: Valuation procedure
Great, thanks for the feedback, Kim.
I'd recommend a few small changes to the procedure as developed to make it align a little better with the Spectrum procedure & our current practices:
-
The "Object valuation renewal date" as recommended by Spectrum is not present
-
Put the "Currency" and "Value" fields into a repeatable group, to allow for recording multiple currencies
-
Link the "Source" field to the Person and Organization authorities
Thanks,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
From: Kim Brasen <Kim.Brasen@smk.dkmailto:Kim.Brasen@smk.dk>
Sent: Tuesday, February 11, 2014 3:39 AM
To: Megan Forbes
Cc: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: SV: [Talk] Code contribution functional review request: Valuation procedure
Hi Megan,
Nice to hear from you – it’s been a long period of silence. We are looking forward to see the development of CollectionSpace start up again once the organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure become part of CS Core. Here valuations are considered confidential information, that we don’t want all of our users to see. In addition to this the Danish State Archives recently required us to keep record of historical valuations; hitherto they were just overwritten when the valuations were changed. So the procedure Jesse has developed for the Walker Art Center would be very useful to us. It would require no extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dkhttp://smk.dk/
Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core code. This procedure is based on the Spectrum valuation procedure. Please take some time to review the schema and user interface for this contribution and let us know your thoughts.
The schema for the procedure is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here: http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February 21st. Not sure what you're looking for? Check out our wiki page on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.orgmailto:firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Thank you, Kim, for your valuable comments in this thread!
Megan, it appears you already integrated the changes you mentioned earlier,
to conform the Valuation Control schema more closely with SPECTRUM, on this
page:
http://wiki.collectionspace.org/display/collectionspace/Valuation+Control+Schema
Is that correct? (If so, is this the page we should now be commenting on,
in this message thread?)
Aron
On Mon, Feb 17, 2014 at 5:03 AM, Kim Brasen Kim.Brasen@smk.dk wrote:
Hi Megan,
I agree with you. It is important that we as close as possible adhere to
the Spectrum standard, if that is what we say we do. However none of the
additional fields are not requirements of ours. I would expect though to
have the source fields linked to Name authorities as you suggest.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dk
Fra: Megan Forbes [mailto:megan.forbes@lyrasis.org]
Sendt: 11. februar 2014 15:10
Til: Kim Brasen
Cc: talk@lists.collectionspace.org
Emne: RE: [Talk] Code contribution functional review request: Valuation
procedure
Great, thanks for the feedback, Kim.
I'd recommend a few small changes to the procedure as developed to make it
align a little better with the Spectrum procedure & our current practices:
-
The "Object valuation renewal date" as recommended by Spectrum is not
present -
Put the "Currency" and "Value" fields into a repeatable group, to allow
for recording multiple currencies -
Link the "Source" field to the Person and Organization authorities
Thanks,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
------------------------------
From: Kim Brasen Kim.Brasen@smk.dk
Sent: Tuesday, February 11, 2014 3:39 AM
To: Megan Forbes
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] Code contribution functional review request:
Valuation procedure
Hi Megan,
Nice to hear from you – it’s been a long period of silence. We are looking
forward to see the development of CollectionSpace start up again once the
organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure
become part of CS Core. Here valuations are considered confidential
information, that we don’t want all of our users to see. In addition to
this the Danish State Archives recently required us to keep record of
historical valuations; hitherto they were just overwritten when the
valuations were changed. So the procedure Jesse has developed for the
Walker Art Center would be very useful to us. It would require no
extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dk
Fra: Talk [mailto:talk-bounces@lists.collectionspace.orgtalk-bounces@lists.collectionspace.org]
*På vegne af *Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation
procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a
VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core
code. This procedure is based on the Spectrum valuation procedure. Please
take some time to review the schema and user interface for this
contribution and let us know your thoughts.
The schema for the procedure is here:
http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here:
http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday, February
21st. Not sure what you're looking for? Check out our wiki page on
evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
PAHMA's Head Registrar commented on the Valuation Control procedure in this
JIRA:
http://issues.collectionspace.org/browse/PAHMA-938
They made three key points:
- There needs to be a "Type of value (pull down)".
That requirement seems to be satisfied by the "Object valuation type"
field, yes?
- "The Object Valuation Group ... does not contain a field for Valuer."
I believe it does, but it's now named "Valuation Source" - is that correct?
If so, perhaps we might make this clearer by:
a. Adding synonymous names for this field (AKAs) somewhere in the field's
definition on the schema, such as "Valuer" and "Determined By"; and/or
b. Consider changing the description slightly (emphasis added by me below)
from:
"The Person or Organization responsible for valuing an object on behalf
of the organization. "
to:
"The Person or Organization responsible for valuing this object or group
of objects [the latter added for consistency with other definitions, above
- Aron] on behalf of the organization."
- That there might be a valuation-related field or fields added to
Cataloging.
My thinking is that relating Valuation Control records to a Cataloging
record is the method by which we might best do this, but this is another
topic for discussion.
Finally, a fourth point came to mind, suggested by this sentence in the
description on PAHMA-938:
- "Currently we have only the two (ungrouped) Valuation Information fields
(Valuer and Valuation reference number), and those are only on Object Entry
[i.e. Intake - Aron]."
Do we need to also consider reworking - and/or removing - those existing
fields on Intake, once the Valuation Control procedure is added?
Thanks,
Aron
On Tue, Feb 18, 2014 at 5:17 PM, Aron Roberts aron@socrates.berkeley.eduwrote:
Thank you, Kim, for your valuable comments in this thread!
Megan, it appears you already integrated the changes you mentioned
earlier, to conform the Valuation Control schema more closely with
SPECTRUM, on this page:
http://wiki.collectionspace.org/display/collectionspace/Valuation+Control+Schema
Is that correct? (If so, is this the page we should now be commenting on,
in this message thread?)
Aron
On Mon, Feb 17, 2014 at 5:03 AM, Kim Brasen Kim.Brasen@smk.dk wrote:
Hi Megan,
I agree with you. It is important that we as close as possible adhere to
the Spectrum standard, if that is what we say we do. However none of the
additional fields are not requirements of ours. I would expect though to
have the source fields linked to Name authorities as you suggest.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dk
Fra: Megan Forbes [mailto:megan.forbes@lyrasis.org]
Sendt: 11. februar 2014 15:10
Til: Kim Brasen
Cc: talk@lists.collectionspace.org
Emne: RE: [Talk] Code contribution functional review request:
Valuation procedure
Great, thanks for the feedback, Kim.
I'd recommend a few small changes to the procedure as developed to make
it align a little better with the Spectrum procedure & our current
practices:
-
The "Object valuation renewal date" as recommended by Spectrum is not
present -
Put the "Currency" and "Value" fields into a repeatable group, to allow
for recording multiple currencies -
Link the "Source" field to the Person and Organization authorities
Thanks,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
------------------------------
From: Kim Brasen Kim.Brasen@smk.dk
Sent: Tuesday, February 11, 2014 3:39 AM
To: Megan Forbes
Cc: talk@lists.collectionspace.org
Subject: SV: [Talk] Code contribution functional review request:
Valuation procedure
Hi Megan,
Nice to hear from you – it’s been a long period of silence. We are
looking forward to see the development of CollectionSpace start up again
once the organizational home with Lyrasis has been firmly established.
At SMK we would very much like to see the Valuation Control Procedure
become part of CS Core. Here valuations are considered confidential
information, that we don’t want all of our users to see. In addition to
this the Danish State Archives recently required us to keep record of
historical valuations; hitherto they were just overwritten when the
valuations were changed. So the procedure Jesse has developed for the
Walker Art Center would be very useful to us. It would require no
extensions on our part, we would implement it as it is.
Cheers,
Kim
Best regards,
Kim Brasen
Curator
T +45 2552 7144 /
Statens Museum for Kunst
Sølvgade 48-50
DK—1307 København K
T +45 3374 8494
F +45 3374 8404
smk.dk
Fra: Talk [mailto:talk-bounces@lists.collectionspace.orgtalk-bounces@lists.collectionspace.org]
*På vegne af *Megan Forbes
Sendt: 10. februar 2014 17:42
Til: talk@lists.collectionspace.org
Emne: [Talk] Code contribution functional review request: Valuation
procedure
CollectionSpace Community:
On behalf of the Walker Art Center, Jesse Martinez has proposed a
VALUATION CONTROL PROCEDURE for inclusion into the CollectionSpace core
code. This procedure is based on the Spectrum valuation procedure. Please
take some time to review the schema and user interface for this
contribution and let us know your thoughts.
The schema for the procedure is here:
http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Schema
A screenshot of the implemented version at the Walker is here:
http://wiki.collectionspace.org/display/deploy/WAC+Valuation+Control+Procedure+Screenshot
Please send any comments or questions to the TALK list by Friday,
February 21st. Not sure what you're looking for? Check out our wiki page
on evaluating proposed code contributions:
http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Functional+Reviews
I look forward to hearing everyone's feedback.
Best regards,
Megan
Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org firstname.lastname@lyrasis.org
800.999.8558 x [2917] Main
917.267.9676 Cell
meganbforbes Skype
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org