One more voice from the Functional Working Group. I agree with Michael and Megan, I think if the procedure is Conservation then that would be the best to stick with conservation/ conservation. I think the thoughts that Michael was able to get from his conservator tells us a lot about how the procedure will function by those using it, and I think Megan's point of being consistent to avoid confusion is very valuable. Jessica ________________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of talk-request@lists.collectionspace.org <talk-request@lists.collectionspace.org> Sent: Friday, November 6, 2015 12:00 PM To: talk@lists.collectionspace.org Subject: Talk Digest, Vol 75, Issue 7 Send Talk mailing list submissions to talk@lists.collectionspace.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org or, via email, send a message with subject or body 'help' to talk-request@lists.collectionspace.org You can reach the person managing the list at talk-owner@lists.collectionspace.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Talk digest..." Today's Topics: 1. Re: Conservation(s)? (Megan Forbes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Nov 2015 16:56:17 +0000 From: Megan Forbes <megan.forbes@lyrasis.org> To: Michael Black <mtblack@berkeley.edu>, Richard Millet <richard.millet@lyrasis.org> Cc: CollectionSpace Talk List <talk@lists.collectionspace.org> Subject: Re: [Talk] Conservation(s)? Message-ID: <BY2PR08MB1799119DD7646A45419AE1EA80280@BY2PR08MB1799.namprd08.prod.outlook.com> Content-Type: text/plain; charset="windows-1252" Seconding conservation/conservation. The backend name does show up on the front end, and if it doesn't match the procedure name it can be confusing - a la "movement" being the name in the permissions list for the Location procedure. If we agree that the procedure is Conservation, let's be consistent with that. 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: Talk <talk-bounces@lists.collectionspace.org> on behalf of Michael Black <mtblack@berkeley.edu> Sent: Friday, November 6, 2015 11:52 AM To: Richard Millet Cc: CollectionSpace Talk List Subject: Re: [Talk] Conservation(s)? Functional Working Group member chiming in. When I first saw Ray's question last night, going with "treatment(s)" was the option that first occurred to me. Even the analysis that would be documented on this procedure (well, most of it?see further below) would be done within the scope of a treatment. But then I spoke with one of our conservators just now and went over the data map with her (see PAHMA-1402<https://issues.collectionspace.org/browse/PAHMA-1402>), and she said that since destructive analysis was included, and destructive analysis would often just be documented in this procedure without any accompanying treatment, it would be inaccurate to call the whole procedure a treatment procedure. So as much as I like going with "treatment/treatments", it looks like "conservation/conservation" is the better choice. Michael On Fri, Nov 6, 2015 at 8:24 AM, Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> wrote: Let's not go with "treatment" just because it is easier to pluralize. I think Megan and other members of the Functional Working Group should comment? ________________________________ From: Talk <talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>> on behalf of John B Lowe <jblowe@berkeley.edu<mailto:jblowe@berkeley.edu>> Sent: Friday, November 06, 2015 10:12 AM To: Peter Murray Cc: CollectionSpace Talk List Subject: Re: [Talk] Conservation(s)? I overheard Al and Michael talking about what would actually be going into the procedure, and related procedures, such as Analysis (which has problems of its own from the point of view of pluralization). However, they were observing that the core concept of the procedure centered on the idea of recording information about "treatments" of objects, whether for conservation analysis, or other purposes. So...how about Treatments? John On Fri, Nov 6, 2015 at 7:26 AM, Peter Murray <pmurray@chillco.com<mailto:pmurray@chillco.com>> wrote: Hey Ray, This is one of the things that has tripped me up, so I'm quite sensitive to it. (Ran up against 'org' versus 'organization' in the authorities realm last week.) How about using 'treatment/treatments' instead? Peter On Nov 5, 2015, at 8:56 PM, Ray Lee <rhlee@berkeley.edu<mailto:rhlee@berkeley.edu>> wrote: Hi everyone, I'm implementing the Conservation procedure (https://wiki.collectionspace.org/display/collectionspace/Conservation+and+Collections+Care+Requirements), and I need to give it a service name. This is the string that appears in the services REST URL, and in schema names. For example, for the Movement procedure, /cspace-services/movements and movements_common. Usually, the service name is pluralized. But "conservation" isn't a countable thing, right? So it doesn't make sense to pluralize? Like, you wouldn't say "I did a conservation," or "there are three conservations over there." In this case "conservation" is really an abbreviation of "conservation treatment." And conservationtreatments seems too long, so is just conservation ok? Are there any rules about this? Opinions? Thanks, Ray _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org -- Peter Murray Dev/Ops Lead and Project Manager Cherry Hill Company _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org -- Michael Black, Ph.D. Head of Research and Information Phoebe A. Hearst Museum of Anthropology University of California, Berkeley mtblack@berkeley.edu<mailto:mtblack@berkeley.edu> [https://docs.google.com/uc?export=download&id=0B0XpjHs2G_OIRUJIODVtSTdIS2M&revid=0B0XpjHs2G_OIOWlzNEgzM0w3YjNzREZQVERQL3R4VXFKNTNvPQ]<http://biggive.berkeley.edu>

1. Re: Conservation(s)? (Megan Forbes)

Hi all, I agree with calling this procedure conservation/conservation, due to the range of conservation activities that might be recorded. Calling it conservation is also consistent with other collections management systems. On Friday, November 6, 2015, Jenkins, Jessica D. (Alumni) < jenkinsjed@my.ccsu.edu> wrote: > One more voice from the Functional Working Group. I agree with Michael and > Megan, I think if the procedure is Conservation then that would be the best > to stick with conservation/ conservation. I think the thoughts that Michael > was able to get from his conservator tells us a lot about how the procedure > will function by those using it, and I think Megan's point of being > consistent to avoid confusion is very valuable. > > Jessica > > ________________________________________ > From: Talk <talk-bounces@lists.collectionspace.org <javascript:;>> on > behalf of talk-request@lists.collectionspace.org <javascript:;> < > talk-request@lists.collectionspace.org <javascript:;>> > Sent: Friday, November 6, 2015 12:00 PM > To: talk@lists.collectionspace.org <javascript:;> > Subject: Talk Digest, Vol 75, Issue 7 > > Send Talk mailing list submissions to > talk@lists.collectionspace.org <javascript:;> > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > or, via email, send a message with subject or body 'help' to > talk-request@lists.collectionspace.org <javascript:;> > > You can reach the person managing the list at > talk-owner@lists.collectionspace.org <javascript:;> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk digest..." > > > Today's Topics: > > 1. Re: Conservation(s)? (Megan Forbes) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 6 Nov 2015 16:56:17 +0000 > From: Megan Forbes <megan.forbes@lyrasis.org <javascript:;>> > To: Michael Black <mtblack@berkeley.edu <javascript:;>>, Richard Millet > <richard.millet@lyrasis.org <javascript:;>> > Cc: CollectionSpace Talk List <talk@lists.collectionspace.org > <javascript:;>> > Subject: Re: [Talk] Conservation(s)? > Message-ID: > < > BY2PR08MB1799119DD7646A45419AE1EA80280@BY2PR08MB1799.namprd08.prod.outlook.com > <javascript:;>> > > Content-Type: text/plain; charset="windows-1252" > > Seconding conservation/conservation. The backend name does show up on the > front end, and if it doesn't match the procedure name it can be confusing - > a la "movement" being the name in the permissions list for the Location > procedure. > > > If we agree that the procedure is Conservation, let's be consistent with > that. > > > > > Megan Forbes > CollectionSpace Community Outreach and Support Manager > megan.forbes@lyrasis.org <javascript:;> > 800.999.8558 x 2917 Main > 917.267.9676 Cell > meganbforbes Skype > > > > > ________________________________ > From: Talk <talk-bounces@lists.collectionspace.org <javascript:;>> on > behalf of Michael Black <mtblack@berkeley.edu <javascript:;>> > Sent: Friday, November 6, 2015 11:52 AM > To: Richard Millet > Cc: CollectionSpace Talk List > Subject: Re: [Talk] Conservation(s)? > > Functional Working Group member chiming in. When I first saw Ray's > question last night, going with "treatment(s)" was the option that first > occurred to me. Even the analysis that would be documented on this > procedure (well, most of it?see further below) would be done within the > scope of a treatment. > > But then I spoke with one of our conservators just now and went over the > data map with her (see PAHMA-1402< > https://issues.collectionspace.org/browse/PAHMA-1402>), and she said that > since destructive analysis was included, and destructive analysis would > often just be documented in this procedure without any accompanying > treatment, it would be inaccurate to call the whole procedure a treatment > procedure. > > So as much as I like going with "treatment/treatments", it looks like > "conservation/conservation" is the better choice. > > Michael > > On Fri, Nov 6, 2015 at 8:24 AM, Richard Millet <richard.millet@lyrasis.org > <javascript:;><mailto:richard.millet@lyrasis.org <javascript:;>>> wrote: > > Let's not go with "treatment" just because it is easier to pluralize. I > think Megan and other members of the Functional Working Group should > comment? > > > ________________________________ > From: Talk <talk-bounces@lists.collectionspace.org <javascript:;><mailto: > talk-bounces@lists.collectionspace.org <javascript:;>>> on behalf of John > B Lowe <jblowe@berkeley.edu <javascript:;><mailto:jblowe@berkeley.edu > <javascript:;>>> > Sent: Friday, November 06, 2015 10:12 AM > To: Peter Murray > Cc: CollectionSpace Talk List > Subject: Re: [Talk] Conservation(s)? > > I overheard Al and Michael talking about what would actually be going into > the procedure, and related procedures, such as Analysis (which has problems > of its own from the point of view of pluralization). > > However, they were observing that the core concept of the procedure > centered on the idea of recording information about "treatments" of > objects, whether for conservation analysis, or other purposes. > > So...how about Treatments? > > John > > On Fri, Nov 6, 2015 at 7:26 AM, Peter Murray <pmurray@chillco.com > <javascript:;><mailto:pmurray@chillco.com <javascript:;>>> wrote: > Hey Ray, > > This is one of the things that has tripped me up, so I'm quite sensitive > to it. (Ran up against 'org' versus 'organization' in the authorities > realm last week.) How about using 'treatment/treatments' instead? > > > Peter > > On Nov 5, 2015, at 8:56 PM, Ray Lee <rhlee@berkeley.edu <javascript:;> > <mailto:rhlee@berkeley.edu <javascript:;>>> wrote: > > Hi everyone, > I'm implementing the Conservation procedure ( > https://wiki.collectionspace.org/display/collectionspace/Conservation+and+Collections+Care+Requirements), > and I need to give it a service name. This is the string that appears in > the services REST URL, and in schema names. For example, for the Movement > procedure, /cspace-services/movements and movements_common. > > Usually, the service name is pluralized. But "conservation" isn't a > countable thing, right? So it doesn't make sense to pluralize? Like, you > wouldn't say "I did a conservation," or "there are three conservations over > there." In this case "conservation" is really an abbreviation of > "conservation treatment." And conservationtreatments seems too long, so is > just conservation ok? > > Are there any rules about this? Opinions? > > Thanks, > Ray > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <javascript:;><mailto: > Talk@lists.collectionspace.org <javascript:;>> > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > -- > Peter Murray > Dev/Ops Lead and Project Manager > Cherry Hill Company > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <javascript:;><mailto: > Talk@lists.collectionspace.org <javascript:;>> > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <javascript:;><mailto: > Talk@lists.collectionspace.org <javascript:;>> > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > > > -- > Michael Black, Ph.D. > Head of Research and Information > Phoebe A. Hearst Museum of Anthropology > University of California, Berkeley > mtblack@berkeley.edu <javascript:;><mailto:mtblack@berkeley.edu > <javascript:;>> > > [ > https://docs.google.com/uc?export=download&id=0B0XpjHs2G_OIRUJIODVtSTdIS2M&revid=0B0XpjHs2G_OIOWlzNEgzM0w3YjNzREZQVERQL3R4VXFKNTNvPQ > ]<http://biggive.berkeley.edu> >