Associate Curator of Indigenous History

We need to output HTML fragment with sections: About the role? The posting includes "Brief Position Overview" and "General Statement". We need to use

for section headings like About the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have: - About the role: could be "Brief Position Overview" and "General Statement". Could combine into About the role. - Responsibilities: "Duties and Responsibilities" section. - Requirements: "Required Qualifications – Experience, Education, Knowledge & Skills". Also maybe "Preferred Qualifications" could be under Qualifications? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have to decide which sections to include. We have content for: - About the role: yes. - Responsibilities: yes. - Qualifications: we have Required Qualifications and Preferred Qualifications. Could put under Qualifications. - Skills: maybe part of qualifications; but we could also have a Skills section if we extract skills from text. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine qualifications and skills into one Qualifications section. - Benefits: posting mentions "Benefits Eligible Eligible". Actually line: "Benefits Eligible Eligible". That seems like a metadata: "Benefits Eligible". Not specific benefit details. No actual benefits described. So we should NOT create Benefits section because no specific content. - Pay: posting includes "Salary $60,000 - $65,000 annually, commensurate with experience, education, and qualifications". That's pay info. So we can create Pay section with that sentence. - Schedule: posting includes "Appointment Type Professional Contract Term Fiscal Year Semester". Also maybe FTE 1.0. Not explicit schedule like full-time, part-time. Could infer full-time. But we should not create Schedule unless posting actually states them. It does state FTE 1.0 (full-time) and Contract Term Fiscal Year Semester. That's schedule info. Could include Schedule section with that. However we need to avoid filler like "not specified". We have actual info: FTE 1.0, Contract Term Fiscal Year Semester. So we can include Schedule. But we need to check if we should include "About the role" heading. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. We must not repeat job title as heading. Good. We must not put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... combined overview ...

Responsibilities

• ... each duty ...

Qualifications

... required and preferred qualifications ...

Pay

Salary $60,000 - $65,000 annually, commensurate with experience, education, and qualifications.

Schedule

FTE 1.0; Contract Term: Fiscal Year Semester.

We need to ensure we preserve all substantive information from the posting. Let's extract details. About the role: combine Brief Position Overview and General Statement. Brief Position Overview: "The Associate Curator of Indigenous History leads Museum of the Rockies’ efforts to thoughtfully and respectfully share the histories, cultures, and contemporary experiences of Indigenous peoples of the Northern Rockies. Working closely with Tribal Nations, advisors, artists, scholars, and museum colleagues, this position will lead the development of MOR’s new long-term Indigenous cultures exhibition, and support related exhibitions, research, collections, educational programs, and community initiatives. The Associate Curator will cultivate reciprocal relationships with Tribal partners, coordinate culturally appropriate review and permissions, administer the museum’s Indigenous Advisory Board, develop agreements with partner organizations, manage project budgets, and supervise Indigenous Relations Program staff. The successful candidate will be a collaborative and skilled communicator who understands that meaningful relationships and institutional change require trust, accountability, and sustained commitment." General Statement: includes museum description, visitor stats, strategic plan, new exhibit Under a Common Sky, working with Native Nations, museum is college-level division of MSU, independent nonprofit, Smithsonian Affiliate, accredited AAM museum, repository for state and federal fossils, location details, facilities, etc. We need to preserve all that. We'll combine into a few paragraphs. Responsibilities: list each duty from "Duties and Responsibilities". Let's extract bullet points: - Work with the Cultural History team to manage American Indian curatorial projects, including communication with exhibit team members, setting project timelines and achievable outcomes; organizing agendas, and other functions as necessary. - Function as the project lead on MOR’s new long-term exhibit on Indigenous Cultures of the Northern Rockies, Under a Common Sky, and serve as the key point of contact for exhibit Tribal Advisory Committees. - Perform research as needed to support museum exhibits and programs. - Manage the budget for the American Indian Exhibits/Collections. - Sit on the Collections Committee. - Collaborate internally with the Cultural History and Education teams to develop exhibits, programming, interpretive materials, and other museum activities that share Indigenous topics in a thoughtful and culturally appropriate manner, including coordinating appropriate Tribal review and documenting feedback, permissions, and follow-up. - Foster relationships with Native Nations and Tribal representatives by working with leaders, Tribal Historic Preservation Officers, elders, artists, and others. - Build an understanding of and communicate ways that the museum can better support the region’s Native Nations and people. - Collaborate with the museum’s Education Department and other departments to develop and implement Indigenous programing at the museum and in various communities. - Coordinate with MOR staff to administer the MOR Indigenous Advisory Board. - Participate as a museum staff team member on various projects, events, and committees. - Draft Memorandums of Agreements or Understandings with Tribes or other organizations, to clearly guide future public history efforts, including exhibits and programming. - Train MOR staff, and Supervise the one full time staff member, the Indigenous Relations Program Lead, and one part time staff member, the Curatorial Assistant for Indigenous History. - Implement MOR Indigenous Relations Programs activities and develop new strategies in collaboration with the Indigenous Relations Program Lead to fit the changing needs of MOR and tribes. We need to preserve all; we can put each as

