Research Data Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Job" then details. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions, duplicated lines. We need to extract content. Let's parse. Job title: "CENTER FOR TRANSPORTATION STUDIES RESEARCH DATA ANALYST". Not to repeat as heading. We have sections: - About The Job: includes description of AO, purpose, relationships. Could map to "About the role". We'll include that. - Primary Responsibilities: broken down into percentages with bullet-like sentences. We'll put under Responsibilities. - Qualifications: Required Qualifications and Preferred Qualifications. We'll put under Qualifications (maybe also Skills?). The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "Requirements" maybe similar to Qualifications? But we have both Required and Preferred. Could put Required under Requirements, Preferred under Qualifications? Or combine. The instruction: Use headings for those categories if content exists. We'll include sections that have content. We have Pay And Benefits section with pay range and benefits description. So we need Pay and Benefits sections. Also Schedule: there is Time Appointment and Work Profile details. That's schedule info. So we include Schedule. We also have "About The Department" which could be part of About the role? Might be extra but we can include under About the role or maybe a separate section? Not in list. Probably we incorporate into About the role. We need to remove boilerplate: Diversity, Employment Requirements, About University Of Minnesota, etc. Also remove "How To Apply", "Priority Review", etc. We must preserve all substantive information: that includes details about responsibilities percentages, qualifications, pay range, benefits list, work profile details, etc. We need to format using

headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what constitutes a list. For responsibilities we have bullet-like sentences with percentages. Could treat each responsibility as list item. For qualifications we have required and preferred qualifications each as sentences; could be list. For benefits we have a list of benefits items. We need to ensure we don't repeat job title as heading. No Job ID/requisition numbers as headings. Let's extract substantive content. From "About The Job" paragraph: "The Accessibility Observatory or AO (https://access.umn.edu), a CTS research program, is a leading national resource for the research and application of access to destinations data to transportation system planning and evaluation. This position will support the Observatory’s National Access Evaluation project as well as other research projects related to destination access, transportation planning, and land use planning." Then "Purpose Of Position": "The Research Data Analyst will assist with the analysis, data sharing, communication, and data management of the Center’s AO program. This includes delivering analysis and evaluation projects; communicating research results; creating and supporting data tools for sponsors and the public; supporting business development activities; and assisting with program management and administration." Then "Relationships": "Research Data Analyst will report to the director of the Accessibility Observatory. Two other full-time research staff and one to three graduate research assistants make up the AO staff." We can combine into prose under About the role. Now Responsibilities: list with percentages. We have: 40% Data Analysis - Deliver analysis and evaluation projects for the AO program by processing and analyzing existing spatially explicit data on access to destinations; creating, improving, and using software and scripting tools for analysis of geospatial data; and matching end product summaries and graphics to question of interest around the intersection of transportation and land use. - Respond to research inquiries and data requests. - Maintain records of research data and results. 30% Tools for Spatial Data Communication - Apply data visualization best practices to translate complex transportation research concepts and findings into usable, accessible static and interactive digital content for diverse audiences. - Create digital tools to share large datasets and derived maps and statistics, with focus on external partner use cases. - Explore and test alternative software for best match with data structure, type, and user needs. - Iteratively develop tools with internal and external stakeholders. - Create supporting documentation and example tutorials of tool use. 15% Communication & Outreach - Present and communicate complex information in a clear, accessible way to various audiences, including transportation agency planners and engineers, policymakers, other researchers, students, and the public. - Transfer research results into practice by presenting stories of analysis at conferences and agency meetings. - Provide support to business development activities that attract funding for access-related research by identifying funding opportunities; facilitating connections with potential research partners; and communicating and promoting AO expertise. 10% Administration & Project Management - Contribute as a team member in the administration and management of AO projects and initiatives. - Participate in the strategic planning process and lead and/or participate in the delivery of tactics. - Utilize project and software management tools to assist the AO director and Lead Researcher in program and process development, project planning and progress tracking, staffing strategies and assignments, and other group management functions as needed. 5% Other duties at CTS - Contribute as a team member in the administration of CTS and AO programs. - Assist in the design and implementation of Center-wide initiatives and special projects as needed. We can treat each bullet as

