search

LibraryCarpentry / governance

Repository for minutes and notes regarding the Library Carpentry Governance Committee
8 stars 6 forks source link

Goal 2 Mini Group - Map LC lesson material to library resumes CVs job descriptions competencies #17

Closed ragamouf closed 3 years ago

ragamouf commented 5 years ago

Goal definition

Our task, find 1-2 library resumes/CVs/job descriptions/competencies and tag particular lesson programs (Software, Data, Library Carpentry), lessons (OpenRefine, R, SQL, etc), episodes (grep, regex, database design, etc)

Part A: Link the tagged document(s) with a brief description below.

Part B: Plan to build an overview table with lessons, episodes etc as variable names and rows for the documents - job descriptions/ competencies etc.

Some initial work was done here: https://librarycarpentry.org/audience/

Part A Areas: Research, Collections, Scholarly Communication, Assessment, Technical/Metadata, Access & Delivery, Teaching, Archives Electronic Resources Coordinator (Librarian) https://docs.google.com/document/d/1ZOZxFB5a_ahTyaB2_pMQ4wZ4bUfHIfiipBYp8XIqopU/edit?usp=sharing From: http://www.ala.org/aboutala/offices/publishing/editions/webextras/technologymadesimple/jobdescriptions/jobdescriptions#electronic

Part B Competencies:

Active members on this goal

@davidfkane @jcoliver @goldmj @gitti1 @jaredabera @libcce

ragamouf commented 5 years ago

Proof of concept for the table Following on from how @libcce tagged the Electronic Resources Coordinator, I've grouped the variables for this table into 4 major categories:

  1. LC core lessons
  2. LC extended lessons
  3. Other carpentries lessons
  4. Carpentries activities - indicating transferrable skills and experience gained by engaging in lessons development, maintenance, instructor certification etc.

I think getting into the episode detail might make this table overwhelming, but certainly happy for anyone to extend the table as you see fit. On rows 4-6 are links to yet-to-be-tagged pdfs of generic job descriptions. I welcome anyone who wants to have a go at tagging these in the fashion that Chris did. Or just ignore them and submit your own.

I got really enthusiastic about the compentencies (part B), but that seems like too big a task in the short term - and it probably warrants another sheet. I think sticking with Part A of this goal would also be helpful in terms of building relationships with people who can help us create impact stories for LC.

gitti1 commented 5 years ago

Hi Liz and all,

from the LIBER list I have added another job description and ticked the relevant lessons (I also added two more columns from the SWC curriculum).

In this table I assume that we read this as an answer to the question: "Is the lesson or activity relevant for the job profile?" - ie we could work with the answer options "yes" and "no" (add a neutral one "not sure"?). IMHO all answers should be made explicit in the table.

All best, Birgit

Am 24.09.2019 um 02:36 schrieb Liz Stokes:

Goal definition

Our task, find 1-2 library resumes/CVs/job descriptions/competencies and tag particular lesson programs (Software, Data, Library Carpentry), lessons (OpenRefine, R, SQL, etc), episodes (grep, regex, database design, etc)

Part A: Link the tagged document(s) with a brief description below.

Part B: Plan to build an overview table with lessons, episodes etc as variable names and rows for the documents - job descriptions/ competencies etc.

Some initial work was done here: https://librarycarpentry.org/audience/

Part A Areas: Research, Collections, Scholarly Communication, Assessment, Technical/Metadata, Access & Delivery, Teaching, Archives Electronic Resources Coordinator (Librarian) https://docs.google.com/document/d/1ZOZxFB5a_ahTyaB2_pMQ4wZ4bUfHIfiipBYp8XIqopU/edit?usp=sharing From: http://www.ala.org/aboutala/offices/publishing/editions/webextras/technologymadesimple/jobdescriptions/jobdescriptions#electronic

Part B Competencies:

@davidfkane https://github.com/davidfkane @jcoliver https://github.com/jcoliver @goldmj https://github.com/goldmj @gitti1 https://github.com/gitti1 @Jaredabera https://github.com/Jaredabera @libcce https://github.com/libcce

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LibraryCarpentry/governance/issues/17?email_source=notifications&email_token=ABFLHTNU4Q3N7A5PZDFY7T3QLFOI7A5CNFSM4IZWTP32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNFTXIA, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFLHTJXSQIDW7TNFM6FZ4DQLFOI7ANCNFSM4IZWTP3Q.

-- Dr Birgit Schmidt Head of Knowledge Commons

Göttingen State and University Library Wissen als Gemeingut (WAG) Platz der Göttinger Sieben DE - 37070 Göttingen

Tel +49 551 39 33181 Fax +49 551 39 5222

www.openaire.eu www.fosteropenscience.eu

ragamouf commented 5 years ago

Thanks Birgit, your clarification is valuable – maybe that means this table performs an evaluative stage, and could be summarised later to illustrate LC promotional materials.

Cheers, Liz

