Jobs · OTHR · California

Health Sciences Librarian

Marshall B. Ketchum University · Fullerton, CA · 1 mo ago
OTHRFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. No Pay or Schedule sections because not mentioned. Benefits is present. Also maybe "About The University" could be considered "About the role"? Actually "About the role" is generic; we have description of role. Could use "About the role" heading for the introductory paragraph(s). Then "Responsibilities" for essential duties. Then "Qualifications" maybe combine required and preferred? There's "Qualification Requirements" and "Education And/Or Experience". Could treat as "Requirements" and "Qualifications"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content: description of role (enthusiastic, innovative...). That's About the role. Essential Duties And Responsibilities -> Responsibilities. Qualification Requirements -> Requirements (maybe includes required knowledge). Also there is "Preferred" etc. Could be Qualifications. Education And/Or Experience could be Qualifications as well. But we can split: Requirements (required) and Qualifications (preferred + education). However we must not create thin sections; better to combine into one Qualifications section that includes required, preferred, education. Skills: we have specific skills like proficiency with search techniques, HTML/CSS, LibGuides, ILL systems, etc. Could be Skills. Benefits: present. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; not invent or summarize away detail. Must keep details like specific programs, committees, tasks, etc. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. Thus we need to convert paragraphs into

    and lists into

    • . We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement, non-discrimination statement; we should remove those. Also "See our website under Employment for more details regarding benefits of working for MBKU (www.ketchum.edu)." That's part of benefits but maybe we keep benefits description but can drop the URL? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The URL is substantive? It's a reference for more details; could be considered boilerplate? It's a link to benefits details; maybe we keep it as part of benefits? It's not essential but it's a detail. However it's a reference to website; could be considered navigation? I'd keep it as part of benefits description but maybe it's okay. We must not include the equal opportunity employer statement etc. So remove those paragraphs. Now craft HTML. Structure:

      About the role

      Marshall B. Ketchum University seeks an enthusiastic, innovative, and collaborative professional to serve as its Health Sciences Librarian. The Health Sciences Librarian serves as the Library’s primary instructor, developing and delivering engaging information literacy classes, research sessions, and clinical support across MBKU’s health science programs. The Health Sciences Librarian is also responsible for fostering strong relationships through outreach initiatives across MBKU departments, as well as participating in the advancement of the health sciences library profession and other communities of professional practice. The successful candidate will demonstrate genuine enthusiasm for teaching and healthcare, a commitment to student success and professionalization, and enjoys working as part of a collaborative team.

      Responsibilities

      • Serve as the Pharmacy Librarian for the College of Pharmacy, and as the main point of contact for instructional needs for all programs, including: the School of Physician Assistant Studies (SPAS) and Doctor of Medical Science (DMSc), Southern California College of Optometry (SCCO), and Interprofessional Education (IPE).
      • Attend monthly Pharmacy meetings and participate in academic committees such as AI, IDEA and IPE.
      • Provide library instructional services including traditional classroom and active learning methods, research consultations, and literature searching, among other activities.
      • Provide one-on-one teaching sessions and specialized search assistance; build relationships with faculty, staff, and students that support all research endeavors.
      • Assist library patrons with reference and informational needs.
      • Provide copyright guidance, following best practices and utilizing the Copyright Clearance Center, citation management, and support with EndNote.
      • Develop outreach activities and communication to promote library programming, resources, and services.
      • Provide updates and monitor social media accounts such as Instagram.
      • Serve on library, university, and professional committees.
      • Assist Director with collection development. Assess relevance and potential application and utility of new and updated health science and medical databases.
      • Participate and present at professional library events and conferences, seminars, and network committees; read professional literature; attend and participate in staff meetings, campus professional development and safety training.
      • Manage the library in the absence of the Director. This includes supervising, training, and monitoring student workers.
      • Complete special projects and assigned tasks.
      • The library team works cooperatively, is cross-trained, and shares responsibility for certain tasks such as:
        • Archives/Exhibits/Displays: developing and arranging new exhibits for library displays on campus and online using tools such as Seeklight and JSTOR’s online repository.
        • Binding: preparing Faculty Books and repairing damaged items.
        • Cataloging: preparing bibliographic records, using bibliographic utilities, ordering and processing new resources for online or print reserves.
        • Circulation: proactively monitoring the front desk to support faculty, staff, and students, and tasks such as maintaining circulation records and equipment, checking items in and out.
        • Content Management/Social Media: creating and updating the library website and LibGuides, instructional materials, and web tutorials. Record and edit tutorials using screen capture software. Provide original content and post to Social Media outlets.
        • Interlibrary Loan/Table of Contents distribution: processing and receiving requests for items the library borrows from other institutions using DOCLINE and disseminating TOCs to faculty.
        • Statistics: collecting and analyzing usage statistics of library resources, designing and conducting assessments of services for MBKU and ACRL using survey programs such as Qualtrix.
      • Other duties as assigned.
      Now Qualifications section: combine required, preferred, education. We need to use
      • for list. We'll have prose maybe? The qualification requirements paragraph: "To complete this job successfully, an individual must be able to perform each duty satisfactorily. The requirements listed below are representative of the knowledge, skills and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's prose; we can put in

        . Then list required knowledge/skills. Then "Preferred" list. Then "Education And/Or Experience" list. We could combine into one list with subheadings? But we must use

        • for any list; we can have multiple lists. Thus:

          Qualifications

          To complete this job successfully, an individual must be able to perform each duty satisfactorily. The requirements listed below are representative of the knowledge, skills and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

          Required

          • Proficient knowledge and demonstrate competency in library ethics and professional standards.
          • Experience teaching library instruction sessions.
          • Ability to work well in a team environment.

          Preferred

          • Certification with Academy of Health Information Professionals (AHIP).
          • Proficiency with search techniques across a variety of health sciences and biomedical resources such as in-depth experience with PubMed and Clinical Key.
          • Basic knowledge of HTML and CSS, and experience using content management software such as LibGuides.
          • Experience with ILL systems such as DOCLINE, vendor management systems such as EBSCO/GOBI, and Library Management Systems such as Koha and new technological processes, trends, equipment, digital resources and databases.

          Education and/or Experience

          • Master’s degree in library science (M.L.I.S.) or equivalent from an ALA accredited library school.
          • Two to four years of relevant experience and/or training or equivalent combination of education and experience.
          But we used

          headings which are not allowed per instruction? The instruction only mentions using

          for section headings. It didn't forbid other headings, but to be safe we could avoid extra headings and just incorporate into lists with prose preceding each list. However we need to keep structure clear. Could use

          Required:

          then list. That's okay. Thus:

          Qualifications

          To complete this job successfully, an individual must be able to perform each duty satisfactorily. The requirements listed below are representative of the knowledge, skills and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

          Required:

          • Proficient knowledge and demonstrate competency in library ethics and professional standards.
          • Experience teaching library instruction sessions.
          • Ability to work well in a team environment.

          Preferred:

          • Certification with Academy of Health Information Professionals (AHIP).
          • Proficiency with search techniques across a variety of health sciences and biomedical resources such as in-depth experience with PubMed and Clinical Key.
          • Basic knowledge of HTML and CSS, and experience using content management software such as LibGuides.
          • Experience with ILL systems such as DOCLINE, vendor management systems such as EBSCO/GOBI, and Library Management Systems such as Koha and new technological processes, trends, equipment, digital resources and databases.

          Education and/or Experience:

          • Master’s degree in library science (M.L.I.S.) or equivalent from an ALA accredited library school.
          • Two to four years of relevant experience and/or training or equivalent combination of education and experience.
          Now Skills section: we have many specific skills mentioned in responsibilities and qualifications; but we could create a Skills section pulling out specific technical skills: proficiency with search techniques, HTML/CSS, LibGuides, ILL systems (DOCLINE), vendor management (EBSCO/GOBI), Library Management Systems (Koha), copyright guidance, EndNote, social media (Instagram), screen capture software, Qualtrix, Seeklight, JSTOR, etc. However many of these already appear in qualifications or responsibilities. To avoid duplication, we could still create a Skills section but ensure we don't repeat same content verbatim? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we create a Skills section, we must include those skills somewhere; they already appear in responsibilities and qualifications. Duplicating might be okay but could be considered redundant. However we could decide not to create a separate Skills section if the skills are already covered under Qualifications and Responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we omit Skills section. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Now Benefits section: we have benefits description. We need

Similar jobs