An OER or reading list consultation is a two-way information exchange. The instructor needs to get more information about how OER and reading lists work, and be told what sort of support they can expect if they embark down those roads. The librarian or instructional designer needs to gather information from the instructor that will help them identify resources that meet the learning (course objectives and learning outcomes) and teaching (pedagogy, preferences, and teaching style) goals for the course.
Helpful Information to Gather
- Narrative from instructor describing interest
- Course logistics and timeframe
- Actual documents being used, like syllabi, rubrics, assessments, and learning outcomes
- Instructor background
- Concerns
- Open licensing awareness
- Goals
- Course topics
- Learning outcomes
- Tools
- Pedagogy
- New or Redesign
- Resource Types
Managing Data and the Paper Trail
OER and affordability practitioners have shared a wide range of forms, templates, logs, and other documents that help with collecting information, brainstorming ideas, and visualizing processes. At this point, there probably already is a physical or digital "paper trail" from planning exercises, but this is likely some of the first data being collected about actual services. Now would be a good time, if it hasn't been done already, to formulate policies and procedures about how data will be collected, stored, shared, permissioned, aggregated, and so on. Here are some questions to answer:
- Will you categorize data by project, department, type of document, librarian, budget index, or something else?
- How will files and folders be named to ensure consistency and ease of retrieval? (e.g., "ProjectName_Date_DocumentType")
- Will any of the data collected be considered privileged/private?
- Will you share some of the documents as "working documents' with instructors and support staff?
- How will you respond when an instructor asks to see or duplicate a colleague's reading list?
- Will there be a centralized knowledge base or index that tracks all documents and their locations?
- What metadata will be captured for each document?
- What additional information (e.g., author, creation date, project tags) will be recorded to help organize and locate documents?
- Where will the data be stored?
- Will you use cloud storage, local servers, or a hybrid approach? If using cloud storage, which platform will be used (e.g., Google Drive, OneDrive, Dropbox)?
- Who needs access to the data?
- Which stakeholders or team members require access to specific types of information? Will access be role-based or need-based?
- What permissions and access controls will be in place to ensure that only authorized individuals can view or edit certain documents?
- How will you handle requests for access or data sharing? Is there a formal request procedure?
- Are there different levels of access, such as read-only, edit, or administrative access?
- Are there any specific legal requirements or institutional policies regarding data privacy and protection that need to be adhered to (e.g., GDPR, FERPA)?
- What reporting capabilities are needed?
- How will incoming data be aggregated?
- What methods or tools will be used to aggregate data from various sources or formats into a cohesive system?
- What software or tools will be used for data analysis?
- Which team members or departments are responsible for collecting, aggregating, and analyzing the data?
- What is the lifecycle of the data being collected?
- What are the stages from collection to archiving or deletion for different types of data?
- How will data be updated or revised over time?
- How will changes to documents and data be tracked? Will there be a version control system to manage revisions and edits?
- What training programs or resources will be available to ensure all stakeholders understand how to handle data properly?
- Is there a mechanism for users to provide feedback on the efficiency and usability of the data management system?