
College of Professional and Global Education · School of Information
Seminar in Archives and Records Management - Data Governance
MARA 284
- Spring 2023
- Section 11
- 3 Unit(s)
- 01/25/2023 to 05/15/2023
- Modified 05/22/2023
Contact Information
Susan L. Marin
E-mail
Office Hours: As requested on an individual basis. Reach out via email to schedule meeting date/time.
Course Description and Requisites
This course explores current issues and practices in archives and records management. Examples of topics studied: "Protecting Conflicting Rights in the Digital Environment," "Archivists: Meet Web 2.0," "Ethics and Computer Forensics," and "Implications of Cloud Computing on Records Management."
MARA 284 - Data Governance has no prerequisite requirements.
Classroom Protocols
Expectations
Students are expected to participate fully in all class activities. It is expected that students will be open-minded and participate fully in discussions in class and debate in a mature and respectful manner. Use of derogatory, condescending, or offensive language including profanity is prohibited. Disagreement is healthy and perfectly acceptable. Expressing disagreement should always include an explanation of your reasoning and, whenever possible, evidence to support your position. In accordance with San José State University's Policies, the Student Code of Conduct, and applicable state and federal laws, discrimination based on gender, gender identity, gender expression, race, nationality, ethnicity, religion, sexual orientation, or disability is prohibited in any form.
Program Information
Course Workload
Success in this course is based on the expectation that students will spend, for each unit of credit, a minimum of forty-five hours over the length of the course (normally 3 hours per unit per week with 1 of the hours used for lecture) for instruction or preparation/studying or course related activities including but not limited to internships, labs, clinical practica. Other course structures will have equivalent workload expectations as described in the syllabus.
Instructional time may include but is not limited to:
Working on posted modules or lessons prepared by the instructor; discussion forum interactions with the instructor and/or other students; making presentations and getting feedback from the instructor; attending office hours or other synchronous sessions with the instructor.
Student time outside of class:
In any seven-day period, a student is expected to be academically engaged through submitting an academic assignment; taking an exam or an interactive tutorial, or computer-assisted instruction; building websites, blogs, databases, social media presentations; attending a study group;contributing to an academic online discussion; writing papers; reading articles; conducting research; engaging in small group work.
Course Goals
MARA 284 supports the following core competencies:
- C Describe the evolution of systems that manage data, information, communication, and records in response to technological change.
- D Apply basic concepts and principles to identify, evaluate, select, organize, maintain, and provide access to physical and digital information assets.
- E Identify the standards and principles endorsed and utilized by data, archives, records, and information professionals.
- J Describe global perspectives on effective information practices that are supportive of cultural, economic or social well-being.
Course Learning Outcomes (CLOs)
Upon successful completion of the course, students will be able to:
- Understand and define key data governance-related concepts.
- Describe current best practices regarding data governance.
- Understand and apply legal and ethical principles that apply to managing an organization's structured, unstructured, and meta-data.
- Understand and identify various roles and associated expectations within datagovernance.
Course Materials
Textbooks
Required Textbooks:
- DAMA International (2017). DAMA-DMBOK: Data management body of knowledge (2nd ed.). Technics Publications. Available through Amazon: 1634622340.
- Wienzierl, K. K. (2021). The data governance guidebook and playbook by a practitioner for practitioners. Technics Publications. Available through Amazon: 1634629620.
Recommended Textbooks:
- Ladley, J. (2020). Data governance: How to design, deploy, and sustain an effective data governance program (2nd ed.). Academic Press. Available through Amazon: 012815831X.
- Seiner, R. S. (2014). Non-invasive data governance: The path of least resistance and greatest success. Technics Publications. Available through Amazon: 1935504851.
- Smallwood, R. (2020). Information governance: Concepts, strategies, and best practices (2nd ed.) . John Wiley & Sons. Available through Amazon: B08234T3J7
Course Requirements and Assignments
Throughout the semester, students are expected to participate in a variety of formative assignments, including, but not limited to:
- discussion board postings;
- quizzes; and
- exercises applying their learning (such as understanding data storage and security).
Data Governance Analysis (30 points, divided over scaffolding assignments and final product): In response to a case study, students will serve as data governance professionals and provide their simulated client a formulated plan to implement a data governance program.
Students will create and provide documentation of their incremental process to implement a data governance program.
Grading Information
The standard SJSU School of Information Grading Scale is utilized for all iSchool courses:
97 to 100 | A |
94 to 96 | A minus |
91 to 93 | B plus |
88 to 90 | B |
85 to 87 | B minus |
82 to 84 | C plus |
79 to 81 | C |
76 to 78 | C minus |
73 to 75 | D plus |
70 to 72 | D |
67 to 69 | D minus |
Below 67 | F |
In order to provide consistent guidelines for assessment for graduate level work in the School, these terms are applied to letter grades:
- C represents Adequate work; a grade of "C" counts for credit for the course;
- B represents Good work; a grade of "B" clearly meets the standards for graduate level work or undergraduate (for BS-ISDA);
For core courses in the MLIS program (not MARA, Informatics, BS-ISDA) — INFO 200, INFO 202, INFO 204 — the iSchool requires that students earn a B in the course. If the grade is less than B (B- or lower) after the first attempt you will be placed on administrative probation. You must repeat the class if you wish to stay in the program. If - on the second attempt - you do not pass the class with a grade of B or better (not B- but B) you will be disqualified. - A represents Exceptional work; a grade of "A" will be assigned for outstanding work only.
Graduate Students are advised that it is their responsibility to maintain a 3.0 Grade Point Average (GPA). Undergraduates must maintain a 2.0 Grade Point Average (GPA).
University Policies
Per University Policy S16-9 (PDF), relevant university policy concerning all courses, such as student responsibilities, academic integrity, accommodations, dropping and adding, consent for recording of class, etc. and available student services (e.g. learning assistance, counseling, and other resources) are listed on the Syllabus Information web page. Make sure to visit this page to review and be aware of these university policies and resources.
Course Schedule
add schedule
When | Topic | Notes |
---|---|---|
Week 1 |
Data Management, Data Handling Ethics, and Data Governance | |
Week 2 |
Data Architecture, Modeling, Design, Storage, and Operations | |
Week 3 |
Data Security | |
Week 4 |
Data Integration and Interoperability | |
Week 5 |
Document and Content Management | |
Week 6 |
Reference and Master Data | |
Week 7 |
Data Warehousing and Business Intelligence | |
Week 8 |
Metadata Management | |
Week 9 |
Data Quality | |
Week 10 |
Big Data and Data Science | |
Week 11 |
Data Management Maturity Assessment | |
Week 12 |
Data Management Organization, Role Expectations, and Organizational Change Management | |
Week 13 |
Submit Case Study to Peers for Review/Comment | |
Week 14 |
Comments to Peer Case Studies due | |
Week 15 |
Submit Case Study Rough Draft | |
Week 16 |
Submit Final Case Study |