From ct.annette at gmail.com Sat Oct 1 08:18:21 2016 From: ct.annette at gmail.com (Cheryl Thompson) Date: Sat, 1 Oct 2016 07:18:21 -0500 Subject: [Rdap] NDS Consortium Workshop: October 19-21, 2016 In-Reply-To: References: Message-ID: I thought some of you might be interested. NDS is focusing on library community at this meeting Sorry for any duplication, Cheryl ________________________________ > > From: Christine Kirkpatrick [christine at sdsc.edu] > > Sent: Wednesday, September 28, 2016 9:47 AM > > To: Willis, Craig > > Subject: REMINDER: NDS Consortium Workshop: October 19-21, 2016 > > > > > > Click here to see this online > > > > > > 6th National Data Service > > Consortium Workshop > > October 19-21, 2016 > > > > The program for the upcoming National Data Service Consortium sixth plenary meeting in Pittsburgh, October 19-21, is now available at http://go.illinois.edu/NDS6. > > > > Our theme is New Frontiers in Data Discovery: Collaboration with Research Libraries and we have a terrific line-up of illustrious speakers and a number of break-out sessions on topics related to the plenary presentations. > > > > Wednesday, October 19 is our ?hack day? for developers who want to learn more about NDS Labs and NDS Share and who want to work on pilot projects with the assistance of NDS staff. The first half of the day will include an introduction to Docker and the NDS Labs Workbench. The second half of the day we will delve into adding your tools and services to the NDS Labs Workbench. We will close the afternoon with a discussion about the new NDS, Interoperability Task Force and a Community Developer Input session which will provide an opportunity for you to share with us what you?re working on in your projects and how you?d like to work with the NDS development team. > > > > Please register online. Additional information about the meeting can be found on the NDS website or you may contact us at info at nationaldataservice.org. > > > > We look forward to seeing you at the Pittsburgh Supercomputing Center and Carnegie Mellon University?s (CMU) Software Engineering Institute next month! > > > > Workshop Details: > > > > Venue: Pittsburgh Supercomputing Center (PSC) and Carnegie Mellon University?s (CMU) Software Engineering Institute, Pittsburg, PA > > > > Accommodations: Wyndham Pittsburg University Center, a short walk to PSC and CMU > > > > Please note: Hotel block closes 10/4/16 > > > > Even if you cannot make the workshop, please stay tuned to the NDS website for other opportunities to get involved and join the conversation. > > > > Bob Hanisch > > Chair, NDSC Steering Committee Chair > > > > Christine Kirkpatrick > > NDSC Technical Advisory Committee (TAC) Chair > > > > REGISTRATION: https://illinois.edu/fb/sec/5343765 > > > > WORKSHOP SITE: http://go.illinois.edu/NDS6 > > > > To be removed from this list, please contact: info at nationaldataservice.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmfitzgerald at noble.org Tue Oct 11 10:22:00 2016 From: jmfitzgerald at noble.org (Fitzgerald, Jennifer) Date: Tue, 11 Oct 2016 14:22:00 +0000 Subject: [Rdap] Security/Storage Systems - DMP Language Message-ID: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Hello: Our institution's library and Data Management Committee are in the process of developing data management plan language for our researchers. There has been discussion regarding how much information to include regarding the security and storage systems used in our operations. There is a proposed paragraph that would describe at a very high level the infrastructure and software suite used by our institution's IT team, how those systems back up data, and general (but not precise) locations of where backup tapes are kept. One member of the Committee expressed concerns over divulging this type of information externally. Opinions and feedback are appreciated. Jennifer Fitzgerald Data Curator, Library and Information Management Services ________________________________ The Samuel Roberts Noble Foundation 2510 Sam Noble Parkway Ardmore, OK 73401 Telephone 580.224.6268 | Fax 580.224.6265 www.noble.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpetters at vt.edu Tue Oct 11 11:06:40 2016 From: jpetters at vt.edu (Jonathan Petters) Date: Tue, 11 Oct 2016 11:06:40 -0400 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: Jennifer, My two cents... If this is a DMP for a research proposal, I imagine that you don't need to have much specific detail about security and back-up. Most funder-specific DMPs have more of a 'What data are you going to share and how' focus... My impression is that proposal reviewers would mostly be interested the researcher affirming they are taking the necessary steps to secure their research data from loss, theft, or confidentiality breaches, and who's responsible for such actions. Thus, stating that they are storing their data on 'university-administered servers' that backup the data regularly and use some general form of authentication would be fine. No doubt the researcher is responsible for some security (e.g. storing a codebook separately from the human-subject data), and these actions should be written as well. But I imagine this could all be written in a way where your IT security folks wouldn't be afraid that too much information is being shared publicly. On the other hand, a detailed DMP for a research project to make sure that specific actions are taken care of appropriately by each responsible party (IT, researcher, IRB) and for which system/OS/dataset etc. would be a real helpful document, woudn't it?! That could be just shared internally though, and not for public consumption. Interested in hearing others' thoughts, it's a great question :) Jon On Tue, Oct 11, 2016 at 10:22 AM, Fitzgerald, Jennifer < jmfitzgerald at noble.org> wrote: > Hello: > > > > Our institution?s library and Data Management Committee are in the process > of developing data management plan language for our researchers. > > > > There has been discussion regarding how much information to include > regarding the security and storage systems used in our operations. There > is a proposed paragraph that would describe at a very high level the > infrastructure and software suite used by our institution?s IT team, how > those systems back up data, and general (but not precise) locations of > where backup tapes are kept. > > > > One member of the Committee expressed concerns over divulging this type of > information externally. Opinions and feedback are appreciated. > > > > *Jennifer Fitzgerald* > Data Curator, Library and Information Management Services > ------------------------------ > > The Samuel Roberts Noble Foundation > 2510 Sam Noble Parkway > Ardmore, OK 73401 > Telephone 580.224.6268 | Fax 580.224.6265 > www.noble.org > > > > > > _______________________________________________ > Rdap mailing list > Rdap at mail.asis.org > http://mail.asis.org/mailman/listinfo/rdap > > -- Jonathan Petters Ph.D. Data Management Consultant Data Services, University Libraries Virginia Tech (540) 232-8682 -------------- next part -------------- An HTML attachment was scrubbed... URL: From daureen.nesdill at utah.edu Tue Oct 11 11:18:50 2016 From: daureen.nesdill at utah.edu (Daureen Nesdill) Date: Tue, 11 Oct 2016 15:18:50 +0000 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: <4BB8E3E08D34034DB9A7D4F285555FB13CA0A5E1@X-MB4.xds.umail.utah.edu> I could not have said it better. Daureen Nesdill From: Rdap [mailto:rdap-bounces at asis.org] On Behalf Of Jonathan Petters Sent: Tuesday, October 11, 2016 9:07 AM To: Research Data, Access and Preservation Subject: Re: [Rdap] Security/Storage Systems - DMP Language Jennifer, My two cents... If this is a DMP for a research proposal, I imagine that you don't need to have much specific detail about security and back-up. Most funder-specific DMPs have more of a 'What data are you going to share and how' focus... My impression is that proposal reviewers would mostly be interested the researcher affirming they are taking the necessary steps to secure their research data from loss, theft, or confidentiality breaches, and who's responsible for such actions. Thus, stating that they are storing their data on 'university-administered servers' that backup the data regularly and use some general form of authentication would be fine. No doubt the researcher is responsible for some security (e.g. storing a codebook separately from the human-subject data), and these actions should be written as well. But I imagine this could all be written in a way where your IT security folks wouldn't be afraid that too much information is being shared publicly. On the other hand, a detailed DMP for a research project to make sure that specific actions are taken care of appropriately by each responsible party (IT, researcher, IRB) and for which system/OS/dataset etc. would be a real helpful document, woudn't it?! That could be just shared internally though, and not for public consumption. Interested in hearing others' thoughts, it's a great question :) Jon On Tue, Oct 11, 2016 at 10:22 AM, Fitzgerald, Jennifer > wrote: Hello: Our institution?s library and Data Management Committee are in the process of developing data management plan language for our researchers. There has been discussion regarding how much information to include regarding the security and storage systems used in our operations. There is a proposed paragraph that would describe at a very high level the infrastructure and software suite used by our institution?s IT team, how those systems back up data, and general (but not precise) locations of where backup tapes are kept. One member of the Committee expressed concerns over divulging this type of information externally. Opinions and feedback are appreciated. Jennifer Fitzgerald Data Curator, Library and Information Management Services ________________________________ The Samuel Roberts Noble Foundation 2510 Sam Noble Parkway Ardmore, OK 73401 Telephone 580.224.6268 | Fax 580.224.6265 www.noble.org _______________________________________________ Rdap mailing list Rdap at mail.asis.org http://mail.asis.org/mailman/listinfo/rdap -- Jonathan Petters Ph.D. Data Management Consultant Data Services, University Libraries Virginia Tech (540) 232-8682 -------------- next part -------------- An HTML attachment was scrubbed... URL: From skarcher at maxwell.syr.edu Tue Oct 11 10:56:37 2016 From: skarcher at maxwell.syr.edu (Sebastian Karcher) Date: Tue, 11 Oct 2016 14:56:37 +0000 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: I'd consider including this good practice. Having such documentation (as you say, at a high level) is part of the World Data System/Data Seal of Approval criteria for trustworthy digital repositories [1] (see R9). DSA publishes all past self-assessments, so you can look at some of the language used by repositories (using an older version of the criteria) on their assessment page [2] [1] https://docs.google.com/document/d/1_DPwSA5P8LpK9Q34BhxJmX8So2GKL7eSLa-G-z5JvVg/edit?pref=2&pli=1 [2] http://www.datasealofapproval.org/en/assessment/ Hope that helps, Sebastian Karcher | Associate Director Qualitative Data Repository Moynihan Institute | Maxwell School 346H Eggers Hall Syracuse, New York 13244 p 315.443.1634 e skarcher at syr.edu SYRACUSE UNIVERSITY syr.edu | qdr.syr.edu From: Rdap [mailto:rdap-bounces at asis.org] On Behalf Of Fitzgerald, Jennifer Sent: Tuesday, October 11, 2016 10:22 AM To: rdap at mail.asis.org Subject: [Rdap] Security/Storage Systems - DMP Language Hello: Our institution's library and Data Management Committee are in the process of developing data management plan language for our researchers. There has been discussion regarding how much information to include regarding the security and storage systems used in our operations. There is a proposed paragraph that would describe at a very high level the infrastructure and software suite used by our institution's IT team, how those systems back up data, and general (but not precise) locations of where backup tapes are kept. One member of the Committee expressed concerns over divulging this type of information externally. Opinions and feedback are appreciated. Jennifer Fitzgerald Data Curator, Library and Information Management Services ________________________________ The Samuel Roberts Noble Foundation 2510 Sam Noble Parkway Ardmore, OK 73401 Telephone 580.224.6268 | Fax 580.224.6265 www.noble.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmfitzgerald at noble.org Wed Oct 12 10:28:57 2016 From: jmfitzgerald at noble.org (Fitzgerald, Jennifer) Date: Wed, 12 Oct 2016 14:28:57 +0000 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: <1b4bdd250d9941eeb1dd0b7a39cb65f5@MailMBPrimary.noble.org> Thanks so much for the insight, Jon. I am going to present some options to present to the Committee members and see if they feel any better about it. Agreed, that they do need to do more of a show and tell of what actions they will take in order to make sure their data is stored and secured using best practices. From: Rdap [mailto:rdap-bounces at asis.org] On Behalf Of Jonathan Petters Sent: Tuesday, October 11, 2016 10:07 AM To: Research Data, Access and Preservation Subject: Re: [Rdap] Security/Storage Systems - DMP Language Jennifer, My two cents... If this is a DMP for a research proposal, I imagine that you don't need to have much specific detail about security and back-up. Most funder-specific DMPs have more of a 'What data are you going to share and how' focus... My impression is that proposal reviewers would mostly be interested the researcher affirming they are taking the necessary steps to secure their research data from loss, theft, or confidentiality breaches, and who's responsible for such actions. Thus, stating that they are storing their data on 'university-administered servers' that backup the data regularly and use some general form of authentication would be fine. No doubt the researcher is responsible for some security (e.g. storing a codebook separately from the human-subject data), and these actions should be written as well. But I imagine this could all be written in a way where your IT security folks wouldn't be afraid that too much information is being shared publicly. On the other hand, a detailed DMP for a research project to make sure that specific actions are taken care of appropriately by each responsible party (IT, researcher, IRB) and for which system/OS/dataset etc. would be a real helpful document, woudn't it?! That could be just shared internally though, and not for public consumption. Interested in hearing others' thoughts, it's a great question :) Jon On Tue, Oct 11, 2016 at 10:22 AM, Fitzgerald, Jennifer > wrote: Hello: Our institution?s library and Data Management Committee are in the process of developing data management plan language for our researchers. There has been discussion regarding how much information to include regarding the security and storage systems used in our operations. There is a proposed paragraph that would describe at a very high level the infrastructure and software suite used by our institution?s IT team, how those systems back up data, and general (but not precise) locations of where backup tapes are kept. One member of the Committee expressed concerns over divulging this type of information externally. Opinions and feedback are appreciated. Jennifer Fitzgerald Data Curator, Library and Information Management Services ________________________________ The Samuel Roberts Noble Foundation 2510 Sam Noble Parkway Ardmore, OK 73401 Telephone 580.224.6268 | Fax 580.224.6265 www.noble.org _______________________________________________ Rdap mailing list Rdap at mail.asis.org http://mail.asis.org/mailman/listinfo/rdap -- Jonathan Petters Ph.D. Data Management Consultant Data Services, University Libraries Virginia Tech (540) 232-8682 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlpetter at ucsc.edu Wed Oct 12 10:35:04 2016 From: jlpetter at ucsc.edu (Jonathan Petters) Date: Wed, 12 Oct 2016 10:35:04 -0400 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: Sebastian, I appreciate the pointer to the DSA-WDS trusted repository requirements! After seeing them at International Data Week I suggested we use them for a quick-and-dirty self-assessment of where we are for our own data IR repository (VTechData). I found them useful in spurring conversations here. Jennifer, glad what I said was helpful :) Jon On Tue, Oct 11, 2016 at 10:56 AM, Sebastian Karcher < skarcher at maxwell.syr.edu> wrote: > I?d consider including this good practice. Having such documentation (as > you say, at a high level) is part of the World Data System/Data Seal of > Approval criteria for trustworthy digital repositories [1] (see R9). DSA > publishes all past self-assessments, so you can look at some of the > language used by repositories (using an older version of the criteria) on > their assessment page [2] > > > > [1] https://docs.google.com/document/d/1_DPwSA5P8LpK9Q34BhxJmX8So2GKL7e > SLa-G-z5JvVg/edit?pref=2&pli=1 > > [2] http://www.datasealofapproval.org/en/assessment/ > > > > Hope that helps, > > > > > > *Sebastian Karcher* | Associate Director > > Qualitative Data Repository > Moynihan Institute | Maxwell School > 346H Eggers Hall > Syracuse, New York 13244 > > *p* 315.443.1634 *e* skarcher at syr.edu > > *SYRACUSE UNIVERSITY* > syr.edu | qdr.syr.edu > > > > > > > > *From:* Rdap [mailto:rdap-bounces at asis.org] *On Behalf Of *Fitzgerald, > Jennifer > *Sent:* Tuesday, October 11, 2016 10:22 AM > *To:* rdap at mail.asis.org > *Subject:* [Rdap] Security/Storage Systems - DMP Language > > > > Hello: > > > > Our institution?s library and Data Management Committee are in the process > of developing data management plan language for our researchers. > > > > There has been discussion regarding how much information to include > regarding the security and storage systems used in our operations. There > is a proposed paragraph that would describe at a very high level the > infrastructure and software suite used by our institution?s IT team, how > those systems back up data, and general (but not precise) locations of > where backup tapes are kept. > > > > One member of the Committee expressed concerns over divulging this type of > information externally. Opinions and feedback are appreciated. > > > > *Jennifer Fitzgerald* > Data Curator, Library and Information Management Services > ------------------------------ > > The Samuel Roberts Noble Foundation > 2510 Sam Noble Parkway > Ardmore, OK 73401 > Telephone 580.224.6268 | Fax 580.224.6265 > www.noble.org > > > > > > _______________________________________________ > Rdap mailing list > Rdap at mail.asis.org > http://mail.asis.org/mailman/listinfo/rdap > > -- Jonathan Petters Data Management Consultant Virginia Polytechnic Institute and State University Research Fellow Earth and Planetary Sciences Department UC - Santa Cruz -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.conrad at nara.gov Wed Oct 12 10:42:06 2016 From: mark.conrad at nara.gov (Mark Conrad) Date: Wed, 12 Oct 2016 10:42:06 -0400 Subject: [Rdap] Security/Storage Systems - DMP Language In-Reply-To: References: <32e1807d7bb642539c3152b8911b8356@MailMBPrimary.noble.org> Message-ID: If you want a more rigorous self-assessment, you might want to look at the self-assessment spreadsheet for ISO 16363 - Audit and certification of trustworthy digital repositories. You can find it here: http://www.iso16363.org/wp-content/uploads/sites/3/2014/10/Self-AssessmentTemplateforISO16363.xls Mark Conrad NARA Information Services IAS The National Archives and Records Administration Erma Ora Byrd Conference and Learning Center Building 494, Room 225 610 State Route 956 Rocket Center, WV 26726 Phone: 304-726-7820 Fax: 304-726-7802 Email: mark.conrad at nara.gov On Wed, Oct 12, 2016 at 10:35 AM, Jonathan Petters wrote: > Sebastian, > > I appreciate the pointer to the DSA-WDS trusted repository requirements! > After seeing them at International Data Week I suggested we use them for a > quick-and-dirty self-assessment of where we are for our own data IR > repository (VTechData). I found them useful in spurring conversations here. > > Jennifer, glad what I said was helpful :) > > Jon > > On Tue, Oct 11, 2016 at 10:56 AM, Sebastian Karcher < > skarcher at maxwell.syr.edu> wrote: > >> I?d consider including this good practice. Having such documentation (as >> you say, at a high level) is part of the World Data System/Data Seal of >> Approval criteria for trustworthy digital repositories [1] (see R9). DSA >> publishes all past self-assessments, so you can look at some of the >> language used by repositories (using an older version of the criteria) on >> their assessment page [2] >> >> >> >> [1] https://docs.google.com/document/d/1_DPwSA5P8LpK9Q34BhxJmX8S >> o2GKL7eSLa-G-z5JvVg/edit?pref=2&pli=1 >> >> [2] http://www.datasealofapproval.org/en/assessment/ >> >> >> >> Hope that helps, >> >> >> >> >> >> *Sebastian Karcher* | Associate Director >> >> Qualitative Data Repository >> Moynihan Institute | Maxwell School >> 346H Eggers Hall >> Syracuse, New York 13244 >> >> *p* 315.443.1634 *e* skarcher at syr.edu >> >> *SYRACUSE UNIVERSITY* >> syr.edu | qdr.syr.edu >> >> >> >> >> >> >> >> *From:* Rdap [mailto:rdap-bounces at asis.org] *On Behalf Of *Fitzgerald, >> Jennifer >> *Sent:* Tuesday, October 11, 2016 10:22 AM >> *To:* rdap at mail.asis.org >> *Subject:* [Rdap] Security/Storage Systems - DMP Language >> >> >> >> Hello: >> >> >> >> Our institution?s library and Data Management Committee are in the >> process of developing data management plan language for our researchers. >> >> >> >> There has been discussion regarding how much information to include >> regarding the security and storage systems used in our operations. There >> is a proposed paragraph that would describe at a very high level the >> infrastructure and software suite used by our institution?s IT team, how >> those systems back up data, and general (but not precise) locations of >> where backup tapes are kept. >> >> >> >> One member of the Committee expressed concerns over divulging this type >> of information externally. Opinions and feedback are appreciated. >> >> >> >> *Jennifer Fitzgerald* >> Data Curator, Library and Information Management Services >> ------------------------------ >> >> The Samuel Roberts Noble Foundation >> 2510 Sam Noble Parkway >> Ardmore, OK 73401 >> Telephone 580.224.6268 | Fax 580.224.6265 >> www.noble.org >> >> >> >> >> >> _______________________________________________ >> Rdap mailing list >> Rdap at mail.asis.org >> http://mail.asis.org/mailman/listinfo/rdap >> >> > > > -- > Jonathan Petters > > Data Management Consultant > Virginia Polytechnic Institute and State University > > Research Fellow > Earth and Planetary Sciences Department > UC - Santa Cruz > > > > _______________________________________________ > Rdap mailing list > Rdap at mail.asis.org > http://mail.asis.org/mailman/listinfo/rdap > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jamenebk at ku.edu Fri Oct 14 13:08:12 2016 From: jamenebk at ku.edu (Brooks Kieffer, Elizabeth Jamene) Date: Fri, 14 Oct 2016 17:08:12 +0000 Subject: [Rdap] IASSIST 2017 call for proposals Message-ID: <035786dc72c04a91ae35f50f67664940@ex13-csf-cr-12.home.ku.edu> IASSIST 2017 CALL FOR PROPOSALS Data in the Middle: The common language of research The 43rd annual conference of the International Association for Social Science Information Services and Technology (IASSIST) will be held in Lawrence, Kansas from May 23-16, 2017. #iassist17 Many issues around data (sources, strategies, and tools) are similar across disciplines. While IASSIST has its roots in social science data, it has also welcomed discussions over the years of other disciplines' issues as they relate to data, data management, and support of users. So again this year, in line with this tradition, we are arranging a conference that will benefit those who support researchers across all disciplines: social sciences, health and natural sciences, and humanities. Please join the international data community in Lawrence, KS, "in the middle" of the U.S., for insights and discussion on how data in all disciplines are found, shared, used, and managed. Join us and draw inspiration from this diverse gathering! We welcome submissions for papers, presentations, panels, posters, and pecha kuchas. The full Call for Proposals, along with the link to the submission form, can be accessed on the conference website here: http://www.iassist17.dept.ku.edu/proposals/ Questions can be directed to the Program Chairs, Samantha Guss and Michele Hayslett, at iassist2017 at gmail.com. We are also accepting submissions for Pre-conference Workshops under a separate Call for Workshops, which can be accessed here: http://www.iassist17.dept.ku.edu/proposals/workshops/ Questions about workshops may be sent to the Workshop Coordinators, Jenny Muilenburg (jmuil at uw.edu) and Andy Rutkowski (arutkowski at library.ucla.edu). Deadline for all submissions: 21 November 2016. Notification of acceptance: February 2017. _________ Jamene Brooks-Kieffer Data Services Librarian The University of Kansas 440 Watson Library 1425 Jayhawk Boulevard Lawrence, KS 66045 785-864-5238 jamenebk at ku.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjanz at upenn.edu Fri Oct 14 14:36:12 2016 From: mjanz at upenn.edu (Janz, Margaret M) Date: Fri, 14 Oct 2016 18:36:12 +0000 Subject: [Rdap] Job: Science and Engineering Librarian and Learning Specialist at Temple University (Philadelphia) Message-ID: Below is the posting for my old job at Temple University in Philadelphia. I can answer questions to interested parties off list. Margaret Janz Scholarly Communication & Data Curation Librarian University of Pennsylvania Van Pelt Library Room 131 Science and Engineering Librarian and Learning Specialist ? Reference and Instructional Services Summary: Make a difference at Temple Libraries. Join our team of subject specialist librarians, serving students, faculty and researchers in our Colleges of Science and Technology and Engineering. We seek an enthusiastic, service-focused colleague eager to engage with our science community to support learning and research. Our new state-of-the-art library building, opening in 2018, is just one reason to explore your future at Temple Libraries. Temple University is a vibrant, urban research university with over 1,700 full-time faculty and a student body of 36,000 that is among the most diverse in the nation. For more information about Temple and Philadelphia, visit http://www.temple.edu/about/. Primary Duties and Responsibilities: Reporting to the Associate University Librarian, the Science & Engineering Librarian provides general reference, specialized research support and instructional programming for students, faculty and staff in biology, bioengineering, chemistry, computer & information science, earth & environmental science, engineering, the mathematical sciences and physics. Serves as library liaison for three or more science and engineering departments. In addition, the Science & Engineering Librarian conducts outreach to a growing number of specialized labs and research centers in the College of Science & Technology. Develops print and web based instructional materials and provides library instruction to students in the assigned subject areas as well as undergraduates in the general education curriculum. As the learning specialist for sciences and engineering, counsels faculty in developing effective information literacy assignments and collaborates with the Information Literacy Coordinator to identify, achieve and assess library-wide learning outcomes. Engages faculty through outreach and promotional activities, including committee participation and attendance at collegial meetings and events. Selects materials for library collections in all formats in support of these academic programs. Maintains awareness of current trends in librarianship, within the sciences and engineering as well as in higher education and related academic fields. Performs other duties as assigned. Required Education and Experience: ALA accredited master?s degree in Library Science. Required Skills and Abilities: *Substantial coursework, library experience or practical lab experience in engineering or science fields, such as biology, physics, chemistry, geology, etc. *Experience designing and delivering learning content and applying information literacy concepts, such as developing learning outcomes and employing assessment techniques, to practice. *Demonstrated ability to provide reference and instructional services. *Must be flexible. *Proficient analytical, organizational, management and communication skills. *Ability to take initiative and meet deadlines. *Ability to work both independently and collegially in a demanding and rapidly changing environment. *Commitment to providing responsive and innovative services to a culturally and racially diverse campus community. Preferred Skills and Abilities: *Experience in a science or engineering academic setting providing reference, consultation or liaison services. *Facility with instruction and information technologies and creative use of technology to enhance learning. *Experience developing and managing science or engineering-related collections in all formats. *Current awareness of issues and trends in public services for academic libraries. *Knowledge of the information needs of relevant disciplines and an understanding of current trends and issues in scholarly publishing. *Science or engineering degree. Compensation: Competitive salary and benefits package, including relocation allowance. Rank and salary will be commensurate with qualifications and experience. To apply: To apply for this position, please visit www.temple.edu, click on Careers At Temple at the bottom of the home page, and reference 16003627. For full consideration, please submit your completed electronic application, along with a cover letter and resume. Review of applications will begin immediately and will continue until the position is filled. Temple University is an Affirmative Action/Equal Opportunity Employer with a strong commitment to cultural diversity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From junus at mail.lib.msu.edu Fri Oct 14 17:59:54 2016 From: junus at mail.lib.msu.edu (Junus, Ranti) Date: Fri, 14 Oct 2016 21:59:54 +0000 Subject: [Rdap] Code4Lib 2017 Call for Proposals Message-ID: <13CEDD3CC20A8D40BC18DD7A7C9135EFB07267FE@mailbox1.lib.msu.edu> Code4Lib 2017 is a loosely-structured conference that provides people working at the intersection of libraries/archives/museums/cultural heritage and technology with a chance to share ideas, be inspired, and forge collaborations. For more information about the Code4Lib community, please visit http://code4lib.org/about/. The conference will be held at the Luskin Conference Center at UCLA http://luskinconferencecenter.ucla.edu/, from March 6, 2017 - March 9, 2017. More information about Code4lib 2017 will be coming soon. We encourage all members of the community to submit a proposal for a prepared talk. Prepared talks should focus on one or more of the following areas: -Projects you've worked on which incorporate innovative implementation of existing technologies and/or development of new software - Tools and technologies - How to get the most out of existing tools, standards, and protocols (and ideas on how to make them better) - Technical issues - Big issues in library technology that are worthy of community attention or development - Relevant non-technical issues - Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc. This year, in order to provide increased opportunities for a diversity of speakers and topics, we'll be soliciting 10, 15, and 20 minute talks. You'll be asked to indicate which talk lengths you would be willing to accommodate for your proposal. We are also considering holding a poster session at this year's conference. If you would be interested in presenting your topic as a poster, please indicate so on the form. https://goo.gl/forms/GbM0jmSdXFkRdHAr2 In addition to "traditional" presentations and posters, we plan to include a panel session this year. If you have a topic you'd like to suggest for a panel, and are willing to work with the Program Committee to organize / recruit for the session, please use the following form. https://goo.gl/forms/q2KbVcO4ntkh6bPp1 As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. The top 10 proposals are guaranteed a slot of their preferred length at the conference. The Program Committee will curate the remainder of the program in an effort to ensure diversity in program content and presenters. Community votes will, of course, still weigh heavily in these decisions. Presenters whose proposals are selected for inclusion in the program will have conference registration slots held for them (up to 2 speakers per talk). In addition, panel participants will have registration slots held. The standard conference registration fee will apply. Proposals can be submitted through November 7, 2016 at midnight PST (GMT-8). Voting will start on November 16, 2016 and continue through December 7, 2016. The URL to submit votes will be announced on the Code4Lib website and mailing list and will require an active code4lib.org account to participate. The final list of presentations will be announced in December. Thank you, The Code4Lib 2017 Program Committee -- Ranti Junus, Systems/Electronic Resources Librarian Library Science Collection & Museum Studies Liaison Michigan State University Libraries 366 W. Circle Dr., East Lansing, MI 48824-1048 +1.517.884.0878 | @ranti From rhmcdona at indiana.edu Mon Oct 17 16:16:47 2016 From: rhmcdona at indiana.edu (McDonald, Robert H.) Date: Mon, 17 Oct 2016 20:16:47 +0000 Subject: [Rdap] =?windows-1252?q?1st_CFP=3A_17th_ACM/IEEE_Joint_Conference?= =?windows-1252?q?_on_Digital_Libraries_=28JCDL_=9117=29?= In-Reply-To: References: Message-ID: <1476735431385.2158@indiana.edu> [Apologies for cross postings] ********************************************************************** 1st Call for Papers 17th ACM/IEEE Joint Conference on Digital Libraries (JCDL ?17) #TOScale #TOAnalyze #TODiscover http://2017.jcdl.org June 19-23, 2017 Toronto, Ontario CA Follow us on: Twitter: https://twitter.com/jcdl2017 ********************************************************************** IMPORTANT DATES January 15, 2017 - Tutorial and Workshop proposal submissions January 29, 2017 - Full paper and short paper submissions February 1, 2017 - Notification of acceptance for tutorials and workshops February 12, 2017 - Panel submissions February 12, 2017 - Poster and demonstration submissions March 20, 2017 - Notification of acceptance for full papers, short papers, panels, posters, and demonstrations April 16, 2017 - Doctoral Consortium abstract submissions April 16, 2017 - Final camera-ready deadline for full papers, short papers April 26, 2017 - Final camera-ready deadline for posters, demonstrations, panels May 1, 2017 - Notification of acceptance for Doctoral Consortium June 19, 2017 - Tutorials and Doctoral Consortium June 19 - 23, 2017 - Main Conference June 22 - 23, 2017 - Workshops AIMS The field of digital libraries has undergone dramatic changes as digital collections grow in scale and diversity. These changes call for novel analytical tools and methodologies for making sense of large amounts of heterogeneous data, for deriving diverse kinds of knowledge, and for linking across different collections and research disciplines. Thus the theme of the 2017 conference is #TOScale #TOAnalyze #TODiscover. Digital libraries must improve outreach efforts, engage diverse communities, and provide scholars and users with effective and flexible access to materials which will in turn empower them to make new observations and discoveries. This year, we particularly invite papers, panels, workshops, and tutorials that present new discovery methods for diverse kinds of collections and datasets (e.g., documents, images, sounds, videos), that apply recent technologies in related fields like machine learning and data mining, and that report on innovative digital library applications that engage diverse communities, facilitate user access, and enable discovery and exploration in all domains including science, art, and the humanities. This year, in addition to the research-oriented program, we are organizing a practitioners? day so experts and practitioners can share their experiences and report on major projects. Practitioner contributions will take the form of posters and demos. Participation is sought from all parts of the world and from the full range of established and emerging disciplines and professions including computer science, information science, web science, data science, digital humanities, librarianship, data management, archival science and practice, museum studies and practice, information technology, medicine, social sciences, education and the humanities. Representatives from academe, government, industry, and others are invited to participate. TOPICS JCDL welcomes submissions from researchers and practitioners interested in all aspects of digital libraries such as: collection discovery and development, hybrid physical/digital collections; knowledge discovery; applications of machine learning and AI; services; digital preservation; system design; scientific data management; infrastructure and service design; implementation; interface design; human-computer interaction; performance evaluation; user research; crowdsourcing and human computation; intellectual property; privacy; electronic publishing; document genres; multimedia; user communities; and associated theoretical topics. Submissions that resonate with JCDL 2017 theme are especially welcome, although we will give equal consideration to all topics in digital libraries. SUBMISSIONS Full papers report on mature work, or efforts that have reached an important milestone, and must not exceed 10 pages. Accepted full papers will typically be presented in 20 minutes with 10 minutes for questions and discussion. Short papers may highlight preliminary results to bring them to the community?s attention. They may also present theories or systems that can be described concisely in the limited space. Short papers must not exceed 4 pages in the conference format. Accepted short papers will typically be presented in 10 minutes with 5 minutes for questions and discussion. Posters permit presentation of late-breaking results in an informal, interactive manner. Demonstrations showcase innovative digital library technologies and applications, allowing you to share your work directly with your colleagues in a high-visibility setting. Proposals for posters or demonstrations should consist of a title, extended abstract, and contact information for the authors, and should not exceed 2 pages in the conference format. Accepted posters and demonstrations will be displayed at the conference. All paper submissions (full/short papers, posters and demos) should use the ACM Proceedings template and are to be submitted in electronic format via the conference's EasyChair submission page [forthcoming-see website for link http://2017.jcdl.org/call-for-papers]. All accepted papers will be published by the ACM as conference proceedings and electronic versions will be included in both the ACM and IEEE digital libraries. ------------ ORGANIZING COMMITTEE GENERAL CO-CHAIRS * Robert H. McDonald, Indiana University Bloomington * Nicholas Worby, University of Toronto Libraries PROGRAM CHAIRS * Cathy Marshall, Texas A&M University * Ian Milligan, Department of History, University of Waterloo * Adam Jatowt, School of Informatics, Kyoto University PROGRAM COMMITTEE TREASURER * Leanne Trimble, University of Toronto Libraries DOCTORAL CONSORTIUM CO-CHAIRS * Jiangping Chen, College of Information, University of North Texas PANEL CHAIRS * Martin Klein, University of California Los Angeles Library * Periklis Andritsos, Faculty of Information, University of Toronto WORKSHOP CHAIRS * Michele C. Weigle, Department of Computer Science, Old Dominion University * Xiaozhong Liu, School of Informatics & Computing, Indiana University ? Bloomington TUTORIAL CHAIRS * Glen Newton, Agriculture & Agri-Food Canada * Kim Pham, University of Toronto ? Scarborough Libraries POSTER & DEMO CHAIRS * Justin Brunelle, MITRE * Emily Maemura, Faculty of Information, University of Toronto PUBLICATIONS CHAIR * Jim Hahn, University of Illinois at Urbana-Champaign Library CONTINUITY ADVISOR * Michael Nelson, Department of Computer Science, Old Dominion University LOCAL ORGANIZATION CHAIRS * Christina Tooulias-Santolin, University of Toronto Libraries PUBLICITY CHAIRS * Jesse Carliner, University of Toronto Libraries * Nattiya Kanhabua, Department of Computer Science, Aalborg University SPONSORSHIP CHAIR * Kyla Everall, University of Toronto Libraries LOCAL ORGANIZERS * University of Toronto Libraries? ********************************** Robert H. McDonald Associate Dean for Research & Technology Strategies Deputy Director-Data to Insight Center, Pervasive Technology Institute Indiana University 1320 East 10th Street Herman B Wells Library 234 Bloomington, IN 47405 Phone: 812-856-4834 Email: rhmcdona at indiana.edu Skype: rhmcdonald ORCID: http://orcid.org/0000-0003-4258-0982 ISNI: http://go.iu.edu/nTM -------------- next part -------------- An HTML attachment was scrubbed... URL: From shorisyl at jmu.edu Thu Oct 20 15:12:04 2016 From: shorisyl at jmu.edu (Shorish, Yasmeen L - shorisyl) Date: Thu, 20 Oct 2016 19:12:04 +0000 Subject: [Rdap] RDAP CFP Message-ID: <104D82DC-402F-4F63-B88C-FB614948EB31@jmu.edu> **Expect cross-posting** The Research Data Access and Preservation (RDAP) Summit, to be held April 19-21, 2017 in Seattle, WA, invites calls for proposals from managers, users, and generators of digital data from all sectors, including industry, academia, government, and cultural heritage centers. RDAP 2017 will focus on the theme ?Meeting challenges in the data world.? RDAP will include panels on the topics of curating difficult data, data reusability, publisher perspectives on data, intellectual property issues surrounding data, and digital humanities data. The planning committee is seeking proposals for short presentations that complement these topics in an additional panel. Potential proposal topics could include: * Representing data (visually, etc?) * Privacy/ethics and data * Data as a commodity * Teaching data information literacy in curricula * The role of data curation in data science * Should data be treated as a collection? * What happens when physical objects are digitized - what kind of stewardship are the digital objects given compared to physical? Please submit proposals via this form by November 20. Questions can be directed to the RDAP Program Chairs, Brianna Marshall (brianna.marshall at wisc.edu) and Yasmeen Shorish (shorisyl at jmu.edu) Thank you! -- Yasmeen Shorish Data Services Coordinator, Assoc. Professor Rose Library 2309 James Madison University MSC 4601 Harrisonburg, VA 22807 540.568.4288 ORCID: 0000-0002-4155-8241 http://works.bepress.com/yasmeen_shorish/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruth.duerr3 at gmail.com Mon Oct 24 13:40:45 2016 From: ruth.duerr3 at gmail.com (Ruth Duerr) Date: Mon, 24 Oct 2016 11:40:45 -0600 Subject: [Rdap] The Future of Careers in Scholarship Message-ID: <162CECD0-BDC0-4085-BA01-D92116E5750B@gmail.com> A non-text attachment was scrubbed... Name: Unconference Flyer Cambridge 2016.pdf Type: application/pdf Size: 1001150 bytes Desc: not available URL: From cmmorris at duraspace.org Tue Oct 25 08:34:20 2016 From: cmmorris at duraspace.org (Carol Minton Morris) Date: Tue, 25 Oct 2016 08:34:20 -0400 Subject: [Rdap] ANNOUNCEMENT: DSpace 6 is Now Available! Message-ID: *FOR IMMEDIATE RELEASE* October 25, 2016 Read it online: bit.ly/2eN5YQt *NOW AVAILABLE: DSpace 6.0?API Enhancements and New Features* *From Tim Donohue, DSpace Tech Lead for DuraSpace, on behalf of the DSpace developers* I would like to formally announce that DSpace 6.0 is now available! DSpace 6 provides significant API enhancements and new features to the DSpace platform. - DSpace 6.0 can be downloaded immediately from: https://github.com/DSpace/DSpace/releases/tag/dspace-6.0 - 6.0 Release notes are available at: https://wiki.duraspace.org/ display/DSDOC6x/Release+Notes - In addition, you are welcome to try out DSpace 6 on http://demo.dspace.org/ and continue to provide feedback on this major release. DSpace 6 features an enhanced configuration system, enhanced file storage plugins, and new quality control / healthcheck reporting features (via REST API and via email). In addition, DSpace 6 has an eye on the future, with a major Java API refactor that adds support for both UUIDs and Hibernate in our database layer. Like its predecessor, DSpace 6 continues to strive to simplify your upgrade process by automatically updating your database to 6.x compatibility (from any prior DSpace version). ENHANCED CONFIGURATION In DSpace 6, most configurations (those in *.cfg files) automatically reload themselves. This means you no longer need to restart your webserver every time you wish to modify a backend configuration. In addition, a new "local.cfg" file has been added to the codebase. This local.cfg gives you the power to override any configuration (from any *.cfg file) by simply copying it into your custom local.cfg file. This means you no longer need to manage all your configurations in separate files. Instead, you can simply copy all your customizations into your local.cfg, and easily take them with you in future upgrades. More information on this feature may be found at https://wiki.duraspace.org/ display/DSDOC6x/Configuration+Reference and in the Release Notes. ENHANCED FILE STORAGE In DSpace 6, the file (bitstream) storage plugins have received a major refactor, including support for Amazon S3 file storage. Additional file storage plugins may be built in the future (or you can build your own). More information on this feature is available athttps://wiki.duraspace.org/ display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore HEALTHCHECKS AND QUALITY CONTROL Want to receive a regular email report of how large your DSpace is? Want to be notified of oddities in your logs (exceptions/warnings) before they cause more severe issues? Then take a look at the new, configurable email healthcheck reports that come with DSpace 6. More information is available at https://wiki.duraspace.org/display/DSPACE/Healthcheck+reports Ever wish you could dig deeper into your site's metadata or files (bitstreams) without having to write database (SQL) queries? What if you could find metadata or file oddities before your users reported them? The DSpace 6 REST API now features a Quality Control reporting interface, along with a sample (HTML) client user interface. More information on this feature is available at https://wiki.duraspace.org/ display/DSDOC6x/REST+Based+Quality+Control+Reports The sample HTML clients can be tried out on our demo site (Sample Query client: https://demo.dspace.org/rest/static/reports/query.html and Sample Quality Control client: https://demo.dspace.org/rest/static/reports/index.html). REFACTORED JAVA API While obviously not a customer-facing feature, DSpace 6 includes a major refactor to the underlying Java API to make it more secure, easier to maintain and to help better support future roadmap goals. Key among these changes is the addition of Hibernate (http://hibernate.org/) to manage database logic and simplify our support of both PostgreSQL and Oracle backends. We've also added UUID (Universally Unique Identifier) support for all objects. Finally, the Java API itself has been modularized into three distinct layers, which provide business logic ("Service" layer), database access (or DAO) layer, and individual object access layer (setters/getters for each object). For most users, these Java API changes (and necessary database upgrades) will be seamless. However, if you have made major site customizations (involving adding new or custom Java API calls), you will need to update your local code to support the new 6.x Java API. Much more information on the extent of these changes is available at https://wiki.duraspace.org/ display/DSPACE/DSpace+Service+based+api OVERVIEW OF ALL NEW FEATURES AND IMPROVEMENTS IN 6.0 - Java API refactor, featuring Hibernate and UUIDs - Enhanced (reloadable) configuration system, featuring a new local.cfg configuration file - Enhanced file storage plugins, featuring support for Amazon S3 - Configurable site healthchecks via email - XMLUI framework for metadata import from external sources, featuring support for PubMed imports - XMLUI export of search results to CSV (for batch editing) - XMLUI extensible administrative control panel - REST API Quality Control Reports, along with sample HTML clients and CSV export (for batch editing) - REST API support for additional authentication methods (e.g. LDAP, etc) - All searches default to boolean AND. - Enhanced indexing for searches (Excel is now searchable, as well as right-to-left text in PDFs) - OAI-PMH adds compliance for OpenAIRE 3.0 guidelines for literature repositories For a list of all new features in DSpace 6, please see the Release Notes: https://wiki.duraspace.org/display/DSDOC6x/Release+Notes DOCUMENTATION The DSpace 6.0 Documentation is available online at https://wiki.duraspace.org/display/DSDOC6x/ Upgrade instructions (for any previous release of DSpace) are available at: https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace 6.0 ACKNOWLEDGMENTS The DSpace application would not exist without the hard work and support of the community. Thank you to the many developers who have worked very hard to deliver all the new features and improvements. Also thanks to the users who provided input and feedback on the development, as well those who participated in the testathons. We especially would like to thank the 6.0 Release Team, which consisted of Pascal-Nicolas Becker (Technische Universit?t Berlin / The Library Code), Tim Donohue (DuraSpace), Kevin Van de Velde (Atmire), and numerous other Committers who volunteered their time. A detailed listing of all known people/institutions who contributed directly to DSpace 6.0 is available in the Release Notes. If you contributed and were accidentally not listed, please let us know so that we can correct it! https://wiki.duraspace.org/display/DSDOC6x/Release+Notes For DSpace 6.0, we had a total of 73 individuals contributed code, bug reports, and bug fixes. A big thanks goes out to everyone who participated. We hope you'll continue to be a valuable addition to the DSpace community for the next release and beyond! As always, we are happy to hear back from the community about DSpace. Please let us know what you think of 6.0! -------------- next part -------------- An HTML attachment was scrubbed... URL: From aneeser at umich.edu Tue Oct 25 16:55:49 2016 From: aneeser at umich.edu (Amy Neeser) Date: Tue, 25 Oct 2016 16:55:49 -0400 Subject: [Rdap] Upcoming RDAP and ASIS&T webinar series Message-ID: As a member of the RDAP 2017 planning committee, I am pleased to announce the following webinar series: *Creating a Campus-wide Research Data Services Committee: The Good, The Bad, and The?* November 15 & November 17, 12pm-1pm EST Join us for this two-part webinar series about developing cross-campus partnerships in order to develop institution-wide data services. Part 1 focuses on establishing stakeholders and building partnerships. Part 2 focuses on launching the service, including project management, collaboration, and program development. This series is sponsored by Research Data Access and Preservation (RDAP) and hosted by the Association for Information Science and Technology (ASIS&T). More information and registration Amy Neeser Research Data Curation Librarian Deep Blue Data Coordinator University of Michigan Libraries 260E Hatcher Graduate Library South 734-764-2203 | aneeser at umich.edu ORCID: 0000-0003-2523-5079 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmmorris at duraspace.org Wed Oct 26 09:40:00 2016 From: cmmorris at duraspace.org (Carol Minton Morris) Date: Wed, 26 Oct 2016 09:40:00 -0400 Subject: [Rdap] CfP REMINDER: OR2017 Proposals Due on Nov 20 Message-ID: *==apologies for cross posting==* *Call for Proposals for Open Repositories 2017 * Read it online: http://or2017.net/call-for-proposals/ The Twelfth International Conference on Open Repositories, OR2017, will be held on June 26th-30th, 2017 in Brisbane, Australia. The organisers are pleased to issue a call for proposals to the program, with submissions due by 20 November 2016. In 2017 the Open Repositories conference returns to Australia, where the Open Repositories journey started in Sydney 2006. Repositories have come a long way in the intervening years, having emerged as critical systems for managing, preserving and sharing intellectual, artistic and scientific output. As such, repositories have found a firm placing within scholarly processes and becoming an integral vehicle to moving towards true Open Science. The OR community has established itself as an important contributor in this space, something we would like to emphasise in Brisbane by promoting the community?s ability to always stay at the forefront of development of both infrastructure and good practice. *OR2017 will provide an opportunity to:* ? showcase innovative repository services as well as innovations in functionality and user experience of repository software; ? introduce innovative uses of repositories, for example to accommodate new types of content, serve new groups of users, or achieve new goals; ? analyse drivers for repository innovation, including evolving technologies, changes in scholarly communication processes, as well as policies around open access to research outputs at institutional, national and international levels; and ? explore and highlight innovation in the wider ecosystem around repositories. We welcome proposals on these ideas, but also on other theoretical, practical, technical, organisational or administrative topics related to repositories. *Key Dates:* ? 20 November 2016: Deadline for submissions ? 14 December 2016: Deadline for Scholarship applications ? 03 February 2017: Submitters notified of acceptance (except Interest Groups) ? 03 February 2017: Registration opens ? 10 February 2017: Submitters notified of acceptance to Interest Groups ? 10 February 2017: Scholarship winners notified ? 26-30 June 2017: OR2017 conference FAQs about OR2017: http://or2017.net/frequently-asked-questions/ Website: http://or2017.net Twitter: http://www.twitter.com/OR2017aus Tag: #OR2017 Facebook: https://www.facebook.com/ORConference/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From junus.msulibraries at gmail.com Thu Oct 27 12:55:10 2016 From: junus.msulibraries at gmail.com (Ranti Junus) Date: Thu, 27 Oct 2016 12:55:10 -0400 Subject: [Rdap] Reminder: Code4Lib 2017 Call for Proposals Message-ID: <01cf01d23072$e17e1ff0$a47a5fd0$@gmail.com> Reminder: Code4Lib 2017 proposals submission closes on November 7th. Thank you. ranti. > -----Original Message----- > From: Asis-l [mailto:asis-l-bounces at asis.org] On Behalf Of Junus, Ranti > Sent: Friday, October 14, 2016 6:00 PM > Subject: [Asis-l] Code4Lib 2017 Call for Proposals > > Code4Lib 2017 is a loosely-structured conference that provides people > working at the intersection of libraries/archives/museums/cultural heritage > and technology with a chance to share ideas, be inspired, and forge > collaborations. For more information about the Code4Lib community, please > visit http://code4lib.org/about/. > > The conference will be held at the Luskin Conference Center at UCLA > http://luskinconferencecenter.ucla.edu/, from March 6, 2017 - March 9, > 2017. More information about Code4lib 2017 will be coming soon. > > We encourage all members of the community to submit a proposal for a > prepared talk. Prepared talks should focus on one or more of the following > areas: > > -Projects you've worked on which incorporate innovative implementation of > existing technologies and/or development of new software > - Tools and technologies - How to get the most out of existing tools, > standards, and protocols (and ideas on how to make them better) > - Technical issues - Big issues in library technology that are worthy of > community attention or development > - Relevant non-technical issues - Concerns of interest to the Code4Lib > community which are not strictly technical in nature, e.g. collaboration, > diversity, organizational challenges, etc. > > This year, in order to provide increased opportunities for a diversity of > speakers and topics, we'll be soliciting 10, 15, and 20 minute talks. You'll be > asked to indicate which talk lengths you would be willing to accommodate for > your proposal. We are also considering holding a poster session at this year's > conference. If you would be interested in presenting your topic as a poster, > please indicate so on the form. > https://goo.gl/forms/GbM0jmSdXFkRdHAr2 > > In addition to "traditional" presentations and posters, we plan to include a > panel session this year. If you have a topic you'd like to suggest for a panel, > and are willing to work with the Program Committee to organize / recruit for > the session, please use the following form. > https://goo.gl/forms/q2KbVcO4ntkh6bPp1 > > As in past years, the Code4Lib community will vote on proposals that they > would like to see included in the program. The top 10 proposals are > guaranteed a slot of their preferred length at the conference. The Program > Committee will curate the remainder of the program in an effort to ensure > diversity in program content and presenters. Community votes will, of > course, still weigh heavily in these decisions. > > Presenters whose proposals are selected for inclusion in the program will > have conference registration slots held for them (up to 2 speakers per talk). > In addition, panel participants will have registration slots held. The standard > conference registration fee will apply. > > Proposals can be submitted through November 7, 2016 at midnight PST > (GMT-8). Voting will start on November 16, 2016 and continue through > December 7, 2016. The URL to submit votes will be announced on the > Code4Lib website and mailing list and will require an active code4lib.org > account to participate. The final list of presentations will be announced in > December. > > > Thank you, > The Code4Lib 2017 Program Committee > > -- > Ranti Junus, > Systems/Electronic Resources Librarian > Library Science Collection & Museum Studies Liaison Michigan State > University Libraries > 366 W. Circle Dr., East Lansing, MI 48824-1048 > +1.517.884.0878 | @ranti >