Project Start
In the Spring/Summer of 2018 a web team was formed with Scott, Ashley, Beth and I to discuss revamping the home page and prepare for the inevitable template change implemented by Web Communications. We met throughout the next 6-8 months but the focus and our goals transformed into something else as the momentum slowed for changing the home page on our own and Ashley's impending move to another job.
New Goals and Focus
By the Spring of 2019, it became clear that we needed to do a whole lot more with our web presence. As the Web Team plodded along with just the homage page revamp, the TS Department formed a new directive to seek out errors, broken links and other accessibility issues.
- TS staff members examined their own LibGuides and fixed errors and made necessary changes to come up to speed and date.
- Heather Hillaker started to comb through T4 pages and LibGuides and made library staff members of what errors existed on pages they managed.
- I was made an admin with Monsido but found shortcomings as it did not detect many of our LibGuide pages. I spent the next few months working with Monsido to figure out if we could fix this issue and looked for Alternatives to index and inventory all of our pages dynamically.
- By July of 2019, it was determined that any system I tested, it would not compile a full inventory of our LibGuides, didn't matter if they were Public or not.
As of November 2019 And Where To Go From Here
- All of the Public Facing LibGuides have been inventoried. From here, I will reach out to the individual LG owners and get the errors and broken links fixed.
- I am in the process now of getting all of the Private side LibGuides inventoried, with a end date of this for Friday, November 8th. Once I am done with this, I will reach out to the page owners to remedy the errors and broken links here as well.
- The T4 pillar pages are compliant and have passed error and accessibility checking.
- The big issue that once we get the errors resolved and everything up to date, is what to do on an ongoing basis. We don't have a system that will scan all of our pages automatically so we will need to put a system in place that we monitor with everyone's help. This may entail them notifying me whenever changes are made to LibGuides or when pages are removed or added. However, that will not prevent if the external content items change, which are not brought about by internal staff page changes. This can only be kept up to date in two ways. If we eventually find a system that can error check all of our pages or we do a quarterly inventory and error check of all of the pages, like I am doing now.
Items to Consider As We Move Forward
- What pages to consider moving from LibGuides to T4
- How the Emgage portal system fits into the picture with what content we want to bring to our user-base
Comments
0 comments
Please sign in to leave a comment.