From: Birgit Schmidt notifications@github.com Sent: Tuesday, 24 September 2019 11:58 PM To: LibraryCarpentry/governance governance@noreply.github.com Cc: Liz Stokes Elizabeth.Stokes@uts.edu.au; Author author@noreply.github.com Subject: Re: [LibraryCarpentry/governance] Map LC lesson material to library resumes CVs job descriptions competencies (#17)

Hi Liz and all,

from the LIBER list I have added another job description and ticked the relevant lessons (I also added two more columns from the SWC curriculum).

In this table I assume that we read this as an answer to the question: "Is the lesson or activity relevant for the job profile?" - ie we could work with the answer options "yes" and "no" (add a neutral one "not sure"?). IMHO all answers should be made explicit in the table.

All best, Birgit

Am 24.09.2019 um 02:36 schrieb Liz Stokes:

Goal definition

Our task, find 1-2 library resumes/CVs/job descriptions/competencies and tag particular lesson programs (Software, Data, Library Carpentry), lessons (OpenRefine, R, SQL, etc), episodes (grep, regex, database design, etc)

Part A: Link the tagged document(s) with a brief description below.

Part B: Plan to build an overview table with lessons, episodes etc as variable names and rows for the documents - job descriptions/ competencies etc.

Some initial work was done here: https://librarycarpentry.org/audience/https://librarycarpentry.org/audience/

Part A Areas: Research, Collections, Scholarly Communication, Assessment, Technical/Metadata, Access & Delivery, Teaching, Archives Electronic Resources Coordinator (Librarian) https://docs.google.com/document/d/1ZOZxFB5a_ahTyaB2_pMQ4wZ4bUfHIfiipBYp8XIqopU/edit?usp=sharinghttps://docs.google.com/document/d/1ZOZxFB5a_ahTyaB2_pMQ4wZ4bUfHIfiipBYp8XIqopU/edit?usp=sharing From: http://www.ala.org/aboutala/offices/publishing/editions/webextras/technologymadesimple/jobdescriptions/jobdescriptions#electronichttp://www.ala.org/aboutala/offices/publishing/editions/webextras/technologymadesimple/jobdescriptions/jobdescriptions#electronic

Part B Competencies:

Active members on this goal

@davidfkane https://github.com/davidfkane<https://github.com/davidfkane> @jcoliver https://github.com/jcoliver<https://github.com/jcoliver> @goldmj https://github.com/goldmj<https://github.com/goldmj> @gitti1 https://github.com/gitti1<https://github.com/gitti1> @Jaredabera https://github.com/Jaredabera<https://github.com/Jaredabera> @libcce https://github.com/libcce<https://github.com/libcce>

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LibraryCarpentry/governance/issues/17?email_source=notifications&email_token=ABFLHTNU4Q3N7A5PZDFY7T3QLFOI7A5CNFSM4IZWTP32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNFTXIA<https://github.com/LibraryCarpentry/governance/issues/17?email_source=notifications&email_token=ABFLHTNU4Q3N7A5PZDFY7T3QLFOI7A5CNFSM4IZWTP32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNFTXIA>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFLHTJXSQIDW7TNFM6FZ4DQLFOI7ANCNFSM4IZWTP3Q<https://github.com/notifications/unsubscribe-auth/ABFLHTJXSQIDW7TNFM6FZ4DQLFOI7ANCNFSM4IZWTP3Q>.

-- Dr Birgit Schmidt Head of Knowledge Commons

Göttingen State and University Library Wissen als Gemeingut (WAG) Platz der Göttinger Sieben DE - 37070 Göttingen

Tel +49 551 39 33181 Fax +49 551 39 5222

www.openaire.euhttp://www.openaire.eu www.fosteropenscience.euhttp://www.fosteropenscience.eu

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/LibraryCarpentry/governance/issues/17?email_source=notifications&email_token=ALEILNT2NJPP673TKEXMSDTQLIMHJA5CNFSM4IZWTP32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7OOP2Y#issuecomment-534570987, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALEILNVYWNWX75KNX7P5FT3QLIMHJANCNFSM4IZWTP3Q.

UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email.

libcce commented 5 years ago

Hi @ragamouf the mapping sheet is great and thanks @gitti1 for adding to it. There was one other category that I was considering @ragamouf called "community building" under "Carpentries Activities" but I was on the fence. It would describe hosting discussions, participating on committees/groups, etc. @gitti1 was curious why you chose SWC R and Python (vs DC Carpentry)? I like the selections as when I advocated for membership at my previous institution, the goal was to connect with early-career researchers across a number of disciplines and I think SWC does this well. That's often a focus of library data services positions to connect with early-career researchers.

I'm also thinking that the map we develop can be turned into a visual like this https://pbs.twimg.com/media/EB7fMq6XsAMZJKa.jpg. Thoughts?

ragamouf commented 5 years ago

Hi @libcce yes definitely add community building to the carpentries activities section. I think that's a very relevant skill for outreach/liaison librarians; and also could help challenge implicit assumptions that metadata/ cataloging librarians are necessarily internally focussed.

I would support your visual map idea too - so

concentric circles content
first inner layer LC, SWC, DC, Activities
second layer LC lessons SWC lessons DC lessons community building
third layer Episode in the lessons...
fourth layer Librarian job titles
fifth layer Statement from selection criteria

I'm thinking this would look great on a poster at a library conference!

libcce commented 5 years ago

Maybe the same person who created the LIBER design can help us @gitti1? Meanwhile, I have to do one more job description.

arieldeardorff commented 4 years ago

Hi All! I am not sure if this is really in the scope of your mini goal but I just had a question from an attendee about whether an upcoming Library Carpentry workshop was certified for CE credit. She was referring to the Medical Library Association Continuing Education credits and it made me wonder if there are other types of librarians who need CE and if any of the LC mapping should connect to those criteria. (The answer btw was no it doesn't count for CE because you need to have the course officially sanctioned by MLA and we haven't done that)

ragamouf commented 3 years ago

Closing this long forsaken goal because it is a good idea but perhaps we've made it too big/ unattainable. Part of me still holds out for reviving it in a Legacy goals sprint, which is a fantasy I will hold onto for a rainy day.