Thesis Defense - MSIQ Program - December 2014

Director of Digital Communications à University of Mary Washington
15 Aug 2016
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
Thesis Defense - MSIQ Program - December 2014
1 sur 29

Contenu connexe

Similaire à Thesis Defense - MSIQ Program - December 2014

Curation-Friendly Tools for the Scientific ResearcherCuration-Friendly Tools for the Scientific Researcher
Curation-Friendly Tools for the Scientific Researcherbwestra
Managing your data pagetManaging your data paget
Managing your data pagetTERN Australia
Fsci 2018 thursday2_august_am6Fsci 2018 thursday2_august_am6
Fsci 2018 thursday2_august_am6ARDC
NCME Big Data  in EducationNCME Big Data  in Education
NCME Big Data in EducationPhilip Piety
Data Management for Undergraduate ResearchersData Management for Undergraduate Researchers
Data Management for Undergraduate ResearchersRebekah Cummings
Research data management & planning: an introductionResearch data management & planning: an introduction
Research data management & planning: an introductionMaggie Neilson

Plus de Shelley Keith, MSIQ

Non Invasive Governance - #confabeduNon Invasive Governance - #confabedu
Non Invasive Governance - #confabeduShelley Keith, MSIQ
Iterative Design101 #psuweb 2014Iterative Design101 #psuweb 2014
Iterative Design101 #psuweb 2014Shelley Keith, MSIQ
Critical Success Factors in Software ProjectsCritical Success Factors in Software Projects
Critical Success Factors in Software ProjectsShelley Keith, MSIQ
Google Analytics - Getting StartedGoogle Analytics - Getting Started
Google Analytics - Getting StartedShelley Keith, MSIQ
Iterative Design 101: Strategery! #hewebneIterative Design 101: Strategery! #hewebne
Iterative Design 101: Strategery! #hewebneShelley Keith, MSIQ
The Role of E-Service Quality and Information Quality In Creating Perceived V...The Role of E-Service Quality and Information Quality In Creating Perceived V...
The Role of E-Service Quality and Information Quality In Creating Perceived V...Shelley Keith, MSIQ

Dernier

SOFTWARE QUALITY ASSURANCE.pptSOFTWARE QUALITY ASSURANCE.ppt
SOFTWARE QUALITY ASSURANCE.pptDrTThendralCompSci
Models of Communication.pptxModels of Communication.pptx
Models of Communication.pptxMYDA ANGELICA SUAN
Mass spectrometry- full lecture Mass spectrometry- full lecture
Mass spectrometry- full lecture DRZIAMUHAMMAD2
WGPC Scoring Rubric TechSoup.pdfWGPC Scoring Rubric TechSoup.pdf
WGPC Scoring Rubric TechSoup.pdfTechSoup
Song-Based Lesson Plan: B2 First (FCE) Exam Prep with English LyricsSong-Based Lesson Plan: B2 First (FCE) Exam Prep with English Lyrics
Song-Based Lesson Plan: B2 First (FCE) Exam Prep with English LyricsMarcia Bonfim
Quick Tips in Odoo 16Quick Tips in Odoo 16
Quick Tips in Odoo 16Celine George

Thesis Defense - MSIQ Program - December 2014