. Qualifications: Required Qualifications – Experience, Education, Knowledge & Skills: - A bachelor’s degree in a field appropriate for the position such as Museum studies, education, Native American studies, anthropology, history, etc. - Understanding of Native American histories and cultures and expertise in contemporary tribal policies and relations. - Demonstrated strong writing and research skills. Preferred Qualifications – Experience, Education, Knowledge & Skills: - Experience building and maintaining equitable and reciprocal relationships with Tribal members and/or tribal governmental representatives in the Northern Rocky Mountain region. - Experience working in a museum or educational environment. - Knowledge of Indigenous material culture and the ability to apply it to thoughtfully and sensitively to tell appropriate Indigenous public history stories. - Advanced degree in Museum Studies, History, Native American Studies, Education, or Communication. Also "The Successful Candidate Will" list includes many attributes; those could be considered Skills or Qualities. But we already have Qualifications section; we could include those as part of Qualifications or maybe a Skills section. However instruction: prefer few substantive sections. We could put those under Qualifications as well, but they are more about successful candidate attributes. Could treat as Skills. But we already have Qualifications; we could add a Skills section for those. However we risk many thin sections. Let's see: The Successful Candidate Will list includes: - Attention to detail and deadlines. - Act as an ambassador of Museum of the Rockies, believing in the museum’s mission and values, and promoting long-lasting relationships based on trust and respect. - Interact with others in a respectful, thoughtful, patient, and trustworthy manner. - Demonstrate an ability to work in a complex, multifaceted organization and an appreciation that building relationships and decolonization will take time. - Be an excellent communicator with ability to work independently and with teams. - Maintain an enthusiastic and curious attitude about museum work and embrace museum best practices. - Demonstrate significant research and public programming skills. - Have knowledge and appreciation of traditional and contemporary Indigenous art and made objects, music, or other expressions of Native artists. - Communicate and work collaboratively with a various range of groups and institutions, including schools, museums, non-profits, and Tribal Nations. These are skills/attributes. Could be placed under Skills section. But we already have Qualifications; maybe we can combine Qualifications and Skills into one section called Qualifications (includes both required/preferred and successful candidate attributes). That would be substantive. Thus Qualifications section will contain all those bullet points. Pay: we have salary line. Schedule: we have FTE 1.0, Contract Term Fiscal Year Semester, maybe also Appointment Type Professional. We'll include those. Now we need to ensure we do not include boilerplate like EEO, etc. Remove those. Also remove "Position Details Position Information Announcement Number STAFF - VA - 27087 For questions regarding this position, please contact: Siriana Lundgren siriana.lundgren@montana.edu Classification Title Program/Project Lead Working Title Associate Curator of Indigenous History" - we should not repeat job title as heading, but we can include metadata in a short paragraph maybe? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph at top with the position info like "Announcement Number STAFF - VA - 27087; Contact: Siriana Lundgren (siriana.lundgren@montana.edu); Classification Title: Program/Project Lead; Working Title: Associate Curator of Indigenous History; Position Number: 4C0537; Department: Museum of the Rockies; Division: Museum of the Rockies; Appointment Type: Professional Contract Term: Fiscal Year Semester; FTE: 1.0; Benefits Eligible; Salary: $60,000 - $65,000 annually; etc." But we already have Pay and Schedule sections; we could still include a short paragraph for other metadata like Announcement Number, Contact, Classification Title, Working Title, Position Number, Department, Division, etc. However we must not repeat job title as heading; we can include it in paragraph. But we need to preserve ALL substantive information. So we should include that metadata somewhere. The instruction says fold minor metadata into a short

or drop it. So we can include a short paragraph at the beginning with those details. Thus output:

Announcement Number: STAFF - VA - 27087. Contact: Siriana Lundgren (siriana.lundgren@montana.edu). Classification Title: Program/Project Lead. Working Title: Associate Curator of Indigenous History. Position Number: 4C0537. Department: Museum of the Rockies. Division: Museum of the Rockies. Appointment Type: Professional. Contract Term: Fiscal Year Semester. FTE: 1.0. Benefits Eligible.

Then sections. But note we already have Pay and Schedule sections; we might duplicate FTE and Contract Term if we also put them in metadata. Better to keep metadata minimal: maybe just Announcement Number, Contact, Classification Title, Working Title, Position Number, Department, Division. Then Pay and Schedule sections cover salary and FTE/contract. Thus metadata paragraph: Announcement Number, Contact, Classification Title, Working Title, Position Number, Department, Division. Now we need to ensure we don't include any boilerplate like EEO, scam warning, etc. Now craft