• . Could also group by percentage headings but not required. We'll just list all responsibilities as list items. Now Qualifications: Required Qualifications: "Bachelor's degree with a major in Geography, Engineering, Urban Planning, Analytics, Data Science, Statistics, Biology, Ecology, or related field, plus two years of experience; or an equivalent combination of education and relevant experience to total 6 years." Preferred Qualifications: list bullet points: - Master’s degree in a related field and two years of experience delivering or supporting transportation and land use research projects. - Project management and software development version control (e.g. Git and GitHub) experience. - Experience using data and geospatial analysis software such as: ArcGIS, QGIS, SQL databases, Python, R. - Experience using cloud computing resources such as AWS or Azure. - Proven ability to communicate complex issues in a concise and thoughtful manner. - The successful candidate will also be resilient, curious, and nimble, and able to thrive in a research environment where thoughtfulness and attention to detail are valued. We could split into Requirements (required) and Qualifications (preferred) or Skills. But we have headings: Requirements, Qualifications, Skills. We could put Required under Requirements, Preferred under Qualifications, and maybe Skills under Qualifications? But we have separate Skills heading; we could put the software/experience items under Skills. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Required and Preferred into Qualifications section. But we have also Skills; we could put technical skills under Skills. Let's think. We have Required Qualifications (education/experience). Preferred Qualifications (additional). Could treat both as Qualifications. Then Skills could be derived from the preferred list (software, version control, communication). But to avoid thin sections, maybe we just have Qualifications section containing both required and preferred as list items. And we could omit Skills section if no distinct skills list beyond that. However we have explicit skills like "Experience using data and geospatial analysis software such as: ArcGIS, QGIS, SQL databases, Python, R." That's a skill. Could be placed under Skills. But we need to follow instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if we have content. We'll decide: - About the role: prose from About The Job + Purpose + Relationships. - Responsibilities: list of duties. - Requirements: Required Qualifications (education/experience). - Qualifications: Preferred Qualifications (maybe also include some skills? but we have Skills heading separate). - Skills: technical skills (software, version control, cloud, communication ability). Could also include "Proven ability to communicate complex issues..." etc. - Benefits: list of benefits. - Pay: pay range and maybe note about initial pay. - Schedule: Time Appointment and Work Profile details. We must not invent or summarize away detail. So we need to preserve all specifics. Let's extract each. **About the role** prose: Combine: "The Accessibility Observatory or AO (https://access.umn.edu), a CTS research program, is a leading national resource for the research and application of access to destinations data to transportation system planning and evaluation. This position will support the Observatory’s National Access Evaluation project as well as other research projects related to destination access, transportation planning, and land use planning. The Research Data Analyst will assist with the analysis, data sharing, communication, and data management of the Center’s AO program. This includes delivering analysis and evaluation projects; communicating research results; creating and supporting data tools for sponsors and the public; supporting business development activities; and assisting with program management and administration. Research Data Analyst will report to the director of the Accessibility Observatory. Two other full-time research staff and one to three graduate research assistants make up the AO staff." We'll put that in

  . **Requirements** (Required Qualifications): "Bachelor's degree with a major in Geography, Engineering, Urban Planning, Analytics, Data Science, Statistics, Biology, Ecology, or related field, plus two years of experience; or an equivalent combination of education and relevant experience to total 6 years." We'll put as

  or maybe

  • ? It's a single statement; could be

    . **Qualifications** (Preferred Qualifications) list: - Master’s degree in a related field and two years of experience delivering or supporting transportation and land use research projects. - Project management and software development version control (e.g. Git and GitHub) experience. - Experience using data and geospatial analysis software such as: ArcGIS, QGIS, SQL databases, Python, R. - Experience using cloud computing resources such as AWS or Azure. - Proven ability to communicate complex issues in a concise and thoughtful manner. - The successful candidate will also be resilient, curious, and nimble, and able to thrive in a research environment where thoughtfulness and attention to detail are valued. We'll put as

    • . **Skills** maybe we could extract technical skills from preferred list but we already have them there. To avoid duplication, maybe we put all preferred under Qualifications and omit Skills. But we have a Skills heading in the list of possible headings; we can omit if no distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine. Let's not create Skills section if it would be thin. We'll put preferred qualifications under Qualifications and maybe rename Qualifications to include both required and preferred? But we already have Requirements heading for required. Could combine required and preferred under Qualifications and drop Requirements. However we have both headings available; we need to decide. We have Required Qualifications (specific). We have Preferred Qualifications (list). Could treat Required as Requirements, Preferred as Qualifications. That gives two substantive sections. That's fine. Thus we will have: - Requirements: required qualification statement. - Qualifications: preferred qualifications list. We'll not have Skills section. Now Benefits: list from "The University Offers a Comprehensive Benefits Package That Includes ..." We need to extract each benefit item. Paragraph: "The University Offers a Comprehensive Benefits Package That Includes Competitive wages, paid holidays, and generous time off Continuous learning opportunities through professional training and degree-seeking programs supported by the Regents Tuition Benefit Program Low-cost medical, dental, and pharmacy plans Healthcare and dependent care flexible spending accounts University HSA contributions Disability and employer-paid life insurance Employee wellbeing program Excellent retirement plans with employer contribution Public Service Loan Forgiveness (PSLF) opportunity Financial