Notes de l'éditeur

  1. Regulatory requirements: archival needs, file content/format, naming conventions governed by other agencies they work closely with, etc.
  2. Reality vs. perception. Leadership vs. the rest of the organization vs. file system scans. Leadership had anecdotes and the desire for consistency, but no hard data to understand the actual state of their file system. They also didn’t have a clear understanding of how issues were impacting the whole organization.
  3. Establish a data quality baseline 10-Step Process Business Impact Techniques Information Life Cycle (POSMAD) Data Quality Dimensions
  4. This project focused on the S and T drives.
  5. The start of building comparative data for measuring progress over time. Attempt to ensure that any corrective measures don’t miss the mark. In many cases, the multiple choice questions existed just to get the user in the right mindset to respond to the long-answer portion. So much value comes from letting people tell their stories. Use cases, anecdotes Frustrations with systems and services The survey responses helped inform the scan priorities. The scans gave context to survey results.
  6. Use steps 1-6 of the 10-Step Process, as prescribed by the project approach. Note that Step 10 isn’t reflected in the survey.
  7. The largest group was the Historic Preservation program with 21 respondents, followed by the Director’s office, the Natural Heritage Commission, and then by a tie between the Historic Arkansas Museum and the Old State House Museum. Delta Cultural Center contributed 3 responses to the survey.
  8. Respondents were asked “How easy is it to locate existing files?” The overall responses clearly skewed “easy” in raw numbers, but when it was broken down into percentages for each employee category, we see that, on average, a larger percentage of leadership and professional respondents skewed toward “hard.” These opposing trends may indicate that users have adapted to the system, or that users don’t perceive reported issues as factors that increase the level of difficulty of file findability. It may also indicate that leadership and professional users rely on administrative staff for some of these functions.
  9. A quarter of the responses indicated consistent problems finding files. Many of the comments provided examples of files renamed or deleted by coworkers, mislabeled or misfiled files, and one mentioned a file that had been password protected by a former employee. The most common issues associated with difficult to find files were those involving images and GIS data. The lack of consistent metadata was repeatedly cited as a contributing factor. Email files: This is of concern because it results in duplicate files, and/or a number of versions of files, across the network. Seventeen percent of respondents indicate they regularly create files only to discover a similar file already existed. Note that these figures only reflect self-reported instances of these scenarios. In the case of discovering files already exist, the probability is high that existing files go undiscovered as well.
  10. Question 10: How often have you encountered files that were supposed to be current, but actually contained outdated or incorrect information? This issue can arise because files haven’t been updated to match new information, but are the most current version; because updated versions are being stored elsewhere, or because an old version is the most readily available to the respondent. Thirty-two percent responded that they encounter this issue more than once per year. Question 11: How often have you encountered conflicting copies of the same file or form? Question 11 measures the frequency of discovering conflicting files, rather than simply outdated ones. Twenty-three percent of respondents encounter this issue more than once per year.
  11. Respondents were asked to self-report the impact of information quality issues in the DAH file system in terms of hours per week. Ninety percent indicated less than 5 hours per week spent on these scenarios. Overall, while frequency may be an issue for some situations, the actual time spent working through these problems is perceived to be minimal.
  12. Keeping copies of files is a common, and sometimes necessary, behavior in networked environments. It can also be indicative of and a contributor to versioning and duplication issues. Eighty-six percent of respondents reported keeping copies of files on their computer. Like storing files on a local computer rather than on the network drives, storing files or copies in the cloud or on other external devices can be a best practice for archiving purposes, but can also lead to versioning and duplication issues. Fifty-three percent of respondents reported storing files in this way. Reasons cited include easier sharing of files, fear of loss due to drive failure, and the ability to access files from outside the office.
  13. Discussions with leadership indicated the possibility that employees within the agencies might not be fully aware of internal and external regulatory requirements governing the storage and deletion of files. Seventy percent of survey respondents indicated an awareness that there was a policy or policies. However, a request to describe the requirement resulted in responses ranging from “I have no idea” to “3 years” to “until legislators say it’s ok to delete them” and even “someone else keeps up with that.” Couple this lack of awareness with repeated reports of “other people” deleting needed files from network drives and we start to see some of the root cause of issues overall.
  14. Sixty-one percent of respondents indicated they already have a method in how they name files, and many provided examples in the comments. While some respondents had very general guidelines, such as date and location for photos relevant to a geographic area, some were very specific in their methods. Examples included above. Many examples of hierarchal folder structures were provided to sort files in ways that were appropriate to the agency. One respondent indicated use National Park Service naming conventions, and another suggested adherence to an ISO standard. The diversity of use cases throughout DAH will factor heavily into any efforts for file name and folder structure consistency.
  15. The leadership interview, and employee survey informed the list of needs for the file system evaluation. Not only did we need to understand the state of the file system, we needed to understand how the perceptions in the survey were reflected by the state of the file system. Thorough scans were taken of each shared drive, and a set of key indicators; age of the file system, file types, and users of interest; shown in the table below, were selected to profile the overall health of the file system. File system age is demonstrated by (1) how long ago the largest portion of the drive was last accessed and last modified, and (2) by how long ago the largest portion of the duplicate space was last accessed. In addition to the evaluation criteria, we’re also able to see the usernames associated with wasted space, who uses the most disk space, who has the most duplicate files, which file types are the most common, and the most commonly duplicated.
  16. 14% of the scanned file system, or (729 gb of space) qualifies as ‘wasted space’, meaning it’s occupied by duplicated files. 17% of the files on the system (213,622) are duplicates.
  17. One of the key indicators of the age of the file system is when files were last accessed. This includes just opening them. The chart here is the last accessed times for the largest portion of the disk space or files of each type. To clarify, the wasted space indicator is the last opened times for the largest chunk of wasted files on each drive. Disk space is calculated the same way. Files are by actual numbers of files. What we see here is a comparison of the perception of the age of files users interact with, and an actual reading of the how recently different types of files are accessed.
  18. Respondents were asked to rate on a scale of 1 (Not at all valuable) to 5 (Very valuable) how valuable they thought a consistent naming convention would be in the context of finding files and information. Only eight percent of respondents felt a level of consistency had little to no value. Overwhelmingly, respondents felt consistency would be valuable, with half of respondents felt there was significant value in the effort. Many did voice concerns about the level of effort such an initiative would require. Those with much evolved naming and storage methods, especially those in use agency-wide, were opposed to imposed standards that would require significant time and manpower to adopt.
  19. Realistic action plan(s) – Accountability, ownership, relevance. Create agency-specific naming conventions. Consider legacy files. Create agency-specific file cleanup plans to remove drafts and unnecessary versions. Establish agency-specific metadata conventions. Consider metadata editors. Provide training on existing tools such as the Microsoft Suite, Adobe, etc. Folders should be relevant to the organization, not individuals. (Personal files should be stored on non-work spaces) Formalize IT processes and communication surrounding backups, archiving, and loss recovery. It would be beneficial for IT to clearly define and make available archiving and backup protocols, including when backups are set to run. Make it known when issues occur, such as backup failures, and communicate updates and changes early and often.
  20. Note the cyclical nature. Use the baselines to measure improvement. Keep testing. Interview/survey – measure perceptions, identify things to test Scan – tests of previous and new metrics. How you identify actual progress or lack thereof. Refine, iterate – identify changes to be made for the next cycle (almost agile, selecting the focus of the next sprint), update survey instrument, select new scans to be run/old to be dropped The overwhelming majority of stakeholders, including leadership and IT, support a more sustainable, strategic file system management process. The least optimal outcome of this initiative, per leadership and IT survey responses, is to do nothing. It should not go unnoticed that the status quo is designated ‘least optimal’ in these responses. The optimal outcome is agency-specific plans designed to support the needs and requirements of each branch of DAH, alleviate some of the pressure on the physical servers, and make transparent the naming, storing, and archiving of files throughout the organization.
  21. As this is the preliminary study in a long-term rehabilitation effort, it will be necessary to re-survey stakeholders regularly to determine needed course adjustments and identify new issues. Based on stakeholder feedback, there is significant interest and perceived need for both a Digital Asset Management System (DAM) and a geodatabase. Enterprise cloud storage options may alleviate some of the network-based issues associated with archiving and availability. Additionally, tools that include change management and version control options, such as Microsoft Sharepoint, could serve to correct user behaviors regarding archiving and versioning. These considerations should not be taken as recommendations, but rather starting points for further evaluation and review. It should be noted that the 1st steps recommended here are necessary for successful implementation of enterprise systems.