CMS Assessment Committee Phase I Report Executive Summary Phase One Methodology and Overview The CMS Assessment group membership is comprised of campus IT professionals with significant website administration knowledge; it is chartered by John Krogman. The committee will report both to John Krogman and MTAG. The committee’s primary goal is to first gather information regarding the use of website Content Management Systems (CMS) on campus. If the data indicates an opportunity to better utilize pooled campus funding, the committee is prepared to engage a second phase, which will put forward enterpriselevel tool recommendations. During this first phase, the committee identified internal and peer institution CMS trends, conducted targeted inperson interviews with 12 campus stakeholders, and collected campuswide data (from over 650 individuals) over a two week period through a survey geared toward current and future CMS usage. The data collected indicates the timing is right to explore options for a new, centrally supported, enterprise caliber CMS. Choosing a new CMS tool will afford campus an opportunity to use existing funding levels to maintain and support a significantly larger percentage of CMS based websites, in addition to the potential real money and opportunity for cost savings that could be realized by units through voluntary aggregation and shared services. In addition, aggregation of websites using a widespread CMS tool would potentially lower the overall risk platform for campus while freeing up security team cycles. User feedback indicates a strong desire for a centralized library of resources, themes, and plugins, however existing distributed campus users would likely be slow to migrate to a centralized CMS. Better CMS alignment on campus would allow centralized development of a library of resources, themes and plugins and a pathway to more centralizing. Our current campus CMS tool, OpenText (formerly RedDot) was chosen during an RFP process in 20072008. It is comparatively expensive to maintain the license ($79k) and infrastructure ($86k), which are covered through campus assessment. Even though web development and technical support services are available at no cost to end users, to date OpenText has been adopted by approximately 10% of campus web sites. According to data collected in the survey, current users of OpenText that are planning a website migration are overwhelmingly looking at other tools, despite their strong satisfaction with the support provided by the WiscWeb CMS team.
Narrative Summary Introduction In recent years, the use of websites has exploded on the University of Wisconsin Madison campus. At present, there are at least 1900 separate UWrelated websites. They are used by groups large and small, for purposes as wideranging as sharing research data, to broadcasting photos of plants, to selling artwork, to collaborating between teams scattered across continents. To address their needs, many units have utilized their own internal staffing and infrastructure to develop and host their web sites. Additionally, some groups within the UW community contracted with thirdparty website vendors to develop custom websites, then hired their own IT support staff. Often times, websites are put up by a graduate student and then orphaned when that person exits the program. Campus groups have looked to DoIT for guidance and support. For the sake of efficiency, branding, and offering guidance for those who need it, the UW needs to map out a strategy to address this critical, and radically shifting landscape. DoIT is very invested in working with campus to work on a future strategy for CMS. In August of 2015, John Krogman, DoIT COO, constituted a committee to conduct a campuswide evaluation of this everevolving website environment on campus. This committee, called the UW CMS Assessment Committee, is chaired by distributed IT and comprised of twelve individuals who represent a broad crosssection of departments, schools, and experiences. This report presents the collective findings of that committee. The CMS Assessment Committee needed to gather information from numerous sources. Subcommittees were formed to conduct facetoface interviews of UWMadison staff, to contact peer institutions, to collect usage on our own campus website community, to analyze the data that was returned through our survey, and to craft the various components of this report. Through committee meeting time, and google document comments, main themes were pulled from the sub groups reports (see Appendix I), and turned into this report.
Gathering Information To better understand the CMS landscape on campus, the committee conducted twelve facetoface interviews with UW groups who had recently built, or rebuilt, their websites, or were otherwise involved in the UW website situation. (See Appendix I, 1on1 Themes) During these interviews, we asked about the decisions that were made, the priorities that were pursued, and ultimately, what guided the group to make the decisions they made. CMS Assessment Committee Final Report
Page 2 of 10
Some recurring themes encountered during these interviews include: There is interest in centralized support for various webneeds on campus. There is also a strong desire for various degrees of autonomy. Campus website owners are largely expecting to provide and edit their own website content. A strong desire for easy to access branding, pictures, UW data feeds, and plugin support. Across campus, there is broad support for (and use of) multiple website platforms. The three most common tools are WiscWeb CMS, Drupal, and WordPress. The WiscWeb CMS, OpenText, has a mixed reception on campus. The service and support team for WiscWeb CMS has a very strong reputation on campus. Many groups on campus are willing to spend a significant amount of money for custom development and hosting of their websites, while other groups need a free service. One of the main themes was ease of use for content editors, which frequently was a key factor in the next CMS selection. A desire for optional workflow control. Significant frustration when a site was dependent on developer support when the area had developer turnover. Instantaneous publishing when the publish button is pressed. A Qualtrics survey was conducted to determine what tools people are using, and why those tools are being chosen. The survey utilized smart logic to keep the questions relevant based on previous responses. If they had recently migrated, we asked them about their old site and reasons for moving. We asked about their current site. And if they planned to migrate within the next two years, we asked them about what they were migrating to. We had over 650 responses, the vast majority were from Drupal, WordPress, and Wiscweb users. In addition to emails to Tech Partner Primes and MTAG, we also sent the survey to the Drupal, WordPress, and Wiscweb user groups. DoIT hosting sent the questionnaire to all their customers, and DoIT’s PTE sent the survey to the attendees of CMSrelated training. A couple standouts ● WordPress is growing; over 50% of the migrations in the next two years. ● Functionality was the top priority when choosing new websites. A number of similar universities were contacted and asked simplified questions, usually with a phone follow up to see what they were doing for enterprise solutions.
CMS Assessment Committee Final Report
Page 3 of 10
Current UW–Madison Offering UW–Madison offers one enterpriselevel web publishing tool: OpenText. It is supported centrally by DoIT’s WiscWeb CMS Enterprise Service, is funded through a campus assessment, and is available at no additional cost to those who use it. OpenText has a small but loyal following of users who are very pleased with the tool. Almost all who responded were pleased with the support provided by the WiscWeb CMS team. However, many groups on campus have decided to not use OpenText, because they determined that the tool did not meet their group’s needs; however, given the absence of central support for other tools, these groups were left to find and fund support on their own. OpenText is a static website generator that pushes content to web servers. This is a very different model than the current crop of CMS where the ability to edit is embedded with the hosting. Modern CMS make much better use of shared resources, requiring fewer staff and vastly cheaper hosting costs per site. In particular, Drupal and WordPress have become commonplace in both corporate and higher education creating a robust user community with innumerable enhancement (plugin) options. UW Milwaukee performed an exhaustive investigation into different CMS options, looking at usability and long term cost before recently settling on WordPress. Other large campuses made the move to Drupal after similar studies. UW–Madison campus users are also making the move. Over 50% of planned new sites will use WordPress.
Current State Issues We also saw a small but significant number of sites that are working with outside vendors for design. There is limited design support on campus. While this isn’t necessary an issue, since there are a number of commercial design companies able to step in, it is concerning that the designers tend to propose new CMS options which further diversify the campus installed CMS base. We did hear that design firms designed for WordPress or Drupal but not OpenText. The result leaves some campus units on a platform for which they have no support. We also investigated several shared hosting options on campus. We found that multihosted WordPress and Drupal were a fraction of OpenText hosting costs and frequently had fewer staff supporting them with a similar portfolio of service to WiscWeb CMS. We also investigated a few cloud vendors, and found potential, though it was often hard to easily gauge final costs. For instance, they typically charge for web certificates, but those can be obtained at no cost on campus due to a subsidy from the Office of Cybersecurity. Our reading of the data shows these two areas, campus multihost sites and cloud solutions, should be covered in a detail in a Phase II report to validate they scale to enterprise levels and with adequate technical detail to able to be evaluated for campus use. CMS Assessment Committee Final Report
Page 4 of 10
One of the areas that needs to be explored is a way to better leverage work done by WiscWeb CMS for use by more of campus. A number of groups noted they are unlikely to move to a campus solution but would be very interested in a library of resources that they can consume.
Other Universities and Corporate We found that universities were moving to Drupal and WordPress. From Gartner reports, these are both strong contenders, each with the ability to handle most website needs with energetic developer communities. Gartner noted that supporting both platforms would ensure that all web projects could find an appropriate CMS tool for their needs. We also looked at reports on adoption rates and found that both Drupal and WordPress had a large user base and market share, while OpenText has dwindled. (See Appendix 4.) UW–Milwaukee in particular was very interesting. They recently picked WordPress as their enterprise solution and are migrating to it. They invested significant resources in researching the best option for CMS, including user testing and analyzing long term maintenance costs. WordPress was found to be the easiest and most efficient content editor, saving staff time when editing pages. It was also the best value when long term maintenance costs were factored in. It was assessed robust enough to handle the vast majority of their needs. There were a number of other large schools that adopted Drupal.
WiscWeb CMS FY16 Budget DoIT Labor Training DoIT Hosting
535,000 40,000 76,420
Servers, Database, Network, Storage, Backup
Licensing Open Text Depreciation Misc
84,394 79,000 10,000 3,150
Room rental, advertising, font services, etc
Total
708,964
CMS Assessment Committee Final Report
Page 5 of 10
Statistics and Survey Analysis Q: What CMS systems are respondents using now to manage their websites and how many websites are they managing on each CMS (question 16)? CMS
Response
% Resonse
Websites
% of Total
WiscWeb CMS
145
33%
175
9%
WordPress
201
45%
658
34%
Drupal
80
18%
260
14%
HTML/CSS
144
33%
338
18%
SharePoint
15
3%
17
1%
Google Sites
37
8%
78
4%
Other1
72
16%
277
14%
Other2
11
2%
118
6%
Numbers in this chart reflect only users who responded to the survey. Actual numbers for all CMSs are believed to be higher.
Q: Why did your group migrate from the prior platform(s)? (Select all that apply.) Reason
Responses
% of Total
dissatisfied with the functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
78
54%
dissatisfied with the technical support (e.g. the ability to develop new features, expand the website’s usefulness)
54
38%
dissatisfied with maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
55
38%
dissatisfied with the cost
8
6%
I don’t know
34
24%
CMS Assessment Committee Final Report
Page 6 of 10
Q: What will be your priorities when selection the next platform? (Select all that apply.) Reason
Responses
% of Total
functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
131
89%
technical support (e.g. the ability to develop new features, expand the website’s usefulness)
92
62%
maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
102
69%
the cost
8
5%
I don’t know
12
8%
Q: Where applicable, indicate your group’s satisfaction with the technical support available with the following web content management platforms or tools. (Note: Responses ranged from 1pt to 4pts. A lower “Average Value” represents a better, more positive response.) Reason
Average Value
WiscWeb CMS
2.45
WordPress
2.62
Drupal
2.77
HTML/CSS (e.g. DreamWeaver)
2.68
SharePoint
3.14
GoogleSites
2.85
Other
2.90
CMS Assessment Committee Final Report
Page 7 of 10
People who have WiscWeb CMS sites, and are planning on migrating in the next two years.
People who have WordPress sites, and are planning on migrating in the next two years.
People who have Drupal sites, and are planning on migrating in the next two years.
CMS Assessment Committee Final Report
Page 8 of 10
WiscWeb CMS satisfaction results for people with WiscWeb CMS sites.
WordPress satisfaction results for people with WordPress sites.
Drupal satisfaction results for people with Drupal sites.
CMS Assessment Committee Final Report
Page 9 of 10
Committee List Eric Giefer, Chair, Law School Ryan Engel, Learning Support Services (LSS) Libby Peterek, University Marketing Jason Pursian, CALS Griffith Randall, L&S Student Academic Affairs Greta Seckman, Division of Continuing Studies Alan Silver, Chemistry Dan Simanek, VCRGE Joe Tarter, DoIT James Vogel, Office of the Registrar Nick Weaver, University Marketing Cliff Cunningham, PM, DoIT
CMS Assessment Committee Final Report
Page 10 of 10
CMS Assessment Committee – Phase I Report Appendix 1 CMS Assessment Committee – Findings and Assessment
Printed 11/17/2015
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Themes from 1on1 Interviews Individuals Interviewed OneonOne Meloney Linder, School of Business Brenda Spychalla, School of Education Aaron Stern, OHR Amy Toburen, Dean of Students Office Brian Rust, DoIT Communications Mike Pitterle, School of Pharmacy Steve Barnet, Ice Cube Alissa Ewer & Kathi MatthewsRisley, Graduate School David Luke, UW Libraries Beth Tobakos, Political Science Department Kelly O’Loughlin & Allyson Casey, UW Union Cathy Riley, WiscWeb CMS
Existing Service WiscWeb CMS, currently using OpenText as the web content management platform, hosts approximately 200 sites on the UWMadison campus. The service provides both standard and responsive templates. Custom site development is also available. Publishing is done via SFTP to a remote site. Extensive documentation is available, as is training. Group training is offered several times a month, while 1on1 training can be made available. WiscWeb CMS provides access to frontend web developers, along with active maintenance and security. It was noted that there are a significant number of people on campus who don’t have funding for a website(s) and/or don’t have access to web developers. This community, in particular, is a key driver behind the existing services.
Themes: Usage Trends A number of large campus entities have recently chosen to migrate away from WiscWeb CMS or never adopted the platform. The most common target platform(s) for campus entities not using WiscWeb CMS are clearly the open source, PHPbased web CMS platforms, WordPress and Drupal specifically though others were noted. Education and School of Business both make use of thirdparty commercial tools, though it seems Education has mixed use with Wordpress and may be shifting in that direction.
Page 1 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Themes: Reasons given for not selecting WiscWeb CMS Several reasons were stated for not making use of or moving away from the WiscWeb CMS service. Stated reasons included: ●
User experience for editors is poor, laborious
●
Not flexible enough for developers
●
Slow and cumbersome to use, sometimes requiring repeat training not intuitive
●
Tool does not protect the end editors from code enough
●
Windows only for administering (no longer true)
●
WiscWeb CMS timetables for delivery could be long
Themes: Key features needed in a tool A number of needs were identified when seeking a web CMS tool. Some of the identified needs included: ●
Quick use of templates and layouts (branded look & exact page layout)
●
Quick and easy editing
●
Image sliders
●
Forms and workflows
●
Open source platform and plugins
●
Cross promotion of event
●
Responsive/Mobile ready
●
Support for distributed editors
●
Enforcement of boundaries and controls across distributed editors/contributors.
●
Some interactivity with data
●
Ability to pull in data from 3rd party sites
Themes: Desired items in a central service A number of items were identified as desirable in a central service. These items included: ●
Available development and support with option to opt out when local staff are available
●
Access to training
●
Appropriate security and long term maintenance
●
Ability to make changes quickly
●
A central repository of themes and plugins
●
Ability to have plugins written and installed
●
Tools to manage and move data between test and production
Page 2 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
●
Delegated access control
●
Very tight shibboleth integration and access for those outside the UW
●
Not constrained by UW look and feel
●
Search engine optimization ( SEO )
●
Address accessibility ( ADA ) issues and concerns
Themes: Other Insights ● ● ● ● ●
A number of campus entities are outsourcing design and development to consultants, sometimes for sixfigure contracts Use of the DoIT Web Hosting service appears to be very common Some do not want to develop or maintain themselves, so ongoing support has been a question for those currently using WordPress or Drupal Some custom plugin work has been provided from DoIT Desktop Support and Academic Technology For those building their own sites, some mention of staff turnover or limited access to development time
Page 3 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Other Schools & Industry Questions asked: 1. Do you use a CMS for your homepage? 2. Are there other CMSes you support? 3. How long have you used said CMS? 4. Who made this decision? 5. Are you happy with it?
Notre Dame 1. Do you use a CMS for your homepage? ○ We do not use a CMS for w ww.nd.edu . It's pretty much a simple PHP class and we update the pages directly on a staging server. 2. Are there other CMSes you support? ○ Our primary CMS on campus is an in-house built Rails app called Conductor ( http://conductor.nd.edu/ ) which manages approx 480 websites. We also have a Wordpress Multisite install that runs our b logs.nd.edu network. The Engineering department uses Plone, but my team is not involved in that product. 3. How long have you used said CMS? ○ We have used Conductor since 2007. 4. Who made this decision? ○ Our web team decided to build a CMS because the solution at the time (Contribute and Dreamweaver) were underwhelming, and none of the other open-source CMS's at the time were very interesting. 5. Are you happy with it? ○ We are very happy with Conductor. We have been able to craft it over the years to fit our needs very well.
Page 4 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
UT Austin 1. Do you use a CMS for your homepage? ○ Yes – Drupal 7 2. Are there other CMSes you support? ○ Yes, Wordpress only. 3. How long have you used said CMS? ○ We’ve been on Drupal for 8 years. 4. Who made this decision? ○ Combination of the central IT web team and University Communications. 5. Are you happy with it? ○ Absolutely! The only downside is that it has become difficult to find, hire, and retain good employees because the demand for Drupal developers is so high in Austin.
University of Michigan 1. Do you use a CMS for your homepage? ○ No, customized platform for umich.edu “gateway” utilizes a robust php/MySQL framework 2. Are there other CMSes you support? ○ Yes, Wordpress for two primary reasons ○ Ease of use for content stewards ○ Ease of use in keeping secure 3. How long have you used said CMS? ○ Several years 4. Who made this decision? ○ UMich Creative team 5. Are you happy with it? ○ Yes, very.
Page 5 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
University of Illinois 1. Do you use a CMS for your homepage? ○ No - Dreamweaver and static files 2. Are there other CMSes you support? ○ There is no centralized solution. Several instances of Wordpress and Drupal on campus. Even within each school or college, different CMSes are used. 3. How long have you used said CMS? ○ N/A 4. Who made this decision? ○ Each unit makes their own decision based on experience and expertise. 5. Are you happy with it? ○ The web services team has created several applications within what they call the “Tool box” They include, but are not limited to: calendars, blogs (home built), directory, maps, email, shortened URLs, and Form and survey builder. All of these applications can be pulled into any of the various web solutions used around campus. The web services team is happy with their solution but cannot speak for the rest of campus.
Page 6 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
University of Wisconsin Milwaukee* 1. Do you use a CMS for your homepage? ○ Yes, UWM uses CommonSpot by PaperThin for the UWM Home Page and some top level (university-wide) web page content on www4.uwm.edu. CommonSpot used to host most of the school/college and administrative unit content as well. We are transitioning to WordPress (multisite) with a UWM-branded theme and curated catalog of plugins residing on web host that simply has the uwm.edu domain (no www4). Most schools/colleges have moved to WordPress (e.g. h ttp://uwm.edu/business/ ) and we are actively working on moving the remaining campus units to WordPress, as well as the UWM Home Page and top level page content that remains on CommonSpot. WordPress infrastructure is hosted at AWS. University Relations & Communications supports the WordPress software for campus. 2. Are there other CMSes you support? ○ CommonSpot and WordPress for organizational unit-level outward-facing web content. CommonSpot is still supported but is colloquially considered a legacy service. We have not yet started a formal retirement project. We are in the process of rolling out another WordPress-based web publishing service for faculty and staff professional pages (e.g. people.uwm.edu/rothfels). The provider is CampusPress. UWM is also in the process of rolling out Office 365 Sites (SharePoint). I believe SharePoint will be primarily targeted at internal audiences, but I mentioned it because it does have CMS capabilities. 3. How long have you used said CMS? ○ CommonSpot since late 2007. WordPress since March 2014. 4. Who made this decision? ○ In both instances, a campus working group conducted research, gathered feedback, produced requirements, vetted candidates, consternated slightly, and issued a recommendation. Both working groups were sponsored by UWM's Web Steering Committee. 5. Are you happy with it? ○ WordPress was selected in May 2013 as an alternative to CommonSpot, based on a campus working group recommendation. The campus working group was formed in June 2012 to assess CommonSpot service/functionality gaps that had become apparent as the CMS landscape evolved in the time since we first selected CommonSpot. WordPress has been well-received on campus, is efficient to work with, and has proven to be approachable by a wide audience of content authors/owners. We have experienced a quite significant reduction
Page 7 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
in development and support hours with WordPress, as well as a significant decrease in time required for web-related project completion with WordPress. * On the phone, Mark walked me through their process. It was very helpful. They did a lot of things right like measuring time and cost for ongoing support of a new system and a high level usability test of the most common tasks in Drupal, Wordpress, and their current system. From those tests, it was revealed that Wordpress was 6x more efficient than any of the other CMSes in completing basic tasks (i.e. fixing a typo, adding a pdf, inserting a photo with caption, inserting a photo gallery, etc.) He’s sending some of their documentation over in the morning. (11/5/15)
Page 8 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Managed/Enterprise Web Hosting UWMadison has a well established history of building and maintaining the infrastructure necessary to support its teaching and research missions, including hosting solutions for websites and web applications. However, given the proliferation and widespread adoption of cloud services in many areas of the IT landscape, it would be remiss of this committee not to include a comparison of some cloud services/service providers in its report. Given the scope of the university’s online presence and the many hundreds of websites associated with the UW, this comparison focuses on a handful of enterpriselevel providers competing in the cloudbased, hosted web content management space. Vendors in this space use a variety of mechanisms for determining pricing, making a straight comparison of the included vendors difficult. One way to elicit a more direct comparison would be to provide each vendor with a sample hosting scenario based on one or more known hosting environments currently in production at the university and that includes a matrix of high, medium, and lowvisibility websites, monthly visitor traffic, the average disk per site, nature of the codebase (single or multisite), etc., along with less commonly used requirements like Solr search or a caching system. We recommend including such an exercise in Phase II of this committee’s project. The vendors included in this report were chosen in part because they have relatively equivalent, comparable feature sets, including a wrapper of service around the content management systems each vendor provides hosting for; these vendors also provide specialized tools to make administering those systems easier. A more comprehensive comparison could include vendors like Amazon Web Services or Rackspace but with acknowledgement that it would be university staff providing the wrapper of support and maintenance of any specialized administration tools and not the host provider.
Blackmesh Blackmesh is a fullymanaged web hosting provider founded in 2003. Blackmesh focuses on providing highly flexible, customized hosting solutions based on customer needs; it also provides fullservice support for WordPress and Drupalbased websites.
Features and Service Configuration: ● ● ● ● ● ●
Hosting/infrastructure: Drupal, OpenText, Wordpress, or any other service or tool Service/support: Will install, configure, and support everything from infrastructure up to code Compliance/Security: FedRAMP, FISMA, HIPPA, PCI Server stability/uptime: 99.999% stability; written into SLA contract Additional services: Apache Solr availability and support, SAML integration Development environment: flexible/customizable per customer needs
Page 9 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
● ● ●
Infrastructure built using dedicated resources; not a shared hosting environment Data center information: USbased; located Virginia and Nevada Brag: claims to cost approximately 30% lower than competitors but with higher levels of service
Pricing based on: 1. 2. 3. 4. 5.
Number of CPUs Amount of ram Size of disk/storage space used Complexity of system Traffic
Customers include: Johns Hopkins University, Department of Energy
Pantheon Pantheon provides a scalable website management platform for WordPress and Drupal with integrated developer, workflow, and automation tools. Pantheon offers tiers of service ranging from personal websites up to Pantheon Enterprise and Pantheon for Edu.
Features and Service Configuration: ● ● ● ● ● ●
●
● ●
Hosting/infrastructure: WordPress and Drupal hosting Service/support: Elite tier includes unlimited tickets 2 hour response SLAguaranteed, phone support, and 24x7 oncall support Compliance/Security: Recommends against hosting FERPA data on Pantheon infrastructure Server stability/uptime: 99.9% (Elite tier customers only) Additional services: Apache Solr v3.6 delivered as a service, Varnish and Redis (caching), Denial of Service Protection, Network Intrusion Protection Development environment: ○ Developer dashboard with oneclick site provisioning ○ oneclick core updates to apply WordPress and Drupal security patches ○ separate Dev, Test, and Live environments Pantheon does not support traditional multisite installations; instead, they provide custom upstreams/distributions that allow individual/department website owners to launch sites with centrally administered branding and templates (Enterprise level only) Rolebased permissions to control site/team/department/individual owner access within an organization Data center information: USbased data centers; primary hosting located at Rackspace in Chicago
Page 10 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
●
Brag: “Pantheon is the world’s fastest hosting for Drupal and WordPress…. Multiple independent benchmarks have compared Pantheon with other providers, and we consistently come out on top.”
Pricing (Pantheon Enterprise): Pantheon pricing is organized around their Personal, Pro, and Business plan levels. Pantheon Enterprise includes a $10,000 annual selfservice credit that is used to manage multiple selfservice plans (Personal, Pro, Business). Owners of individual sites then select the appropriate plan based on a site’s pageview, storage, RAM/memory, etc., needs; site owners can switch between plans based on evolving site needs. Pantheon for Edu includes free hosting for development sites; charges begin only after a site is launched. Pricing for the selfservice plans is as follows: ● Personal: $25/month with up to 10,000 monthly pageviews and 5GB storage ● Professional: $100/month with up to 100,000 monthly pageviews and 20GB storage ● Business: $400/month with up to 500,000 monthly pageviews and 30GB storage
Customers include: Arizona State University, Columbia, MIT, Princeton, UCBerkeley, University of Minnesota
Acquia/WP Engine Acquia is a largescale Drupalonly cloud platform provider, though for the University of Texas at Austin, Acquia partnered with WP Engine, itself a WordPressonly hosting service, to provide a comprehensive enterprise hosting solution.
Acquia Features and Service Configuration: ● ● ● ● ●
●
Hosting/infrastructure: Drupal hosting Service/support: 24x7 support for critical issues with non24x7 support for other issues (Acquia Cloud Enterprise tier) Compliance/Security: HIPPA, FISMA, PCI Server stability/uptime: 99.95% SLA Additional services: Varnish and Memcache (caching); Apache Solr search; Mollom (spam blocker); Acquia Content Hub (a cloudbased, centralized content syndication tool that ties into many popular content management systems) Development environment: ○ development, staging, and production environments ○ easy deployment of code, files, and databases between environments ○ Drupal core and module security patching ○ automated tests monitor and flag issues as content is migrated between environments ○ GIT and SVN support
Page 11 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
●
●
○ Drush integration Enterprise contracts usually a combination of Site Factory (6080% of sites) and Acquia Cloud (2040%). Site Factory is relatively locked down with little control of underlying infrastructure; Acquia Cloud provides more access to the underlying platform. Data center information: USbased data centers in Oregon and Virginia
WP Engine Features and Service Configuration: ● ● ● ● ●
● ● ● ● ●
Hosting/infrastructure: WordPress hosting Service/support: 24/7 technical support from USbased WordPress experts Compliance: PCI Additional services: Evercache (caching), builtin enterprise CDN Development environment: ○ staging area with oneclick pushtolive ○ git push integration Autoapplication of minor patches; WP Engine tests major patches before recommending customer upgrades Realtime security threat detection monitors against DDOS and brute force attacks, intrusion detection, Javascript/SQLinjection, XMLRPC attacks, and other vectors Automatic backup and disaster recovery Data center information: USbased data centers located in the Midwest Brag: “If you get hacked, we’ll fix it for free.”
Pricing based on: The complexity of a joint pricing contract with Acquia and WP Engine is beyond the ability of this report to estimate. Acquia has a flexible pricing solution that incorporates factors including amount of CPU/RAM, site storage, number of PHP processes, number of code bases, and support needs. WP Engine’s basic pricing is organized around a system of hosting plans based on code bases, page visits, and data storage. WP Engine also has a Premium and Enterprise plans.
Customers include: UCLA, Harvard, UTAustin
Page 12 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Campus Summaries WiscWeb CMS ● ●
● ● ● ●
● ●
# Sites: around 200 # staff: 6.5 FTE, representing the following rolls: Project Manager, Application Administrator, Support Consultant, Application Developers, Database Administrator, End User and Administrator Trainers, System Administrator, LDAP Administrator #infrastructure cost (licenses & hardware): $165,420 Service (noninfrastructure) cost: $543,544 Cost to user: $0 (if different levels, explain) Service narrative (a couple paragraphs, not longer than a page) — should include support (who does patches), security, description of service (i.e., design, dev, training, etc), who the service is suitable for. WiscWeb CMS Info: ○ Push type CMS from OpenText, previously RedDOT. WiscWeb CMS Service Narrative: ○ Provides CMS hosting for any UWMadison dept/school/college. ○ http://info.wiscwebcms.wisc.edu/ ○ Support provided by DoIT HelpDesk and the DoIt WiscWeb CMS team. Numerous well written KB articles covered most end user and administrative topics. ○ Users are added/removed to project by WiscWeb CMS team. ○ Team is very responsive and customer focused. ○ Monthly brown bags with end users to both share new features and gather user input. ○ Training provided by DoIT training. Regular user classes (3 hours), no cost to user; Admin training, 2hours, free; specialized training on request. ○ Website can be hosted by DoIT CMS team, or by DoIT WebHosting, or on own server ○ CMS server supported by DoIT WiscWeb CMS team ○ Provides older standard and new responsive templates with numerous content classes, including: Photo Carousel, RSS Feed, Calendar, Video, Tabs, Accordions, Blog, Forms, Google Maps, Person Bios, News articles, and , numerous text entry options. http://demo.wiscwebcms.wisc.edu/ http://demo.wiscwebcms.wisc.edu/responsive/ ○ Templates have accessibility built in. ○ New custom templates are developed by the WiscWeb CMS team as needed. Includes a customizable workflow, with approval before publishing ○ Templates allow easy editing by content owners, reducing the need for web developers to update content.
Page 13 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
○ ○ ○ ○
Templates allow extreme flexibility, allowing web developers to combine complex web apps with content that is updated by content owners. Provides versioning, with compare versions, and restore version Content can be activated/deactivated automatically at predetermined times. Original RedDOT CMS was selected by an exhaustive RFP process, and included a campus wide team of users/server admins that reviewed over 15 different CMS's.
DoIT Hosting ● ● ● ● ●
# Sites: 215 WordPress, 40 Drupal, some Silverstripe & Joomla # staff: ? #infrastructure cost (licenses & hardware): ? Service (noninfrastructure) cost: ? Cost to user: $0 if html only site with 5GB storage, then three tiers for database (ie WordPress) with multidomains, starting at $45 and an enterprise restricted data hosting for $150/month. NOTE: basic WordPress/Drupal is $540/year.
Service Narrative The service has all the usual options – unlimited bandwidth, nightly backups, ability to increase quota, usage reporting, test/prod servers, and custom domains (mysite.wisc.edu). They support open source applications through Plesk Support Control Panel which is great for quickly creating sites. Easy integration with NetID and partnerships with DoIT ADI and WiscWeb CMS. They take care of patching the core service, however things like WordPress plugins need additional manual attention. The have additional security, including Mod_security that helps moderate connections to the server preventing some kinds of attacks, admin features only available on campus or through VPN. Service is focused on empowering users with the access to the kind of server they need, quickly, and with self service options to quickly be up and running with a reliable host. They have rapid support response when needed. The service is suitable for anyone from a static dreamweaver website (free), to a complex Drupal/WordPress site (at a monthly fee), or restricted data (at a monthly fee, see above). Design and Development is available at an hourly rate.
Page 14 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Sample Drupal Hosting in Chemistry ● ●
● ● ●
# Sites: around 75 # staff: .5 FTE, .2 student hourly representing the following roles: Project Manager, Application Administrator, Support Consultant, Application Developers, Database Administrator, End User and Administrator Trainers, System Administrator, LDAP Administrator #infrastructure cost (license and hardware): $4,000 Service (noninfrastructure) cost: $0 cost to user: $0
Service Narrative Provide Drupal CMS for any department entity that is looking for a web presence. All hardware infrastructure is hosted at Chemistry. This includes 70+ sites including the main department site, research group websites, events, facilities and inventory databases. These sites that we set up initially are then handed over to those groups that we work alongside. This can be graduate students, staff, or faculty. We offer multiple templates and tailor the sites to the needs of the user/group. A research group UW branded themed site is already in production in Chemistry. Our service offering is comprised of a team of 3 people. ● Admin The admin is in charge of security, patching the application and system, and initial drupal install. This is handle by one person. ● Development The support team includes flushes out what the main department website will look like and how it will function. They are also work directly with entities who are looking for a new website. They collect information about how the user would like the site to operate. This duty is handled by 3 of us. Two people of the team can handle the basic development. If it complicated, the 1 main developer will step in to help. ● Support Any questions about adding content, adding new functionality also goes through our three team members for triage. Training and support is done in person and via email whenever users have questions.
Page 15 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
Sample Drupal Hosting in LSS ● ●
● ● ●
# Sites: 133 # staff: 1 FTE representing the following roles: Project Manager, Application Administrator, Support Consultant, Application Developers, Database Administrator, End User and Administrator Trainers, System Administrator #infrastructure cost (license and hardware): $1300/y for two virtual servers, 2 servers purchased at ~$6k (approximately $1,000 per year) Service (noninfrastructure) cost: $0 cost to user: $0
Service Narrative Similar to Chemistry, most support in one person, with some duties supplemented by others.
Page 16 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
CMS Assessment SurveyResponses Summary 1. Who completed the survey? a. b. c. d.
Most responses from “staff” (86%) Most respondents are decision makers (84%) Almost all respondents are affiliated with a website (97%) Majority of respondents have content related dutieseditor, publisher, reviewer (65%) and writer/contributor (59%). e. Roughly onethird of respondents identified as “IT professional, site administrator, system admin” and another onethird identified as “Designers.” f. Only 16% identified as “Developer or programmer.” g. Exactly 27 respondents identified as “Dean/CIO/Executive Administrator.”
2. What did we learn about the websites represented in the survey? a. Almost all website represented in the survey are publicfacing websites (92%) b. Other significant functions include intranet (35%), events/eventrelated (54%), and personal/biographical/researchrelated (30%) c. A number of respondents used the “other functions” field to add a comment about the desire for webbased forms, scheduling, or other data input type functions. d. Of the websites represented in our survey, approximately 70% have been on the current platform for more than two years.
3. Approximately 144 respondents (30%) indicated that the websites represented in the survey have been on the current platform for less than two years. What did we learn about these websites and associated respondents, in particular? a. The most common prior platform response is the “HTML/CSS (e.g. Dreamweaver)” selection. Since the committee opted to combine HTML/CSS with Dreamweaver, we can’t be sure how many of these prior “platforms” were handcoded websites as opposed to Dreamweaver websites. b. The second highest number of responses for prior platform is WiscWeb CMS with 28 responses (20%). c. Of the “other” responses for question 11 (What was prior platform?), there were only three unique platforms cited with more than 2 responses each: Adobe Contribute, Sitefinity, and Joomla. d. Of the reasons cited for leaving the previous platform, cost had the lowest response of all reasons provided (6%) e. Of the reasons cited for leaving the previous platform, dissatisfaction with functionality received the highest number of responses (54%) f. Dissatisfaction with technical support offerings (37%) and platform maintenance concerns (38%) both received significant responses
Page 17 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
g. Two common themes emerged in the comments for question 12 (Why did you leave your prior platform?). The first theme concerned the availability of and ease of access to a set of prebuilt, UWbranded designs/templates on other platforms. The second common theme detailed an unacceptably high level of perceived difficulty for basic content editing operations on the prior platform. h. As would be expected the priorities in the selection of the new/current platform mirror the reasons for leaving the old platform. The same three selections: functionality, technical support, and platform maintenance each had over 50% response. i. The same (inverse) themes were true of the comments for question 13 (What were priorities in selection of current/new platform?). Common themes included: ease of use for content editing, availability of common UWthemed branding components, and the availability of local technical support options for the platform. j. Interestingly, while the “cost” option was not selected as a significant concern with the old platform (6%) nor a significant priority for the new/current platform (3%), it did emerge frequently in the comments for the “priorities for new platform” (question 13). Approximately 30% of the comments included at least one reference to “low cost” or “free” as being an important consideration in the selection of the new platform. The cost option in question 13 was labeled as “dissatisfied with the cost” and I think that might have caused some confusion for respondents.
4. What CMS systems have respondents used (question 15)? a. Out of 499 responses in total, 185 respondents have used WiscWeb CMS (37%), 295 respondents have used WordPress (59%), and 144 respondents have used Drupal (29%). Additionally, 61% of respondents have used “HTML/CSS (e.g. Dreamweaver).” As noted above, due to the specific survey language used, we can not differentiate between manual HTML/CSS coding and Dreamweaver usage. b. “Other” was selected by 111 respondents (22%). Other platforms mentioned at least 3 times include Joomla (13), Sitefinity (6), DotNetNuke (5), Adobe Contribute (4), Expression Engine (3).
Page 18 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
5. What CMS systems are respondents using now to manage their websites and how many websites are they managing on each CMS (question 16)?
CMS
Response
% Resonse
Websites
% of Total
WiscWeb CMS
145
33%
175
9%
WordPress
201
45%
658
34%
Drupal
80
18%
260
14%
HTML/CSS
144
33%
338
18%
SharePoint
15
3%
17
1%
Google Sites
37
8%
78
4%
Other1
72
16%
277
14%
Other2
11
2%
118
6%
6. Are respondents satisfied or dissatisfied with the CMS systems they are using now? This is a summary of the data collected in questions 17, 18, and 19. For the purposes of a summary, we have combined “Very Satisfied” and “Satisfied” into one response and “Very Dissatisfied” and “Dissatisfied” into one response.
CMS
Functionality
Support
Maintenance
% Sat.
% Dis.
% Sat.
% Dis.
% Sat.
% Dis.
WiscWeb CMS
40
33
54
16
47
15
WordPress
72
4
45
16
59
8
Drupal
42
12
34
17
34
19
HTML/CSS/DW
50
20
41
19
41
25
SharePoint
15
19
10
21
11
16
Google Sites
43
9
28
16
29
12
Other1
49
15
27
24
37
22
Other2
19
10
14
9
19
10
Page 19 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
7. What is your affiliation to the university? (choose one)
Affiliation
Count
%
Staff
517
86.5%
Faculty
46
7.7%
Undergraduate student
7
1.2%
Graduate student
9
1.5%
Postdoctoral
0
0%
PA/TA
1
0.2%
Other
18
3.0%
8. Are you a “decision maker” regarding your group’s website? (choose one) “Decision Maker”
Count
%
Yes
312
52.2%
No
100
16.7%
No, but my recommendation will be accepted.
186
31.1%
Page 20 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
9. What role(s) do you play in the management of your group’s website? (select all that apply)
Role
Count
%
Campus communicator or marketing
152
28.8%
Web editor, publisher, or reviewer
342
64.7%
IT professional, site admin/custodian, account manager, server maintenance
140
26.5%
Content contributor, copy writer
313
59.3%
Owner
118
22.4%
Designer or layout editor
170
32.2%
Developer or programmer
87
16.5%
Dean/CIO/Executive Administrator
27
5.1%
Other
52
9.9%
Page 21 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
10. People who have WiscWeb CMS sites, and are planning on a new site in the next two years.
11. People who have WordPress sites, and are planning on a new site in the next two years.
12. People who have Drupal sites, and are planning on a new site in the next two years.
Page 22 of 23
Appendix 1 - CMS Assessment Committee - Findings and Assessment
WiscWeb CMS satisfaction results for people with WiscWeb CMS sites.
WordPress satisfaction results for people with WordPress sites.
Drupal satisfaction results for people with Drupal sites.
Page 23 of 23
CMS Assessment Committee – Phase I Report Appendix 2 CMS Assessment Committee – Survey Results – Without Comments
Printed 11/17/2015
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
CMS Assessment Committee - Survey Full Report, without individual comments 11/12/2015
Appendix 2 - Page 1 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What is your affiliation to the university? (choose one)
#
Answer
1
Staff
2
Faculty
3
Bar
Response
%
517
86.45%
46
7.69%
Undergraduate student
7
1.17%
4
Graduate Student
9
1.51%
5
Postdoctoral
0
0.00%
6
PA/TA
1
0.17%
7
Other
18
3.01%
Total
598
100.00%
Appendix 2 - Page 2 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Are you a "decision maker" regarding your group's website? (choose one)
#
Answer
Bar
Response
%
1
Yes
312
52.17%
2
No
100
16.72%
3
No, but my recommendation will be accepted.
186
31.10%
Total
598
100.00%
Appendix 2 - Page 3 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Does your university group currently have a website? (choose one)
#
Answer
Bar
Response
%
1
Yes
596
97.23%
2
No
17
2.77%
613
100.00%
Total
Appendix 2 - Page 4 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Is your university group currently pursuing the creation or development of a website?
#
Answer
Bar
Response
%
1
Yes
7
41.18%
2
No
10
58.82%
Total
17
100.00%
Appendix 2 - Page 5 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What functions do you envision being served by your group's website(s)? (select all that apply)
#
Answer
Bar
Response
%
1
an intranet (sharing documents, information inside our organization, etc.)
3
60.00%
2
instructional/educational content (information aimed at students, a site that students contribute content to, etc.)
1
20.00%
3
to share information with the public about our organization (college, school, department, program, center, institute, lab, research center, etc.)
3
60.00%
4
personal/biographical/research related (a professor's CV, a "research notes" blog, etc.)
0
0.00%
5
cultural/heritage/online exhibits
0
0.00%
6
events/event-related
3
60.00%
7
Student organization
1
20.00%
8
Other:
1
20.00%
Total
12
100.00%
Appendix 2 - Page 6 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Below is a list of web content management platforms or tools. Please, indicate any that you or your group has experience working with. Use the "Comments" field to elaborate. (choose all that apply)
#
Answer
Bar
Response
%
1
WiscWeb
1
20.00%
2
WordPress
5
100.00%
3
Drupal
1
20.00%
4
HTML/CSS (e.g. Dreamweaver)
2
40.00%
5
SharePoint
0
0.00%
6
GoogleSites
3
60.00%
7
None
0
0.00%
8
Other
0
0.00%
9
Comments:
1
20.00%
13
100.00%
Total
Appendix 2 - Page 7 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What will be your priorities when selecting a platform? Use the "Comments" field to elaborate. (select all that apply)
#
Answer
Bar
1
functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
5
100.00%
2
technical support (e.g. the ability to develop new features, expand the website's usefulness)
1
20.00%
3
maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
3
60.00%
4
dissatisfied with the cost
1
20.00%
5
I don't know
0
0.00%
6
Comments:
0
0.00%
10
100.00%
Total
Appendix 2 - Page 8 of 23
Response
%
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What role(s) do you play in the management of your group's website (select all that apply)
#
Answer
Bar
Response
%
1
Campus communicator or marketing
152
28.79%
2
Web editor, publisher, or reviewer
342
64.77%
3
IT professional, site administrator/custodian, account manager, or server maintenance
140
26.52%
4
Content contributor, copy writer
313
59.28%
5
Owner
118
22.35%
6
Designer or layout editor
170
32.20%
7
Developer or programmer
87
16.48%
8
Dean/CIO/Executive Administrator
27
5.11%
9
Other:
52
9.85%
1401
100.00%
Total
Appendix 2 - Page 9 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What is the function served by your group's website(s)? (select all that apply)
#
Answer
Bar
Response
%
1
an intranet (sharing documents, information inside our organization, etc.)
194
35.79%
2
instructional/educational content (information aimed at students, a site that students contribute content to, etc.)
246
45.39%
3
to share information with the public about our organization (college, school, department, program, center, institute, lab, research center, etc.)
498
91.88%
4
personal/biographical/research related (a professor's CV, a "research notes" blog, etc.)
161
29.70%
5
cultural/heritage/online exhibits
42
7.75%
6
events/event-related
292
53.87%
7
Student organization
54
9.96%
8
Other:
61
11.25%
1548
100.00%
Total
Appendix 2 - Page 10 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
How long has your group's current website existed on its current platform? (choose one)
#
Answer
Bar
Response
%
1
less than 2 years
158
28.52%
2
2 to 5 years
182
32.85%
3
6 or more years
149
26.90%
4
I don't know
65
11.73%
554
100.00%
Total
Appendix 2 - Page 11 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
You indicated that your group's current website is less than two years old. On which of the following platforms or tools was your group's website built prior to the current platform? Use the "Comments" field to elaborate. (select all that apply)
#
Answer
Bar
Response
%
1
WiscWeb
28
19.44%
2
WordPress
22
15.28%
3
Drupal
11
7.64%
4
HTML/CSS (e.g. Dreamweaver)
44
30.56%
5
SharePoint
0
0.00%
6
GoogleSites
2
1.39%
7
Other
40
27.78%
8
Comments:
28
19.44%
175
100.00%
Total
Appendix 2 - Page 12 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Why did your group migrate from the prior platform(s)? Use the "Comments" field to elaborate. (select all that apply)
#
Answer
Bar
Response
%
1
dissatisfied with the functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
78
54.17%
2
dissatisfied with the technical support (e.g. the ability to develop new features, expand the website's usefulness)
54
37.50%
3
dissatisfied with maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
55
38.19%
4
dissatisfied with the cost
8
5.56%
5
I don't know
34
23.61%
6
Comments:
61
42.36%
290
100.00%
Total
Appendix 2 - Page 13 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What were your priorities when selecting the current platform? Use the "Comments" field to elaborate. (select all that apply)
#
Answer
1
functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
2
Bar
Response
%
106
72.60%
technical support (e.g. the ability to develop new features, expand the website's usefulness)
77
52.74%
3
maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
75
51.37%
4
dissatisfied with the cost
4
2.74%
5
I don't know
25
17.12%
6
Comments:
41
28.08%
328
100.00%
Total
Appendix 2 - Page 14 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
(Optional) Please, elaborate with any other relevant details as to why the current platform chosen.
Text Entry
Ease of use was big as we do not have a dedicated web dev. From what I understand the old version of DNN was not going to work any longer on a server so we had to be moved over to the new version. We were extremely happy and impressed with the support and professionalism of Learning Support Services through L&S. cost is a major factor. we need to take advantage of campus resources that are affordable. We chose WiscWeb so we could easily and cheaply create a website for our department. I was what was available non cmapus to use for free. Support from WiscWebCMS staff to migrate our site (at no cost) was extremely attractive when choosing a new platform. WiscWeb CMS was presented and understood to be the platform of choice for the enterprise. There was no website before I started working here. I started one. I asked someone and they told me how to start one. I really didnt choose, didnt know there were other options. Align with the campus standard. We chose WiscWeb to conform to the University's "look" and to have DoIT support and training. View More
Appendix 2 - Page 15 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
We would like to know what content management platforms or tools you have used anywhere, not limited to your current website. Please, check all the relevant items below. Use the "Comments" field to elaborate. (select all that apply)
#
Answer
Bar
Response
%
1
WiscWeb
188
36.72%
2
WordPress
301
58.79%
3
Drupal
148
28.91%
4
HTML/CSS (e.g. Dreamweaver)
315
61.52%
5
SharePoint
48
9.38%
6
GoogleSites
103
20.12%
7
None
22
4.30%
8
Other
112
21.88%
9
Comments:
51
9.96%
1288
100.00%
Total
Appendix 2 - Page 16 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Please, tell us about your current web environment. Some groups on campus are responsible for multiple websites. Indicate the approximate number of websites in your group that are managed on the various platforms. Use the "Comments" field to elaborate. (select all that apply)
#
Answer
Bar
Response
%
1
WiscWeb
147
32.59%
2
WordPress
204
45.23%
3
Drupal
83
18.40%
4
HTML/CSS (e.g. Dreamweaver)
147
32.59%
5
SharePoint
15
3.33%
6
GoogleSites
37
8.20%
7
Other1
73
16.19%
8
Other2
11
2.44%
9
Comments:
63
13.97%
780
100.00%
Total
Appendix 2 - Page 17 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Where applicable, indicate your group's satisfaction with the functionality of the following web content management platforms or tools.
#
Question
Very Satisfied
Satisfied
Neutral
Dissatisfied
Very Dissatisfied
Response
Average Value
1
WiscWeb
29
60
61
49
24
223
2.91
2
WordPress
54
139
65
11
-
269
2.12
3
Drupal
22
45
73
14
6
160
2.61
4
HTML/CSS (e.g. DreamWeaver)
37
73
67
35
8
220
2.56
5
SharePoint
2
10
52
8
7
79
3.10
6
GoogleSites
13
29
48
7
2
99
2.56
7
Other1
14
22
27
8
3
74
2.51
8
Other2
1
3
15
1
1
21
2.90
Appendix 2 - Page 18 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Where applicable, indicate your group's satisfaction with the technical support available with the following web content management platforms or tools.
#
Question
Very Satisfied
Satisfied
Neutral
Dissatisfied
Very Dissatisfied
Response
Average Value
1
WiscWeb
44
66
61
24
9
204
2.45
2
WordPress
28
80
92
32
7
239
2.62
3
Drupal
16
32
71
19
6
144
2.77
4
HTML/CSS (e.g. DreamWeaver)
26
49
72
25
9
181
2.68
5
SharePoint
2
4
45
9
4
64
3.14
6
GoogleSites
6
17
48
10
3
84
2.85
7
Other1
9
9
33
11
5
67
2.91
8
Other2
1
2
17
1
1
22
2.95
Appendix 2 - Page 19 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Where applicable, indicate your group's satisfaction with the maintenance involved with the following web content management platforms or tools.
#
Question
Very Satisfied
Satisfied
Neutral
Dissatisfied
Very Dissatisfied
Response
Average Value
1
WiscWeb
36
62
77
17
14
206
2.57
2
WordPress
34
109
81
14
7
245
2.39
3
Drupal
12
36
68
20
8
144
2.83
4
HTML/CSS (e.g. DreamWeaver)
21
53
61
28
17
180
2.82
5
SharePoint
1
6
48
6
4
65
3.09
6
GoogleSites
5
19
50
7
3
84
2.81
7
Other1
7
16
26
9
5
63
2.83
8
Other2
1
3
15
1
1
21
2.90
Appendix 2 - Page 20 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
Is your group considering migrating to a new platform in the next two years?
#
Answer
Bar
Response
%
1
Yes
157
32.44%
2
No
327
67.56%
Total
484
100.00%
Appendix 2 - Page 21 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
You indicated your group is considering a migration to a new web content management platform. Below is a list of web content management platforms or tools. Please, indicate any that your group is considering for this migrating. (select all that apply)
#
Answer
Bar
Response
%
1
WiscWeb
26
18.31%
2
WordPress
88
61.97%
3
Drupal
23
16.20%
4
HTML/CSS (e.g. Dreamweaver)
9
6.34%
5
SharePoint
3
2.11%
6
GoogleSites
5
3.52%
7
None
2
1.41%
8
Other
42
29.58%
Total
198
100.00%
Appendix 2 - Page 22 of 23
Appendix 2 - CMS Assessment Committee - Survey Results - Without Comments
What will be your priorities when selecting the next platform? Use the "Comments" field to elaborate. (select all that apply)
#
Answer
1
functionality (e.g. the ability to create new pages, edit existing pages, make minor changes to appearance and layout)
2
technical support (e.g. the ability to develop new features, expand the website's usefulness)
3
maintenance (e.g. maintaining versions, installing patches, managing backups, security, etc.)
4
dissatisfied with the cost
5 6
Bar
Response
%
131
88.51%
92
62.16%
102
68.92%
8
5.41%
I don't know
12
8.11%
Comments:
48
32.43%
393
100.00%
Total
Appendix 2 - Page 23 of 23
CMS Assessment Committee – Phase I Report Appendix 3 CMS Assessment Committee – Survey Results – Comments Only
Printed 11/17/2015
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Q2_TEXT What is your affiliation to the university? (choose one) Worked on website as a graduate student; now in an interim academic staff position. Professor Emeritus Contractor (Web work) Outreach specialist, UW‐Extension, funded through CALS Professional Organization Volunteer staff and student (multiple roles ‐ there are some of us) contractor Student Web Developer (workstudy staff), undergraduate UW Hospital employee Marketing Partner/Vendor Emeritus Vendor Emerita professor Emeritus Professor
Q8_9_TEXT What role(s) do you play in the management of your group's website? (Select all that apply) Advisor and Unit Director assistant dean responsible for communications, our team is just me, one other person and a handful of students Content reviewer/approver Coordinator (or Director) of three programs with three separate websites. co‐owner with program director department administrator and development committee member Department Supervisor Developer for many other campus units, frequently refer people to shared hosting Director of Website Services Director; Chair divisional/path coordinator, I do edit two web sites also Don't play a role faculty director Give input on site content as a staff member I create information that gets posted on the Webpage regarding our program I edit and manage a site within a larger group's work. I have been in marketing, editing, designer, and developer roles. Currently I supervise those who do these functions. I maintain my own website because it is too hard to update our group's I post informatiion about events and field days happening at our station and data/results from display garden I provide campus wide services (EOH dept) Occupational Health I supervise the employee who develops, designs, and maintains it. I'm a digital project manager at a local ad agency. Liaison to web developer
Appendix 3 - Page 1 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Manager, technology group Managing data from our Filemaker system to an Oracle system which then feeds our CMS n/a na No role No roll at all none none none Not allowed to manage our website. Can give input/advice, but rarely listened to. our group website has a set of pages assigned to the sub‐unit I manage provide input and feedback to assist with design and content information Review/Recommend website interface with our management tracking database system SEO consultant Some content needs to be approved by me; any expenditures have to be approved by me Strategic planning for unit supplies purchasing, including sogftware if the order is approved These are positions from the previous academic year. I remain a resource with some authority. Two websites: one for my research group, one for my department (I am the chair) updates User will be a contributor
Q19_8_TEXT What is the function served by your group's website(s)? (select all that apply)‐Other: All of the selected above are representative of our clients. Our group also has its own informational site. also to share internally information about policies, etc. an infrastructure for many groups of research specific resources Application‐heavy assist people to identify and request services from the group Child care business, lab school (research & teaching) Communicate about our organizations services to campus patrons Communicate with faculty, staff, students and alumni Content aimed at other UW‐Madison users (administrators, staff, faculty) content distribution (files in excel, pdf, etc.) data reporting for public/student/staff/factulty Documentation for technology we have that the UW‐Madison community can use. educational content for the industry we support (non‐traditional students); short course registration; help students apply and enroll; provide policy info for students; provide resources for students and community http://snapplus.wisc.edu/ ‐ Wisconsin Nutrient Management software site industry outreach Information and gateway on how to use services for students; resource for faculty information for students (but they don't contribute) Information on programs including application links. information targeted to physicians, researchers, and advanced practitioners in academic medicine
Appendix 3 - Page 2 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Instructional content aimed at adult learners, particularly farmers; instructional content aimed at high school ag instructors Instructional content aimed at employess large campuswide initiative Marketing‐‐to recruit students to our programs My organization has built all of the above for campus organizations. Office 365 information and training for employees On‐Boarding, HR, and Payroll both Internally and Externally Organizational recruitment Our website addresses faculty, staff and student issues across campus from driver authorization to approved vendors. personal Program registration Provide researchers with knowledge of our services, web forms for selecting those services, a repository for varies printed reports and forms and assistance with the funding process. Providing central location for student leader group organization, providing central location for staff organization (multiple sites) publicize events and programs of multiple entities across campus Real‐time weather data request forms Research support resources needed by faculty, university guidance scheduling appointments Sell UW Press books through our website and provide information about the Press (esp to authors) Selling courses both non‐credit and credit. share information and resources with members share information with faculty about governance activities, mostly on campus share opportunities for grant funding, distribute research policy software assurance facility streaming Student Job Center jobceter.wisc.edu built for campus but used by Madison community also. Wisc idea, in action. technical training and organization information This site shares academic information such as degree requirements both on and off campus. to communicate with University and commercial clients / researchers to inform patrons about our services To make certain kinds of data more visible and visual, and to make it easier to access that data. to share information with critical access hospitals, clinics, nurses, hospital administrators, etc. Various Functional Group Specific Applications we would like to add intranet but have not been able to muster the required resources to do that Web access to our professional development catalog Web Hosting, CMS management, Web Development
Q14_7_TEXT You indicated that your group's current website is less than two years old. On which of the following platforms or tools was your group's website built prior to the current platform? ‐ Other
Appendix 3 - Page 3 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
AngularJS CMS Red Dot Contribute Contribute Contribute Custom ASP.net CMS Custom built CMS DIY / hand‐coded DNN Dot Net Nuke older version Don't know. Site is hosted on departments Web site don't know Dont' know what it was before migration to WiscWeb 1.5 years ago‐ the migration to "current" wiscweb site occurred before my tenure. We are revamping current layout and content of website now using wiscweb as it does not fit our needs. dotCMS DotNetNuke 7 Dreamweaver Dreamweaver Dreamweaver, along with a custom developed upload and versioning system EMS? Home‐grown CMS developed internally Homegrown with Html, java and Php I am not sure I think it was Dreamweaver, but I'm not sure Joomla Joomla Joomla joomla N/A Not sure not sure not sure, UHS IT/commuications can address this question w/your group Silver Stripe Sitefinity sitefinity There was none. Unknown Web services consumed by WordPress for data display, e.g. Library hours and services, staff directory, etc.
Q14_8_TEXT You indicated that your group's current website is less than two years old. On which of the following platforms or tools was your group's website built prior to the current platform? ‐ Comments built and maintained entirely in‐house, with sporadic student developer assistance Currently WordPress, do not recall what it was before, possibly wiscweb don't know
Appendix 3 - Page 4 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
dotCMS was free when we switched to it. Before then we had IBM WebSphere, which was expensive and very difficult to use. Have consolidated the multiple programs in our office over the past few years in an attempt to have all affiliated websites hosted in WiscWeb CMS I am not sure. We upgraded to DNN7 and I am not sure what it was prior to that. I believe it was HTML, but the main office site is Drupal I do not know I don't know, as I just started this position in eraly 2015. I don't know, but my guess is HTML/CSS I don't know; website was designed by our PA; we had to switch to Drupal I should clarify that we were on WiscWeb prior to now, but in 2013‐2014 we updated to the standard templates. Prior to that the website was being done in Dreamweaver. I wasn't around yet. new site to replace crappy old site. CMS has been good Not sure if that was the name of the platform but that was the program I used to make changes to the website. Not sure. Not sure. Was not responsible for it at that time. not sure; was not employed here at that time Our main site is based on a custom ASP.net solution. Ours is WordPress. We often do Drupal work as well. Still support sitefinity for other instances Unit and websites did not exist prior to current platform ‐ these are new resources for students and for facstaff. We bought server space from DoIT. We did not have a website We moved the site from D6 to D7. Does that count as moving platforms? we now have Wordpress but I don't remember what it was before that because CALS IT managed it then We recently migrated to WiscWeb CMS after our Drupal site was hacked. website was newly launched, did not have a prior life
Q15_6_TEXT Why did your group migrate from the prior platform(s)? ‐ Comments: also with the inability to control various user rights Biggest reason was the responsive design offered by WWCMS. Secondary reasons included better navigation and adapting a closer replication of the UW brand. CALS ARS as a group moved from the Contribute platform to Wordpress CALS made the decision to move from Adobe Contribute to WordPress. Didn't migrate ‐ started new site with WiscWeb CMS. dissatisfied with complexity of simple tasks AND difficulty of implementing larger custom functionality dissatisfied with the speed of implementation and the flexibility. WiscWeb was unknown to many outside developers ‐ so we couldn't engage external resources to support it. Dreamweaver is terrible. drupal was so clumsy Easier to have staff trained in a single platform. Additionally, DoIT support and free classes for beginner training we a huge plus
Appendix 3 - Page 5 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Found WiscWeb not to be user friendly for people maintaining the site. Overly complicated and not intuitive at all, and online documentation is lacking. Group we are part of all migrated to Wordpress. Have developers who could do work but time was scarce for that, wanted to move to a platform that allowed more, less technical, contributors to website updates and management I don't remember but I believe it had to do with not being looking current enough (layout, design, functionality) and possibly not mobile friendly I was not responsible for the migration choice, and was fine with the older system. I was very satisfied with Dreamweaver, but our Director wanted us to have a website that utlizes the UW Theme in Wordpress. It was more to have something more compatible with CALS and to have something that worked better. It was more about moving forward that dissatisfaction. Launched a new UW branded website with assistance from UW Communications LSS required the switch for security reasons. Our site was breachable and provided a way into other systems for hackers Meat Science was covered by Animal Science Website, now we have one for new facility construction updates. / / Bucky's Butchery was also through the Department of Animal Science. We were unable to access and edit the content, so we went about getting our own site. Moved from a static HTML/CSS site maintained using Dreamweaver to a dynamic CMS Moved to wisc web CMS to better align with other campus units, also for the support provieded by DoIt and the ease of use of the tool. My website is hosted by another group that made the platform choice. N/A Needed something more robust, easier to use and maintain for non‐developers, contemporary design and functionality. New site. didn't migrate No longer was free. no migration, this was just started. old‐fashioned look and functionality of the site; many changes within our office and so much needed updating, it was a good opportunity to go with the responsive design wiscwebcms Our contact ended with one provider and the new provider was selected based off a prior contractual relationship. Previous cms was cumbersome for end‐user content providers. previous version was maintained by single person in department ‐ if person was unavailable or unwilling to update, no others could contribute Rather than upgrade own unit's site to a newer version of Sitefinity, wanted to prototype in WordPress. Really outdated required by Dean's office The new sites provide more functionality the old system was clunky, hard to train someone how to use, not flexible to respond to change and not responsive for phone, etc. There were many reasons for us to switch to Wordpress and CALS‐supported template. Wordpress is quite easy to use, old HTML‐based site was clunky and hard to update. CALS was encouraging (and, I think, slowly forcing) CALS‐based departments to update their web sites anyway and use Wordpress and their CSS, so it was time to move! This is a new website Too complicated to use for our purpose
Appendix 3 - Page 6 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Too cumbersome to use and no one seemed to know how. upgrade to standard template from the unique template we were on before (see comments on previous question) UW stopped Drupal support Wanted to use templates similar to rest of the UW. And clean things up. Was no longer being supported. Told we needed to move it. Wasn't here when new website was designed. We migrated to CMS because the version we were on was old and outdated. We moved over to the CALS platform because of reduced effort for similar quality result, and for increased security. We have slightly decreased flexibility, but have better consistency of format with other Departments in CALS. we needed more than an occasional update and moved to WIscWeb to / ‐change the look to conform with most university sites / ‐allow for a blog / ‐easier to update (last site was a nightmare) We needed rebranding We needed to be able to edit and design without going through someone external. I use WiscWeb for the portal and Google Apps for the content pages. We needed to upgrade based on what we would be supported on We wanted to have content owners do their own pages. We wanted to move to a system where our websites were easier to upkeep. We were hand‐coding pages before, with several dozen web authors using dreamweaver. it just made sense to move to a CMS We were informed from the University that they are changing our website and using Word Press. We were told we were migrating to Word Press. No choice in the matter. We were unable to customize the site to make it more attractive and user‐friendly. WiscWebCMS was attractive to us because it is free and we have great support. When clients leave WiscWeb or dont' want to use WiscWeb, usability and ease of use of the content authoring platform is a big one. Our WordPress clients like it's simplicity and low barrier to entry. With our previous site ‐ content editors were responsible for knowing HTML and CSS to create their pages. We wanted an easier way for them to push content. It also allows us to have more control over the code being written to help ensure an accessible and responsive site. WordPress has way too many menu options and I get confused as to which one I need to make changes or upload something new (it's not obvious). Some options I don't seem to have ever needed.
Q32_6_TEXT What were your priorities when selecting the current platform? ‐ Comments Ability to make a responsive website Better resources available and easier to turn around a new site in WordPress over Sitefinity. Cost and availability cost and availability of support for small department with limited IT experience / ability to stay current with technology without retraining limited staff Dean's office wanted to have control of layout Desire for our website to have a similar look and feel to other UW‐Madison websites. ease of use Ease of use Free option, format is in line with university branding and fewer decisions to make regarding layout
Appendix 3 - Page 7 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Having a larger support structure at CALS, we anticipate better security and more seamless patching/maintenance than what we had trying to do everything ourselves. Hosted and supported by LSS at no cost. Other members of our staff had experience with Drupal. I didn't know there were options. I ignored cost, which I probably should pay more attention to! / I love the support I was not consulted I was not part of that decision making. It is free and the support is great, even when requesting tight turn‐around times. The trainings have also been appreciated and easy to understand. It was free with on‐going long after I'm gone free support. It was already being used by several groups on campus (as is Drupal and Wordpress but those would have cost money to create AND to maintain). DoIT is right here on campus and very accessible and knowledgable. looking for a "best practice" experience for providing user‐focused content ‐ i.e., not just for internal, not just for "us" ‐ for our stakeholders. / / branding very important, which was not true prior to current site (we love it, but most important, our users/visitors to the site seem to love it, too!) looking for something flexible that can be easily changed and adopt new design needs. Moving from Dreamweaver to a content‐based management platform was a priority due to ease of editing access. We also knew this would set us up better for future web upgrades. My group wanted to move from a custom solution to a campus standard. We wanted our departmental site to have a look and feel similar to that of other campus departments. We also wanted a CMS that was supported by campus, so my department's IT staff would not need to support the CMS. Having a centralized CMS service saves us time and money. needed to allow us to simplify content creation, manage user (editor) access, simplify technical support, and use a system supported by other support groups on campus Our choice was to hire an outside web designer or use Drupal, assisted by LSS. Due to cost, we selected Drupal. Drupal has other advantages, including ease of updating for multiple staff. Responsive design was the top priority. Reusing as much content as possible. See above; did not make the choice, don't know why they shifted. Since most application development happens in‐house, we mostly looked for a system that would be easy for content editors to use and had broad support on campus. The Dept IT people chose the Wordpress format for us. We dont like it that much The editing experience needed to be user friendly, the cost to develop (in time) needed to be low, the platform needed to be in a state of constant security updates and patches, and there needed to be a lot of good plugin support (active development community) the platform was chosen for me ‐ I had used a former, easier version of Wordpress in the past but this current version seems very advanced Time to revise the old site was more than a decade old user‐friendly for member‐contributors Users' pre‐existing knowledge of selected CMS. (Wordpress) UW stopped support for Drupal (which they had fully endorsed several years before) and offered support for CMS Wanted to take advantage of the UW technical support. We also chose WiscWebCMS in order to build redundancy within our department and enable multiple non‐technical staff to easily be added as editors. Was not involved in this. Was not our decision to change to Word Press. Wasn't here when new website was designed.
Appendix 3 - Page 8 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
We are struggling with the technical support right now because we don't know what we don't know ‐ and I think we are going to have to hire a PT expert to help with the tech side although I'd prefer to work with DoIT and not commit to a staff position right now We just upgraded what we had into a new version of what already existed. We now use Wordpress. Ease of use was key because we have distributed editing/publishing rights with staff that might only do web work occasionally.
Q16 (Optional) Please, elaborate with any other relevant details as to why the current platform chosen. Align with the campus standard. Because it was a known product. Both of our new sites are on Drupal. Drupal was selected because of it's ability to meet most of our business needs out of the box ‐ with less customization than WordPress would have likely required. The trade‐off was Drupal's admin. interface is a little less user friendly than WordPress', but it is still sustainable (non‐technical folks can update and maintain the site with minimal training). Campus support, low/no cost, ability to have various users/roles cost is a major factor. we need to take advantage of campus resources that are affordable. Ease of use was big as we do not have a dedicated web dev. From what I understand the old version of DNN was not going to work any longer on a server so we had to be moved over to the new version. I maintain the website and have used Dreamweaver in the past. Wanted to have full functionality. I wanted to keep the platform within UW; hoping to integrate with other infotech ideas (eventually) I was pleasantly surprised to learn that DoIt provided technical support on WiscWeb CMS free of charge. I took advantage of that last year so that we could make major overhauls to our site. overall, I am quite satisfied with both the way it has turned out and how user friendly it is. there is some counterintuitive parts to adding content, but I'm able to figure most everythign out. In switching to responsive design, we determined that WordPress could provide the layout we desired, with less regular updates, and and easier editor to work with It was free and supported by campus It was free, flexible, accessible to non‐technical users and doit was helpful as a resource It's a user friendly platform. Joomla was chosen as it was the platform the designer/developer we hired was most experienced with. Many others were using WP and were satisfied with it; it is easy to set up and use. Mobile friendly person responsible for content managment also uses platform for grad and undergrad catalogs, was familiar and able to use easily Primary reasons: FREE! and easily updated among our staff without the need to send all updates to one webmaster who can never seem to be found or easy to communicate with. I like the freedom of being able to learn something new and apply it right away. Sorry, I don't know anything about platforms, I just write the copy and give it to our web people. specifically looked for event handling, multiple layers of administration, very easy cms as we have over 40+ users for our site Support from WiscWebCMS staff to migrate our site (at no cost) was extremely attractive when choosing a new platform. The current platform had the best support for our LDAP
Appendix 3 - Page 9 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
There was no website before I started working here. I started one. I asked someone and they told me how to start one. I really didnt choose, didnt know there were other options. user‐friendly We chose a designer and a developer based on their capabilites, cost, and inital concepts. We then in turn, asked them to suggest a platform that would be the CMS. I didn't care too much about the platform as long as it met basic requirements of 1) Easy to update 2) Easy to teach/delegate to student employees to update 3) Easy to make iterative changes to design/functionality. 4) comfortable that we could plug "most developers" into the project should we become dissatisfied with the initial vendors. We chose WiscWeb so we could easily and cheaply create a website for our department. I was what was available non cmapus to use for free. We chose WiscWeb to conform to the University's "look" and to have DoIT support and training. We chose Wordpress because it would work with our other IT systems and we thought it would be easy to find web developers with Wordpress experience. We considered Drupal, but the core was more application‐development focused and was a bit tricky for non‐tech folks to use. Looks like Drupal 8 will improve this a lot, but it was just taking too long to get out. We copied the school of agriculture and life sciences We needed a more sustainable model. Most updated were being done by student staff but they all had different levels of experience. We needed something that was trainable. We wanted ease of maintenance. I am not a true professional, so something intuitive and easy to use We were extremely happy and impressed with the support and professionalism of Learning Support Services through L&S. When I started the project I incorrectly assumed that the department staff had some Drupal or HTML knowledge. After finding out the sad history of changing consultants every 2 years for the last decade, I discovered that there really was no good reason to stick with Drupal, but that discovery was 8 months too late. WiscWeb CMS was presented and understood to be the platform of choice for the enterprise. WordPress has so much more support and documentation than SiteFinity that makes developing, adding plug‐ins, etc. much less painful. Wordpress was chosen due to the large community, quick patches and updates, and ease of content creation / editing
Q18_8_TEXT We would like to know what content management platforms or tools you have used anywhere, not limite to your current website. Please, check all the relevant items below. ‐ Other 1 and 1 My Website Adobe Contribute AngularJS Big Rose Cargo Collective CMS Made Simple (CMSMS) CMS, red dot, dotNetNuke CMSMS, Joomla ColdFusion Contribute Contribute Contribute, Frontpage
Appendix 3 - Page 10 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Contribute, Squarespace Custom built web apps and Plone. custom CMS built by marketing firm custom coded platform created for the organization I worked for. Custom platform created by BigRose Webdesign CWIS (http://scout.wisc.edu/cwis/) Desire2Learn, DNN, Active Server Pages, Confluence, MS Exchange, UW Knowledge Base django Django CMS, Mezzanine DNN DNN DNN 7 Does Learn@UW count? DoIT's Knowledgebase program Dot Net Nuk, Red Dot Dot Net Nuke Dreamweaver Dreamweaver drupal scholar edit html files by hand Expression Engine Expression Engine Expression Engine, Craft CMS, Perch CMS, Jekyll, Square Space goDaddy, network solutions Google Drive Home‐grown CMS Html/css (hand‐coded or web templates, not Dreamweaver) HTML/CSS with non‐WYSIWYG editor (BBedit, NoteTab+) I do not know I don't know. I send updates to our IT people and they make it all happen. I'm not sure what our previous website was managed on, but it wasn't WiscWeb In house built CMS called PAT (built by e‐Health Office‐ UW Hospital and Clinics) In house custom ASP.net CMS Internal Ruby on Rails application Joomla Joomla Joomla Joomla Joomla joomla joomla Joomla! Joomla!, Mambo, Zope/ Plone, MediaWiki Joomla, MyWebSpace Joomla, RedDot (maybe that's what's now referred to as "WiscWeb"?) Joomla, Weebly JS frameworks ( Angular, Backbone, Ember ), Node.js blogging platforms ( Ghost ), Joomla ( why?! )
Appendix 3 - Page 11 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Liferay Marqui CMS Mediawiki Microsoft Front Page moodle Moodle net objects fusion, in‐house designed software NetBeans Notepad; custom‐built CMS; TerminalFour old MyWebSpace, OpenAtrium Omeka php php/my sql PHP/MySQL php/mysql php/mysql coded sites PHP/SQL Site and FTP sharing as well Plone Proprietary tool for posting news stories developed by Nick years ago Rails, Custom PHP, Jekyll rapidweaver Silverstripe, Craft, ExpressionEngine Sitecore SiteCore and .Net Applications Sitefinity SiteFinity Sitefinity Sitefinity Sitefinity Sitefinity ‐‐ the Content Management System that is used by most units within the School of Education Squarespace SquareSpace Template‐based automated generation (Sphinx) hosted on Github pages Tumblr, blogspot, blogger TypePad. Also, proprietary systems developed in my previous campus department. various proprietary systems vendor‐developed custom CMS vim :) We use the DOIt page extensively for internal policy communication. web2py Weebly weebly weebly and plain HTML code wikispaces, Frontpage Wix Wix, SquareSpace, Dreamweaver Wix.com
Appendix 3 - Page 12 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Q18_9_TEXT We would like to know what content management platforms or tools you have used anywhere, not limite to your current website. Please, check all the relevant items below. ‐ Comments Before we moved to WiscWeb, departments/programs logged into a branch of our server and dowloaded Word and/or html files. Dept public site + intranet site use Drupal 6. Plan was to migrate to Drupal 8, but delays in release led us to start developing a new dept site with WordPress. Doing okay with Dreamweaver but I think the files are getting messy. Dont know. Dreamweaver is difficult for us to use. example: http://www.uhs.wisc.edu/occ‐health/ergonomics/index.shtml Found Dreamweaver hard to use Have used google sites for other organizational support of campus wide groups. I am not skilled in web development, but have to do it to have a web presence. It would be so much better if I had a professional I could use continually. I am not sure how to answer this I am not the web programmer and do not typically use a CMS. I am the staff person willing to learn whatever platform the college decides to go with; therefore I learn enough to put our content up and maintain the site. I do not know I don't know I don't know what if the "CMS" I use is one of these. Or for that matter, what the KB is. I have had for reasons or another to use many options but other than WordPress or Drupal most are inflexiable for most needs. Drupal has been the most useful and flexiable for a wide range of purposes albeit WordPress is useful for a simple content site. I have no idea. I don't manage our station's website; my co‐worker does that. I know WrodPress but I am not sure what else I use WordPress for my personal website I usually edit my HTML by hand. Our office staff uses Dreamweaver to update the site. I'm not sure if doing a blog on WordPress counts, but I added it. I also included Google even though I've never had a live page on it, but have played around with it. I'm not sure of all content platforms we've used. I've built a lot of websites using many different CMSs and tools. But currently, we are exclusively using WiscWeb CMS. Liferay was miserable Main site is Sitefinity, others are custom coded ASP.Net or plain Apache. Most sites are in Worpdress / We also have sites written with straight / HTMl/CSS (we do not use dreamweaver) using Ruby for needed functionality. / / We have one Joomla site we are migrating off of in a a week My DNN website launched in January of 2006. I converted to CMS in March of 2012. My role is more administrative and advising News system basically works fine but has some limitations and glitches. Our college's main website is run on WiscWeb, while our news website uses WordPress. Our web site is ancient and embarassing ‐‐ we have no resources (staff time or money to hire) to improve PHP
Appendix 3 - Page 13 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Rails app integrates with the public and intranet Drupal sites via web services Since the creation of our department (formerly a division) we have used DOIT web hosting and CMS. SMPH controls format, we work through them to maintain and update content Social media could be considered relevant to this list. Our department uses Facebook, LinkedIN, and TypePad blogs to supplement our official websites because of the interactivity features on those platforms. The College of Letters & Science uses WiscWed CMS for our outward‐facing website (ls.wisc.edu), the KB for our internal, administrative content (kb.wisc.edu/ls), and an externally‐supported WordPress site for our news (news.ls.wisc.edu). Unknown. That is all handled upstairs now. Version7, bootstrap theme We (Extension specialists) are supposed to have done WordPress training but I still need to do it... We are considering a move to WordPress but the final decision has not been made. We are in a multi‐year project to migrate to WiscWeb. However, we have no control over the several lab sites we host We are moving from using Lasso to extract Filemaker data to a using data in a WordPress system from data from an Oracle database We have been using WiscWeb for our main websites, but are switching to Drupal‐‐we are in the process of making the transition and expect the new sites to be live within the next month. With the transition we will also acquire responsibility for an additional site. We may use more, but I'm not aware of it. We own/support 2 websites: one in Drupal and one in WordPress due to different vendors used in development. We're considering a redesign, using Drupal. You could have indicated that WiscWeb is the same as CSM... That would have been helpful
Q23_9_TEXT Please, tell us about your current web environment. Some groups on campus are responsible for multiple websites. Indicate the approximate number of websites in your group that are managed on the various platforms. ‐ Comments again, I do not know All of our department's research group sites, department site, event sites, etc. all websites hosted by DoIT in LAMP enviroment College of Engineering is currently switching to Wordpress Custom ASP.net based sites doit KB don't know don't know don't know what my coworkers use Don't know what platform wisc.edu, news.wisc.edu and wisconsinidea.wisc.edu are on each dept and project are responsible for their own site if they decide not be part of the SoHE site Extension websites are part of a huge project run through Extension's tech group, but ours for the smaller program I work with is directed by the specialist team that runs our program. So Extension has a huge Sharepoint site that we all hate, hate, hate and we have more local wordpress sites that confound some and work well for others. I am not sure what they used. I know how to edit it.
Appendix 3 - Page 14 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
I don't have anything to do with my groups web site so I have no idea which are used. I don't know I don't know ‐ I am using my department's website as the target of this survey, but I also have my own lab website because it is too difficult to get content uploaded reliably. I am terrible at managing my own website, but do it out of necessity. Wish there was more help or templates or something to give a professional presence with modest amounts of time/training. i don't know; i submit requests via email I have 3 "active WP sites, and 3 post‐event websites (the sites are still up, but the event is over). I have no idea which program is used, but here's the third website: http://www.engr.wisc.edu/current/coe‐ summer‐undergraduate‐research‐experience.html I think I have this right. I use GoogleSites to create informational pages for event participants. I'll pass this survey onto the web programmer integrated with KB site I've included sites we host, not just our site (which is HTML/CSS). Obviously they're rough estimates. Joomla LessonShare site is Drupal. Course website connects to department website. I don't know the platform, but I manage it through Contribute. Much depends on how one counts sites. We support sub‐sites for many libraries across campus, but these fall under the umbrella of a single site. My understanding is that a chunk of our website is still being maintained using Dreamweaver n/a not sure not sure enougn to answer Not sure how to answer this one either as I do not know what all theses platforms are not sure of others not sure; not involved in tech One of our programs runs a separate website on WiscWeb. Other1=DNN, Other2=Confluence & UW Knowledge Base Our group manages many sites on different platforms; primarily, these are WiscWeb, but we have moved away from WiscWeb into Wordpress and Google sites because of the ease with which we can create them. php for personal site and WIMR charge back PHP/MySQL website using Bootstrap Framework Plone Sitecore is used for our main website. Sharepoint for our intranet. Sitefinity or custom coded ASP.Net Some individual faculty members have their own websites that are linked to the department's site. some of our pages are in html and not drupal but linked off the drupal pages The above describes clients, not our own sites The website is in the process of being redone on a different platform‐‐csweb or wiscweb The WP site allows us to collaborate easily with outside parties. The HTM/CSS sites are used for custom data collection activities. there are also multiple sites that are no longer used actively This is for Engineering's Vhost platform. Two sites are for the Wisconsin Insect Research Collection (WIRC) and the D.K. Young lab in the Department of Entomology. unknown
Appendix 3 - Page 15 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Unknown Unknown we are attempting to reassess our drupal 6 site. But the evaluation of other CMS are not easily available We are moving to all these websites to one. We have only one website for the Institute I direct We link to shopping cart through our Chicago Distribution Center. wiscweb site in developement and not public yet wordpress is just in test right now, eventually it will replace the drupal site.
Q29 If desired, please elaborate on any of your responses to the three questions on this page. All hands‐on work with the backend of our website is done by a co‐worker. She is more qualified to answer these questions. All updates seem to mess up the online ordering system, DOIT is slow at getting these types of issues fixed. As a non‐developer, an HTML/CSS site is very technical and challenging to maintain, edit, and upgrade. Based on personal use. Not use within the University Unit Both platforms has their pros and cons. Word Press is definitely more appearance appealing but it lacks the ability to upload a file from your computer with a link that allows you to change content in your file on your computer "daily" and it is automatically available to the general public on the website. No need to re‐upload the file "daily" to replace the previous day's file. Contribute had this capability and Word Press has been a bear with trying to come up with a way to accomplish this. Box.com and Google Drive are a weak solution for this issue. Would work fine if just sharing with UW affiliated members but we deal with the general public and most folks do not have a Box.com account or Google Drive account. I do not like how it is displayed to the end user through these two avenues either. It should upload as an excel spreadsheet that they can take the information and use it to their specifications. The only way to do this in Word Press is to upload a new file to replace the previous one..."daily". Coming from an HTML/CSS design background I find the WiscWeb interface very cumbersome and unpredictable. Didn't answer as I don't know the platform used. SMPH support has been very responsive when we ask for updates to be made. Dreamweaver itself is becoming more and more of a problem. Trying to find a replacement with similar functionality is on my to‐do list. On the other hand I'm still convinced of the value of its functionality and approach for technical people who don't need a complex workflow. Drupal is a little too powerful and thus a little too much management ‐ however, we are concerned that WordPress won't give us all of the features that we need. Drupal is not that user‐friendly and it seems that most of the time, I can't take control....I can only edit basic pages that already exist. I have to go to some other person to create a new page. Not sure if it is just because I don't know how to do it or because that is the way it is set up but I can not manage the website as independently as I would like to... The people that help with it are nice and knowledgeable but also busy and it can take a few days to hear back. Our faculty want stuff immediately, and it is hard to explain to them that while I may have been trying to accomplish something, my hands were tied by not having either the knowledge or the control....or both.
Appendix 3 - Page 16 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
For much of our needs Drupal is easy to work with, maintain the sites, and expand/develop new content. When we want to get fancy we do have to engage our developers (work with DoIT AT) who are certainly able to deliver what we need to meet our business requirements. We do have to pay for those services, but they are quite worth it. Getting fixes made by DoIT on WiscWeb seems to always be a long, drawn‐out process. GoogleSites is EXTREMELY user friendly, particularly for a person like me who is not tech‐savvy at all. WiscWeb is too glitchy and complicated most of the time. When I edit text on it, the formatting gets all weirdfor no apparent reason and it's hard to figure out why or how to fix it. Hard to compare the different options. WiscWeb is a full service provider with support, templates, campus funding. With WordPress we are more or less on our own. So it's a completely different experience. I am not responsible for the above functions so can not address the questions. My staff have commented that they can figure out the basics with both Word Press and Drupal, but more than that we would have to outsource the work. I am responsible for all of this except when I need Php help. I have a freelance tech person for those matters. Also he upgrades when needed, as he's very fast. I am satisfied with our own internal support for WordPress (we hired an expert on our team to provide that service) I did not answer most of these because I did not know how to answer them I didn't fill these 3 questions out, since I don't have first‐hand experience working on or maintaining our website. I've only contributed small amounts of content which were loaded by someone else. I do not do any of this myself for our department. I did use GoogleSites for my own website and did not like it. Overall, I wish that I could keep a Wisc domain name but use a website template for my lab so that the address made sense and it was easy to keep updated (but that is not the department's site). I don't know any of this stuff. I am not the person in my group who should be completing this survey. I don't know what these questions are asking. Who is providing the maintenance, technical support? I find WiscWeb difficult to use. Continually looking at help docs. The staff is helpful and willing to fix things for me, which I appreciate. WordPress is a lot easier to use, but have a VERY difficult time getting technical help from those running the server. Takes days to get a reply back and the general feeling is that it is a burden to help. There are always "more important" projects going on. I have asked for some assistance on the technical support aspect, and have received mixed results. I also work with a freelance programmer, and that has been helpful. / / The only maintenance I am aware of is that I have a test site, and my site gets backed up on a regular basis. And I am OK with that. I left certain questions blank because I don't have experience with them related to the questions asked. I only have responsibility for HR content and don't know the platform we use. I only use DreamWeaver/Firezilla and WiscWeb. Others in our group use other platforms for their personal/professional pages. I know VERY little about DreamWeaver/Firezilla ‐ only what someone has shown me to make updates to certain pages. Not NEARLY as user friendly as WiscWeb I pay for Big Rose to manage my site. It's expensive but worth it. I really appreciate that WiscWeb is supported by DoIT. We have an in‐house web expert, but when he is not around, having the ability to seek needed help on a short timeline has been invaluable to getting critical web updates published. I seldom contact DoIT, but when I sought help for web hosting issues, I got good response. I loved the 15‐minute listening/questions sessions you set up. Lots of good info. I think WiscWeb CMS is really clunky and not at all intuitive. But I AM over 40 years old. :‐) I was neutral on most of these since I personally don't have to maintain them, nor do we currently rely on persons outside our group to maintain our sites. We (my colleagues) maintain our sites.
Appendix 3 - Page 17 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
In a way, we are very satisfied, because things tend to work really well. I can't put that though, because it's not clear that there are no issues, only that we don't know of any issues. It would be nice to know more clearly that things are well‐maintained and secure. In general, the WiscWeb team is responsive to technical requests and works to make things fit into the CMS template and meet our needs. / The CMS product itself is clunky and has too many steps for most actions. This is a hindrance to content management and makes us spend more time updating our website than we would prefer. It will be beneficial to have a CMS technical support phone number. It will be more convenient and clear to talk to a person, when explaining how to do step by step instruction, in comparison to email. It's tedious how, in WiscWebCMS, every change involves clicking the "red dots" multiple times (eg, first to open text field then again to edit text field) when one click theoretically should open a page or text field. "Page Information" doesn't open it the first time, it has to be clicked again. Also, the posting process could be streamlined and made easier. limited experience‐‐ i find the wiscwebcms support very responsive (except for maybe some development features we'd love to have, but I realize these can be more problematic) LSS staff rocks! very helpful, listen carefully to find out what our needs are, deliver excellent solutions Many basic things are blessedly easy in Wordpress, but for anything more complicated (Javascript, adding widgets), assistance from CALS (and, for another site I manage for a unit outside CALS) is limited ‐‐ there just isn't enough staff time to help with advanced web development. For the site I help with outside CALS, we hired a private Wordpress consultant to develop our site's architecture. Having the staff time to do that kind of work at no cost to campus units would be fantastic, though I am very, very grateful for the help available now and the professionalism of the people providing it. Many times when you request help with things immediately you never get a response... & NO one answers their phone. Matt Goins has been outstanding at helping us bring our website into NIH compliance! MIS dept. is great, it's just not right for our website as we need to be able to update content ourselves Most CMS providers(wordpress, joomla, etc) don't offer any kind of direct technical support, so that was difficult to answer. WordPress is superior in the sheer volume of information and experience from other users and forums, and it has helpful documention. I have answered "neutral" to questions I don't know how to answer. Most of our websites are constructed in house by professional developers. They provide all technical support, maintenance, training, and any other functions that are necessary for the sites to function. Our most popular site is run in a similar manner with dedicated support from our the provider. My experience with DoIt has been positive. Some things take more time than I'd like or require a second reminder, but overall the site came together well and is serving our needs much better than our previous Html based site. My group greatly benefits from a campus‐supported hosted CMS. no clue on any of these questions No support available on campus for maintenance or development of smaller department web sites. This reflects badly on the University. We are an internationally‐acclaimed research and publication project, and our web site is an embarrasment. University Communications nor L&S would assist, even during the launch of a major publication, even with over 6 months pre‐publication notice. Our academic department came through to the best of their ability ‐‐ and we are immensely grateful. But our overarching web presence is an absolute dinosaur. Needs major overhaul, and no resources avail for that to happen. Not being a coder/programmer by trade and having learned Dreamweaver on the job, I find that mechanism extremely cumbersome and difficult to manipulate and/or change. Not familiar enough about these choices to answer questions
Appendix 3 - Page 18 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Not user friendly and support personnel were way too over loaded to provide assistance quickly. On the previous page of questions, you said that we should list which CMSs and tools we've used anywhere, even if it doesn't relate to your current site. I've used many tools in the past but now we are exclusively using WiscWeb CMS. Therefore, I don't feel it is pertinent to respond to my "group's satisfcation" with the other tools since we don't use them and have never used them in THIS group. I used them in previous jobs I held. Because of this, I answered "Neutral" for all of the other CMSs. It just doesn't make sense for me to comment on behalf of my group if they haven't used them or they weren't used while on campus. The support/maintenence/functionality does not relate. One reason we moved platforms is that we could not reliably depend on help from DoIT with our WiscWeb site. They were unresponsive/slow and often just didn't do what we asked. They also had no ability to translate between our needs and the technical aspects of a web project. Our course website is old and our department doesn't seem to have the time to integrate it. This is the website I'm referring to with HTML/CSS. I update using Contribute and sometimes Dreamweaver but can't do much with the way it's set up, which is complicated. Our department hired a person for a three‐year contract to convert websites to WordPress. However, as of the end of that contract the department does not have a specific person to help with WordPress questions or problems. Our dept site is simple, yet totally functional for our needs, in order to keep down costs (a key driver for my dept). Our Drupal sites are externally hosted (not my decision or my recommendation). Our group does not expect anything more than solid hosting performance/uptime for our application's environment. We haven't had any problems with DoIT in this respect, but we did have issues before moving to DoIT. Our in‐house system is based on 10+ year old technology and presents many user experience shortcomings, including requiring multiple entries for the same piece of data, in multiple places Our office operates with a very small budget. We'd been hoping to be set up with a system that would require low programming costs for maintenance. Unfortunately, thanks to over‐customization and zero documentation, we've had to pay an experienced programmer who has spent the past 4 months trying to fix the many bugs that have arisen. We're currently stuck back in WP3.6. When (if) we ever get to WP4.1.1, we face the prospect of being stuck again as major parts continue to break moving forward. / / Read: We're experiencing extreme frustration at spending so much time and effort setting up a system that's already grievously out of date with no clear path to updating. That said, we're very happy with a number of the out‐of‐the‐box plugins. Our site does not have a content management system, which makes having an up‐to‐date website impossible for an organization as large as ours. Our site would be great if we could use Dreamweaver, but instead, due to its age and legacy, we use Microsoft Web Expression, which is absolutely awful. Out of all of our web platforms, we are most dissatisfied with the WiscWeb CMS (I know this feeling is shared by many others actorss campus): Our site is non‐responsive, we don't have access to certain content areas that our group has the expertise to manage, leading to content and update bottlenecks, and the University‐provided designs and web layouts are outdated, and not compelling for externally‐focused content. / / We've invested in a custom Wordpress theme for our news page to get around the outdated design and layout issues, and to give us more flexibility in displaying out news and outward‐facing content. The site is hosted and maintained by a private company, which isn't ideal, but we don't have a Wordpress developer on staff, nor will we be getting one any time soon. Web is so important, but I get the sense that campus, in general, is lacking in web resources. / / Site responsiveness remains a huge issue. None of our content is responsive, and that is our number one priority in any site redesign.
Appendix 3 - Page 19 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Q39 ‐ I feel like the IT staff in CALS are great, but they are very understaffed. I've tried to contact them about website issues and it takes forever for anyone to respond, and then there is no way to track where the IT staff is at in terms of completing my request. It would be nice if there was some ticket system or something. SharePoint is a nightmare to customize anything on, good for out of the box but otherwise would avoid. Sitecore is completely customizable and for the most part easy to use and server side API can do just about anything. Sitefinity is not the worst. But the support we receive from this company, which is located overseas, is not good. When major system "upgrades" take place it is not at all uncommon for certain aspects of our website to break down/become unusable. It would be AWESOME if one vendor was used by all those across UW‐Madison ‐‐ and then well supported SiteFinity is really cumbersome to maintain and get technical support on. It doesn't meet all of our technical needs, and often the needs it is supposed to meet, it does poorly. It would be great to have a campus‐level recommended CMS. Technical support is rated as neutral since I haven't had any issues lately in order to rate the support. The CMS has worked for us, but it was complex and cumbersome to set it up, and there was a long learning curve. Now that we've gotten through the "growing pains," it works just fine. When a large number of people update files within the CMS, and each of those files needs an authorization package, administrative work can become quite time‐consuming. It's easy to edit within the CMS, but the many, many steps involved to maintain it and to publish were overwhelming for the first year. Even now, several years later, I find myself plodding through some of it and consulting the campus Knowlegebase, especially if it's a step (such as setting up an authorization package) that I haven't attempted in a few months. Having said all this, I realize that technological changes are often time consuming, regardless of the software or system. I would likely face similar challenges with any content management system! Could be that this is not unique to WiscWeb at all but that it is just a fact of life when we use technology! the member of our group who actually works with the group's website would be in a better position to answer these questions. I personally am dissatisfied with the website because I would like to be able to update it myself, but it is designed so only our staff member can do so‐‐and he's too overworked to get to the changes in a timely manner. The question not asked here: What tool do you use to host your site. We recently moved from local hardware to a cloud server, Pantheon. This has some negative effects for the easy of use of our content. The site to submit a support online never works so I end up having to email someone. The "Submit a Desktop support request" hyperlink here: http://it.cals.wisc.edu/it‐support/ The WiscWeb people, from developers to tech support, have been superb from the very beginning in helping us create and then launch our Cytotechnology Program pages. Their ongoing responsiveness when we've had the occasional issue arise has been invaluable. Re: WordPress. Although this is run on our in‐house (WSLH) server(s), it has been far more problematic for us in that we went through several developers during our migration from our old CMS to WordPress. We now have a fantastic support person who knows WordPress and its idiosyncracies when being used as the platform for our large site, so really have no negative comments in this area. Overall, I'd say we (the State Lab) is very well‐served by its web platforms and the people who support them. There are many functions that we wanted for our website that couldn't be obtained through drupal, including some drop down menues that would be helpful.
Appendix 3 - Page 20 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
There are some 'glitchy' or quirky side of CMS, especially with different browsers render things differently. As far as maintenance and technical support from Cathy Riley's team has been exceptional. The team is responsive and seem to be on the same page (left hand knows what right had is doing), which is important for end‐users. They communicate in a succinct and with the normal CNN English, which I like. In a nutshell, they give me a piece of mind. There is a lot of on‐line technical support available. Within CALS, there is technical support available, but it is not always available in a timely manner. There is an individual in CALS working as a web developer/designer who has the role of administrator for both Meat Science's and Bucky's Butchery websites. He is very qualified and knowledgeable, but has a bit too much on his plate to pay attention to smaller sites such as these. Our web presence is stunted by his inability to tend to our sites' needs. Both sites run 'okay'. I wish there was more I could do for these websites, but the way UW's wordpress sites are structured is different than other WordPress sites I have managed. / / It would be great to host an instructional meeting that would walk‐through the different layouts, widgets, functions, and visual capabilities that UW WordPress sites can have. there is no support for website development or mainteance Updates to Wordpress are needed in order to increase the user functionality. Right now, the widgets we are allowed to use are drastically out of date, negatively effecting users We are an academic department and we put our main page in drupal but some things we've left in html as they are easier to edit. I personally find editing a drupal page a bit challenging. It isn't as easy as you'd think it would be. We are shut out of certain functions on the website, but it is impossible to get the owner of those functions to answer questions or make changes. also very difficult to get new websites for specific short term purposes, like a conference. We are still early in using the WiscWeb for our website. We have many parts to the website, and DoIt WebCMS has been quite helpful in meeting with us to understand our website design needs and have been good about coming up with compremises so they can help us create a good website template given our timeline and needs. We don't have a COE admin anymore. Although I was satisfied up until end of August, it is unclear of how the support can look like in the future. / The html site makes maintenance with graduate students complicated in comparison to WordPress. However, to get the full functionality needed with a WordPress site, an admin would need to put significant hours in the migration, which is also not feasible. We find Wordpress clunky to use and our IT people do not want to alter the prescribed themes to fit our needs and we at this point feel that the current theme/layout does not really reflect our needs or present our group to the public the way to want it presented. We have a Wordpress website that we have updated and maintaned by an outside company. We have had multiple issues with the WiscWeb CMS, mostly in terms of editing our website...and things not showing up as we typed! The fonts are weird; we type one thing, but it saves in a different format, etc. We have had our WordPress sites hacked. While this is not a frequent occurrence, it is extremely time consuming to fix them. We like being able to maintain our own website and make the text/layout changes we desire, without multiple levels of permission invovled. We need a database system to track volunteer hours for people who have taken a course and must then volunteer in the community. They enter their hours by logging into a dashboard. Currently use Drupal and it is terrible for this. All kinds of problems, limitations, even the simplest thing can't be done (such as finding total hours per year). We provide our own technical support and maintenance for our sites.
Appendix 3 - Page 21 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
We use DoIT's Shared Hosting services, no complaints at all, they are very responsive to any issues that come up. We were early adopters of the WiscWebCMS, and do not have some of the functionality of later installs of the CMS ‐ partcularly a dashboard for the web manager to edit CSS. We have to contact tech support and have them edit some aspects of the site, and add users. The biggest problem we have had with the WiscWeb CMS is that it has remained problematic to have all content contributors post content on their own ‐ a small team of staff who know the CMS end up posting content for everyone else. We also have had problems embedding newer media and external content (e.g. Google maps) into pages on the site ‐ Web2py allows us to have control over each aspect of the websites but requires someone with more coding skills to make edits and updates. We are currently switching all websites to drupal, we are loosing some control over the design of the website and features but it will allow content creators to have more ability to update and make small changes to the website with out a developer We've got great technical help for our WordPress websites ‐ we'd just like more time/attention from our tech support people. They are stretched thin, however, helping many groups. When we moved to WordPress we were advised to use Carrington Build by the campus group we hired. We will be moving to PageBuilder in WordPress because of the issues we've had with Carrington Build. WiscWeb is clunky, cumbersome, and inflexible. / The support folks are helpful and do the best they can given the limits of the system. WiscWeb is easier to set up than maintain. Most of what we do is add new content to old pages. Wiscweb is not hard to use, but it has a mind of its own. I am often heard yelling at it for doing something it shouldn't. WiscWeb is stunningly, unbelievably, hideously awful. Outages are frequent and it often "misbehaves" in impossible‐to‐troubleshoot ways. I'm pretty nerdy, but even I can't convince WiscWeb that I'm allowed to edit MY OWN PAGE on the department website! RedDot is junk. Please get rid of it. WiscWeb is the worst web design/management tool I have ever used including text editors where I had to write all of my own html. Word Press is better for multiple contributors and smooth transition from one year to the next of new administrators/contributors. Expression Engine worked well for a limited number of contributors because it is counter‐intuitive but it had awesome video tutorials for the features we used Wordpress feels pretty limited, particularly when you are talking about core functionality and user permissions. It is easy to use out‐of‐the‐box though. WordPress seems the most agile with updates, patches. Easier to use. We have fewer technical developers now than when we originally chose Drupal. Drupal 6 is outdated and waiting for an 8 release was no longer an option. Unhappy with the slow development time for Drupal 8. Seems like it's become bloated. Would like it better if it had search functionality like KB has. Would like more informational resources available on campus for managing sites. All changes to our website are maintained through a member of our technical support staff and are dependent upon their schedule after changes are submitted. Although very capable personnel are hired to help problem solve with our Word press hosted website, they are rarely available or do not respond to requests for help in a timely manner. I can't really speak to the technical maintenance question (esp. vis a vis other platforms) since I am not responsible for it. I am on the content side of things. As for function, it meets our needs overall, but it sometimes seems complicated to add new features if they don't 'play well' with how Drupal behaves. I don't know what was used in the past, or what is used currently and am not familiar with any of the platforms you mention above. An option (person) to update the current sites is DIRE at this point given the person who was doing this was laid off this summer and nobody was slated to take over her duties.
Appendix 3 - Page 22 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
It's great that there's a free system with support on campus, but the user interface is pretty unintuitive, the CMS site seems to be down a lot (I frequently can't get in to make changes to my site), and the DoIT staff is very over‐ extended so it sometimes takes them quite awhile to get back to us (although we always really appreciate their help). Our website transition to Drupal is still in transition. There is one section (Archives) of our old website that has been very difficult to transition. We had to hire an LTE who worked many many hours to transition from our old system to Drupal; it was very expensive. On the whole, we are pleased with Drupal. Sorry, but my responsibility doesn't extend far enough to comment! There's tech support? JK. Kindof. Been running the UW SJC with student employee programmers for so long, it's... a very strange transition to have to now outsource for tech support and work with someone who's not a student. The student emps really assumed responsibility for the site. They were proud of the SJC, serving their peers, the campus and the Madison community and were always trying to improve the site, as if they owned it. It was a good situation. Very disappointed that SharePoint is not included in Office 365. We have a hard time finding someone on campus to update our drupal site. It was developed off‐campus. We have contacted DoIT several times to hire an expert to update it. It would be helpful if DoIT had a designated drupal team that could be hired to update, help with technical issues, etc. We have a webmaster that we can contact for help but she is part time and sometimes it takes awhile to get responses. Communication from people above her has not always been great but it works OK. We would love if there was a centralized or multi‐site approach to updating and maintaining WordPress and/or Drupal sites. Oftentimes we recommend customers enable auto‐updates to base WordPress for this reason, but this does risk breaking custom functionality ‐ but it's better than leaving security holes open. WiscWeb is a nightmare to add content to. I have less experience with wordpress. Having owned Drupal sites in the past I found keeping the code current to be difficult. Upgrading tended to break modules and settings in ways that were hard to track. A problem that stemmed from the mingling of settings and content in the database. WiscWeb is not intuitive ‐‐ that's probably it's biggest drawback. I still get confused and I've used it for three years and am comfortable with technology. I was hoping to have more of our staff use it to edit and publish their own content, but it's too complicated for those who only make updates a few times per year. Would like to be able to have/maintain a more updated, modern looking site without having to request customizations through the development team. I have been told the template is boring and bland.
Q30 (Optional) Please, list the primary websites or URLs for which your group is responsible. acdtl.dcs.wisc.edu all sites within the ohrd.wisc.edu platform soon to be switched over to talent.wisc.edu apir.wisc.edu aqua.wisc.edu / seagrant.wisc.edu / wri.wisc.edu / wisconsinshipwrecks.org / eatwisconsinfish.org arboretum.wisc.edu artsinstitute.wisc.edu / arts.wisc.edu / thestudiopresents.wordpress.com / artsenterprise.wisc.edu / madisonearlymusic.org artsinstitute.wisc.edu / arts.wisc.edu / wifilmfest.org asm.wisc.edu babcockhalldairystore.wisc.edu biochem.wisc.edu / ipib.wisc.edu
Appendix 3 - Page 23 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
biology.wisc.edu (in redesign); science.wisc.edu (newly aquired, being redesigned); wiscience.wisc.edu (in design) btp.wisc.edu bus.wisc.edu bus.wisc.edu (Sitecore) / beta.bus.wisc.edu (Sitecore) / connect.bus.wisc.edu (SharePoint ‐ Intranet) bus.wisc.edu, pubs.bus.wisc.edu, multiple applications on apps.bus.wisc.edu, beta.bus.wisc.edu, admissions.bus.wisc.edu, inquire.bus.wisc.edu, connect.bus.wisc.edu, and I am sure I am forgetting a few. cals.wisc.edu / news.cals.wisc.edu / ecals.wisc.edu / grow.cals.wisc.edu canes.wisc.edu careers.ls.wisc.edu cfli.wisc.edu / greeklife.wisc.edu / guide.cfli.wisc.edu chazen.wisc.edu Chem.wisc.edu, I do the inorganic and chemical Biology updates. chem.wisc.edu; all faculty group sites at [faculty name].chem.wisc.edu (~40), for example, bertram.chem.wisc.edu; etc. cias.wisc.edu, uncommonfruit.cias.wisc.edu, ecofruit.wisc.edu, organic.wisc.edu, agof themiddle.org, grazing.wisc.edu, cias.wisc.edu/curriculum,, cias.wisc.edu/dairysch.html, agofthemiddle.org cnerg.engr.wisc.edu / fuelcycle.org / svalinn.github.io College of Engineering continuingstudies.wisc.edu/advising (moving to Doit server in next year) / continuingstudies.wisc.edu/visp (soon to be visp.wisc.edu ‐ changing to Doit server) ctri.wisc.edu dare.wisc.edu / darewordscount.com discovery.wisc.edu/lel; healthsystem.engr.wisc.edu doit.wisc.edu, cio.wisc.edu, itc.wisc.edu, sts.doit.wisc.edu, tt.doit.wisc.edu, doitnet.doit.wisc.edu, 365transition.wisc.edu doit.wisc.edu, doivent.doit.wisc.edu, cio.wisc.edu, it.wisc.edu
[email protected] /
[email protected] /
[email protected] ecalsforstudents.wisc.edu, fisc.cals.wisc.edu, cals.wisc.edu/careerservicesblog, ambassadors.cals.wisc.edu, studentcouncil.cals.wisc.edu, chars.cals.wisc.edu, ip.cals.wisc.edu education.wisc.edu / Off this website we host nine department home pages (art.wisc.edu; dance.wisc.edu; ci.education.wisc.edu; counselingpsych.education.wisc.edu; elpa.education.wisc.edu; eps.education.wisc.edu; edpsych.education.wisc.edu; kinesiology.education.wisc.edu; rpse.educuation.wisc.edu; wiscape.education.wisc.edu energy.wisc.edu / glbrc.org english.wisc.edu ergo.engr.wisc.edu Filling this in reduced annonimity of the survey. General Education Requirements page genetics.wisc.edu / intranet.genetics.wisc.edu ghi.wisc.edu http://academic.son.wisc.edu/localnet/ / http://www.son.wisc.edu/ / http://academic.son.wisc.edu/studentnet/ / https://uwsonat.wordpress.com/ / http://winrs.son.wisc.edu/ http://advising.wisc.edu/ / http://advising.wisc.edu/facstaff/ http://afroamericanstudies.wisc.edu/ http://aos.wisc.edu/index.htm
Appendix 3 - Page 24 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
http://arlington.ars.wisc.edu/ http://bjb.engr.wisc.edu/ http://cfli.wisc.edu/index.htm http://community‐food.org, http://foodlinkmilwaukee.org, http://fyi.uwex.edu/foodsystemstoolkit, http://urbanagriculture.horticulture.wisc.edu http://continuingstudies.wisc.edu/ http://continuingstudies.wisc.edu/advising/ http://cqpi.wisc.edu/ http://education.wisc.edu (and all subsites spanning departments, programs and projects across the school), http://dance.wisc.edu, http://art.wisc.edu, http://wiscape.wisc.edu http://facilities.fpm.wisc.edu/index.htm / https://fpm‐www3.fpm.wisc.edu/campusplanning/ / http://www.cpd.fpm.wisc.edu/ / http://www.ehs.wisc.edu/ / physicalplant.wisc.edu / https://fpm‐ www3.fpm.wisc.edu/spacemanagementoffice/Default.aspx / http://www.eid.fpm.wisc.edu/ http://forward‐madison.org/index.html http://german.wisc.edu/ http://german.wisc.edu/ http://greenhouses.ars.wisc.edu/ http://hamers.chem.wisc.edu / http://sustainable‐nano.com / http://susnano2.chem.wisc.edu / http://susnano.chem.wisc.edu Http://journalism.wisc.edu http://labs.russell.wisc.edu/wirc/ / http://labs.russell.wisc.edu/younglab/ http://lancaster.ars.wisc.edu/ http://limnology.wisc.edu/ / http://limnology.wisc.edu/Library/LimnologyLibrary/ http://lsc.wisc.edu/ / http://scimep.wisc.edu/ http://marshfield.ars.wisc.edu http://materials.wisc.edu/ / http://acceleratornetwork.org/ / http://wiscmat.org/ http://news.cals.wisc.edu/ / http://ecals.cals.wisc.edu/ / http://ars.wisc.edu/ http://ntp.neuroscience.wisc.edu / Neuroscience & Public Policy...currently being created in WiscWeb CMS...not yet live http://nutrisci.wisc.edu/ / http://ghi.wisc.edu/education/undergraduate‐certificate/ http://pbk.wisc.edu/ / http://www.lssaa.wisc.edu/scholarships/ http://provost.wisc.edu/ http://provost.wisc.edu/ http://provost.wisc.edu/assessment/ , https://provost.wisc.edu/inside‐assessment/ http://scandinavian.wisc.edu/ http://scout.wisc.edu / http://atecentral.net http://slhcmsprod / http://cytotechprogram.wisc.edu http://snapplus.wisc.edu/ / http://dev.snapmaps.snapplus.wisc.edu / http://alpha.snapmaps.snapplus.wisc.edu / http://beta.snapmaps.snapplus.wisc.edu / http://release.snapmaps.snapplus.wisc.edu http://spooner.ars.wisc.edu/ http://uwpress.wisc.edu/ / http://uwpress.wisc.edu/journals/index.html / http://www.uwpress.org/ http://wgnhs.uwex.edu http://wipac.wisc.edu/ / http://icecube.wisc.edu/ / http://meetings.wipac.wisc.edu/ / http://universe.wisc.edu/ / http://icecube.wisc.edu/masterclass/ / http://ara.wipac.wisc.edu/home / http://hawc.wipac.wisc.edu/home / http://internal.icecube.wisc.edu/ http://wiseli.engr.wisc.edu/
Appendix 3 - Page 25 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
http://www.adrc.wisc.edu/ http://www.anthropology.wisc.edu/index.php http://www.biotech.wisc.edu http://www.bussvc.wisc.edu/ / http://intranet.bussvc.wisc.edu/index.htm http://www.bussvc.wisc.edu/purch/ / http://www.bussvc.wisc.edu/shopuw/ http://www.bussvc.wisc.edu/risk_mgt/risk_mgt.html http://www.cals.wisc.edu/ http://www.cals.wisc.edu/ / http://news.cals.wisc.edu/ / http://ecals.cals.wisc.edu/ / http://grow.cals.wisc.edu/ http://www.cals.wisc.edu/HR/index.html http://www.chem.wisc.edu/areas/clc/ http://www.doit.wisc.edu/services/workload‐automation http://www.ehs.wisc.edu/ http://www.english.wisc.edu/english100/ / https://lessonshare.lss.wisc.edu/eng100/ http://www.english.wisc.edu/esl/ http://www.engr.wisc.edu/current/coe‐summer‐undergraduate‐research‐experience.html / http://www.engr.wisc.edu/future/coe‐opportunities‐in‐engineering.html / http://www.engr.wisc.edu/current/coe‐graduate‐engineering‐research‐scholars.html http://www.engr.wisc.edu/isye‐index.html http://www.engr.wisc.edu/mse.html http://www.entomology.wisc.edu / http://www.plantpath.wisc.edu / http://www.fwe.wisc.edu / http://labs.russell.wisc.edu (and all subsites, including www.russell.wisc.edu) http://www.geography.wisc.edu/histcart/ / attempting to improve web presence by using Facebook: https://www.facebook.com/HistoryofCartographyProject http://www.housing.wisc.edu, http://intranet.housing.wisc.edu http://www.library.wisc.edu/ / https://gobigread.wisc.edu/ / http://uwdc.library.wisc.edu/ (This is currently a Joomla site... new WP site going live on the 28th) http://www.ls.wisc.edu/careerinitiative.html / http://careers.ls.wisc.edu/ http://www.med.wisc.edu/education/mstp‐mdphd/medical‐scientist‐training‐program‐mstp/390 http://www.ntp.neuroscience.wisc.edu http://www.physic.wisc.edu/ http://www.secfac.wisc.edu/ / and, with about as much maintenance, the KB: https://kb.wisc.edu/sof/ http://www.slis.wisc.edu/ http://www.slis.wisc.edu/ (WiscWeb) http://portfolio.slis.wisc.edu/ (WordPress) http://www.slis.wisc.edu/studentorgs.htm (straight HTML, I believe) http://www.ssc.wisc.edu http://www.uhs.wisc.edu/occ‐health/index.shtml http://www.uwsc.wisc.edu/ http://xray.engr.wisc.edu http://zoology.wisc.edu/ / https://damschenlab.zoology.wisc.edu/ http:/www.waisman.wisc.edu https://admissions.wisc.edu https://continuousassurance.org; https://www.mir‐swamp.org https://kb.wisc.edu/ecms / https://forms.imaging.wisc.edu https://kinesiology.education.wisc.edu/ / https://kinesintranet.education.wisc.edu/ https://mcmahonlab.wisc.edu/ (including a private login‐only section) / https://uwmcmahonlab.wordpress.com/people/
Appendix 3 - Page 26 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
https://socwork.wisc.edu / https://intranet.lss.wisc.edu/sw / https://sswportal.socwork.wisc.edu/ / http://ccwp.wisc.edu/ https://sohe.wisc.edu/research‐development/preschool‐home https://www.math.wisc.edu, https://atrium.math.wisc.edu, https://www.math.wisc.edu/algrtg, https://www.math.wisc.edu/apam, https://www.math.wisc.edu/talentsearch, https://www.math.wisc.edu/mathclub https://www.rarc.wisc.edu https://www2.fpm.wisc.edu/support/index.htm / https://wiscwebcms.wisc.edu/cms/WebClient/SmartEdit.aspx I am responsible for the University Records Management portion of the Archives site through the Library. http://www.library.wisc.edu/archives/records‐management/ I am responsible for the University Staff Shared Governance website, https://ous.wisc.edu/index.htm I do not know if my group is moving to a new platform, that is not my area I maintain and support three UW site: history of science dept, medical history dept, and body donor web pages ictr.wisc.edu / mentoringresources.ictr.wisc.edu / uwictr.wordpress.com ictr.wisc.edu, mentoringresources.wisc.edu ils.wisc.edu irh.wisc.edu / This is the Institute for Research in the Humanities, which I direct. I oversee the web site copy and design but do not do any of the technical work myself. Thus I couldn't answer a lot of your questions iss.wisc.edu/reach / iss.wisc.edu/mfis/index.html / iss.wisc.edu it.cals.wisc.edu languages.wisc.edu / languageinstitute.wisc.edu / sla.wisc.edu / russianflagship.wisc.edu law.wisc.edu / library.law.wisc.edu / gargoyle.law.wisc.edu library.wisc.edu library.wisc.edu, gobigread.wisc.edu library.wisc.edu/news. Forthcoming: UW‐Madison Libraries Digital Collections, Shakespeare in Wisconsin. ls.wisc.edu / news.ls.wisc.edu ls.wisc.edu / news.ls.wisc.edu / ks.wisc.edu/ls (and kb.wisc.edu/ls/internal) lsc.wisc.edu maresgroup.ophth.wisc.edu / sites.ophth.wisc.edu me364.me.wis.edu, seniordesign.me.wisc.edu meatlab.ansci.wisc.edu / meatsciences.cals.wisc.edu medicine.wisc.edu morgridge.wisc.edu morgridge.wisc.edu / wwb.wisc.edu mph.wisc.edu / wicphet.org mrsec.wisc.edu / uwamic.wisc.edu / education.mrsec.wisc.edu ncra.info / www.nc‐climate.org northcentralwater.org, http://conservation‐training.uwex.edu nutrisci.wisc.edu occfr.wisc.edu Office of the Registrar patientpartnerships.org, cppadvocacy.org, online.cpp.wisc.edu pec.engr.wisc.edu / 3Dprinting.wisc.edu
Appendix 3 - Page 27 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
personal: http://wilson.engr.wisc.edu/ / For other sites, I'm the developer but not the owner: / Waisman chargeback: https://ctc.waisman.wisc.edu/charges/ / WIMR chargeback: https://cress.cae.wisc.edu/showLogin.pl pharmacy.wisc.edu, apps.pharmacy.wisc.edu, ce.pharmacy.wisc.edu plantcare.wisc.edu / dcsmithgreenhouse.cals.wisc.edu pophealth.wisc.edu pophealth.wisc.edu / show.wisc.edu Primate Center, Stem Cell and Regenerative Medicine Center. I am contribute to content for each site as a communicator and editor, but I have IT people doing the tech stuff. psych.wisc.edu publicart.wisc.edu radiology.wisc.edu registrar.wisc.edu; ordertranscript.wisc.edu; veterans.wisc.edu; aac.wisc.edu; scandinavian.wisc.edu seasia.wisc.edu / seassi.wisc.edu / hmongstudies.wisc.edu softmoney.son.wisc.edu / https://sites.google.com/a/wisc.edu/softmoney/ / https://sites.google.com/a/wisc.edu/t2trcertificate/ / https://sites.google.com/a/wisc.edu/research‐project‐ management/ / https://sites.google.com/a/wisc.edu/qualitative‐and‐mixed‐methods‐resources/ sohe.wisc.edu tt.doit.wisc.edu uhs.wisc.edu Undergraduate Catalog http://pubs.wisc.edu/ug/index.htm / Graduate School Catalog http://grad.wisc.edu/catalog/index.htm union.wisc.edu union.wisc.edu, terraceviews.org, unionreinvestment.wisc.edu, terracepaver.org, terracestore.union.wisc.edu, uniontheater.wisc.edu, wumarketing.org urpl.wisc.edu uwclp.org uwhealth.org/cancerresearch uwpd.wisc.edu uwsc.wisc.edu vtb.bme.wisc.edu waisman.wisc.edu wcwpds.wisc.edu, and one other subdomain that I'm forgetting now. We are migrating to: / epd.wisc.edu on October 27 / up to that point we've been / epd.engr.wisc.edu / distancedegrees.engr.wisc.edu / tic.engr.wisc.edu / dmc.engr.wisc.edu / mees.engr.wisc.edu / management.engr.wisc.edu / sse.engr.wisc.edu / environment.engr.wisc.edu / metj.engr.wisc.edu / campbadger.engr.wisc.edu / and a few others that are 'disappearing' as they are no longer relevant. wec.wceruw.org westmadison.ars.wisc.edu wisc.edu, news.wisc.edu, wisconsinidea.wisc.edu, budget site, chancellor's site incl. blog, IUW, The Weekly wisc.edu/support wsum.wisc.edu / wsum.org www.agroecology.wisc.edu www.ahec.wisc.edu www.ahec.wisc.edu / www.informedcaring.org / www.healthcareers.org
Appendix 3 - Page 28 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
www.aos.wisc.edu www.bmolchem.wisc.edu www.ccas.wisc.edu / www.ccas.wisc.edu/careerexplorationcenter www.cdr.wisc.edu / www.turbo.cdr.wisc.edu www.chemedx.org / olcc.ccce.divched.org / confchem.ccce.divched.org / www.ccce.divched.org / www.jce.divched.org www.d2p.wisc.edu www.dermatology.wisc.edu / https://kb.wisc.edu/dermatology/internal/ www.education.wisc.edu / art.wisc.edu / dance.wisc.edu / ci.education.wisc.edu / psn.education.wisc.edu / kinesiology.education.wisc.edu / careercenter.education.wisc.edu / elpa.education.wisc.edu / mspe.education.wisc.edu / rpse.education.wisc.edu / merit.education.wisc.edu / website.education.wisc.edu/* / Any other *.education.wisc.edu www.engr.wisc.edu and all sub domains / graingerinstitute.engr.wisc.edu / commencement.engr.wisc.edu / perspective.engr.wisc.edu / store.engr.wisc.edu / and others www.engr.wisc.edu/cee www.finaid.wisc.edu www.fpm.wisc.edu / www.masterplan.wisc.edu / www.engageUWMadisonMasterPlan.com www.geography.wisc.edu www.jobcenter.wisc.edu www.kemp.wisc.edu www.kemp.wisc.edu www.lafollette.wisc.edu www.library.wisc.edu; gobigread.wisc.edu; www.licensing.wisc.edu www.music.wisc.edu www.nutrisci.wisc.edu www.ohr.wisc.edu/ifss www.primate.wisc.edu / ipad.primate.wisc.edu / pin.primate.wisc.edu www.primate.wisc.edu, pin.primate.wisc.edu www.quality.wisc.edu www.slh.wisc.edu www.topslab.wisc.edu, projects.511wi.gov, www.glrtoc.org, transportal.cee.wisc.edu, www.wisconsintimecoalition.org, www.itswisconsin.org, www.itewisconsin.org www.training.fpm.wisc.edu www.uhs.wisc.edu www.uwbadgers.com / buckysbuddies.com / myuwbadgers.com / uwathletics.com / and many others. www.veterans.wisc.edu www.worh.org www.wvdl.wisc.edu Yes
Q26_8_TEXT You indicated your group is considering a migration to a new web content management platform. Below is a list of web content management platforms or tools. Please, indicate any that your group is considering for this migrating.‐Other 1 and 1 My Website
Appendix 3 - Page 29 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Anything simple enough for a novice but that can still handle php/mysql integration for web app development Built with PHP Buying a complete CMS system or building one CMS CMS CourseLeaf (Leepfrog) CraftCMS Discussion has begun on moving the catalogs into a product called CourseLeaf. If and when it happens, the Undergraduate Catalog would be first. do not know Dont know don't know Don't know which one to choose. See previous comments about limitations of Drupal. We need to fx the problems we have currently, and we think these problems are caused by Drupal. Don't know. Technology dictates we will. first move is just to Drupal 7, then within a short period move to another platform ‐‐ not sure about which one I am not aware of what they are considering at this point. I don't actually know if we're considering migrating to a new platform, but that wasn't a possible answer. I don't get to decide what platform is used. Upper management will. I dont know, Dept IT will tell us I think we are really open to almost anything ‐‐ but WordPress and Drupal have been noted the most I'm not sure. It might be WiscWeb ‐‐ whatever the English department uses. The issue is that I need to be able to update our content. It's possible we'll explore other options. KB Migrating our remaining sites that are still in DNN and also upgrading current wisc web to responsive templates. n/a No distinct plans but WiscWeb is so limiting as to have us question how long we can stick with it. Probably something more like Wordpress. Probably will move content to the KB. No idea.... but have heard they're planning something for January that would mean we could update our own sites. not sure Not to the point of looking at other platforms yet, always looking for better solutions. Responsive Template Ruby on Rails ruby/jekyll undecided Unknown at this time Unknown. We are considering a PHP website that is built to display the book metadata in our database as dynamic web pages. We are leaning toward moving everything to WordPress, but haven't made a firm decision yet. We had an opportunity to use SilverStripe but that bid was turned down by our marketing folks We will be moving to CMS which maybe is WiscWeb? I have no idea. We will investigate what options are available when we redesign the web site.
Appendix 3 - Page 30 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
WP for iss.wisc.edu and iss.wisc.edu/mfis/index.html
Q34_6_TEXT What will be your priorities when selecting the next platform? ‐ Comments #1 is ease of migration and support for transition. Ability to dig in to details as an admin but very easy to edit for student assistants and staff, etc. Ability to manage a database that tracks volunteer hours. See previous comment about Drupal. Already well into process of moving over to WiscwebCMS Campus committment and support Current WordPress implementation is problematic (delegation and updating of content is an issue) so we are looking at migrating to a different WordPress site, independent of the parent organization. Ease of page editing is our primary concern ‐‐ it would be preferable to not need to use HTML Ease of use for content maintainers Ease of use. / Flexibility. / Security. Follow standards, Responsive, / Encourage Collaboration I am not involved in the update/changes to our group website, I just know it is being discussed. I have my own thoughts and ideas, however I am not the decision maker for the priorities. I think functionality and usability will be our primary factors. I think it's some sort of combination of functionality (how easy is it to use/can those with little web training figure it out without too much trouble); technical support and maintenance. My gut instance is to rate functionality as the most important priority but ???? I wish they would choose something that is more functional and easier to use than WordPress Is being driven by heads of the division in an attempt to unify departments. Little input from individual departments. iss.wisc.edu‐ because the Division is implying we have a choice to jump on the bandwagon or be left to our own devices. / mfis‐ we need something easy to use and not solely supported through the university (community org). Looking for a platform that is easier for a non‐coder/programmer to use for website updates and changes. Most important: cost, functionality and mainenance. need scheduling/booking functionality One of the department websites we serve is redesigning their site (currently in WiscWeb) in WordPress. Our biggest selection was the marketing options, everything else was secondary. Our current SiteFinity installation seems to require a large amount of maintenance, little technical support available, doesn't meet our functionality desires, and costs a yearly subscription fee. Our group has been unhappy with the lack of ease in editing/learning curve with wiscweb. Our experience with Wordpress shows us that the user learning curve is shorter adnd it is much more intuitive. Our main reason is functionality, Drupal allows content creators to have more control over the content and layout and let developers focus on maintenance and technical support. Perhaps others, I'm not involved in this decision. However, there is great dissatisfaction around the wiscweb CMS. I prefer using databases and html in my websites ‐ greater control and easier to update so all html/css pages/sites will stay while we migrate the department wiscweb site to wordpress. Please allow for individual researchers to use a template from UW for their website that can use a UW web address. scalability: can we automate as much as possible about universally applied custom branding and content creation by integrating from other data sources, while still allowing necessary business‐process differentiation between groups of users
Appendix 3 - Page 31 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Seamless integration with a massive database standardization of web sites among organization The ability to track leads and registrations through the entire process, as well as the ability to do smarter marketing related to web user behavior. The College of Engineering has already selected a new platform for us in the departments The CourseLeaf product manages academic information on campuses—degree requirements, courses, curricula, and so on. There are more technical changes I'd like to make to these sites (applications that feed to a database where supporting documents can be uploaded rather than sent to me separately... which is archaic and something I have to routinely apologize for. UMich does not have students sending transcripts and reference letters separately to program directors.) This question made me realize that I don't even know the platform that runs our current site; it is between 5 and 10 years old, looks and feels incredibly dated. We are hiring right now for someone who can recreate the external site in WordPress and move the internal stuff to Google Docs for now, while we investigate what we really want to do with the internal stuff. USABILITY. Drupal can do a lot, but it has a very steep learning curve. Moving toward wordpress because it is a more friendly user environment. USABILITY. Most faculty/staff are already at least vaguely familiar with WordPress, and its authentication via netID generally works. We are most likely migrating our 3 Drupal sites to WordPress in the next year. we cuurently have a dreamweaver/html site that is extremely flexible but requires significant technical experience in order to maintenance. Current staff in the communications department does not have this skill and they are looking for something easier to use. We need a site that is responsive, and dynamically showcases our content and what our college is about. Our current set up is so static. We need something that will allow us to: / 1) Have roles/permissions that allow us to restrict which pages editors may edit and what types of content they can create/edit/delete; limit file upload sizes and types of files that can / 2) Mimic Drupal Views functionality so we can display events and news stories in custom formats [with or without teasers, different date formats, etc.] on the site / 3) Reasonable page‐load speeds / 4) Functionality (modules/plugins) that is ideally free of charge We need something that will make database data display within dynamic web pages easy; also need pages that will work with mobile devices. We needed something we could maintain and support internally, so we could make sure it meets changing needs. we rely on open source tools We want a platform that is simple enough for faculty to easily update it themselves. we want the ability to mange how content is being published. We also want to decrease the level of website design knowledge needed to main our websites. We're looking for a user‐friendly, functional platform that we easily can expand, develop and revise.
Q25 This is the last question in this survey. Please, use this space to share any other experiences, thoughts or comments regarding websites on the UW campus.
Appendix 3 - Page 32 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
A major difficulty is the campus search engine, or lack thereof. Even when there are sites with the information someone needs, they can't find them. This is a communications nightmare and interferes with recruitment and retention, as well as increasing our time wasted on wheel‐reinvention exponentially. Also University Communications branding standards are so inflexible that if we followed them, our site would be much less effective‐‐if they actually implement the proposed new standards, this would help greatly, but I have no faith that they will. In such a diverse and decentralized environment, trying to enforce rigid standards without any assessment of needs across campus is ridiculous. They are also unaware of the differences in the needs of units that are outside of schools/colleges, which may focus primarily on internal rather than external customers‐‐they seem completely unaware of how many units (and entire divisions) are outside of colleges. Again the question about who hosts the site, local hardware or a cloud based. So many to choose from and so many different cost ranges. Again, the support is great. Although WiscWeb CMS can be a bit clunky, it works. Once you are familiar with how to update your pages and content classes, it's fairly straight forward. I would guess that new users or those that only make infrequent updates may find it more challenging. Any shared resources for Drupal migration and/or development would be helpful things like templates, experience with choosing contact forms, galleries, and other extensions would be great. Appreciate the support for WiscWeb CMS. Would be great to have more FREE classes available to academic staff working with other online and computer tools. As I mentioned before, web is hugely important, but there seem to be so few resources and very little expertise to go around. Part of this, I'm sure, rests with campus units: too many faculty and staff lack any sort of web expertise, and shy away from investing any time our unit resources into web design, development, and maintenance. / / My unit ‐ the largest academic unit on campus ‐ has a communication staff of three, with two somewhat web‐savvy staff members (myself and another staffer). Neither of us are developers, though, and while we'd be able to tweak and maintain a custom Wordpress theme, we both lack the expertise to create it from scratch, and to keep the server maintained and the Wordpress installation patched. Also, while I can design a responsive website, creating one is beyond my skill level, currently. / / We gravitate towards Wordpress, as opposed to a custom CMS, because we don't want to lock ourselves into a system that only one person our company can maintain. I think it would be better for campus in general to understand that a web redesign is not a "one and done" project ‐ but an ongoing endeavor. We know that web changes so quickly, and we'll probably be going through a major overhaul every 3‐5 years. It wouldn't be wise to lock ourselves into one inflexible system. / / I'm really hoping that campus, in general, can work towards solving this responsiveness issue. So many of our constituents ‐ especially students ‐ are accessing our content via smartphones, and our content has not kept up with this trend at all. It makes us look behind the curve, and outdated, which does not befit a research institution that prides itself on being at the forefront of knowledge. As someone who accesses various campus websites on a regular basis to help students and prospective students, I find it really frustrating that there is not more consistency about how sites are set up. For example, some units make it easy to find contact info and people and others make it difficult if not impossible. I'd hate for units to lose their individual brand but consistency about what types of info is shared and how it is shared would make the user experience much better. If those of us who work here can't find info, imagine how hard it must be for students and prospective students. As the School of Education considers moving to a new content management system, I'd love to be able to speak with someone who has thought through some of these topics and might be able to lend us a hand in making some of these tough decisions ‐‐ Todd Finkelmeyer, Communications Coordinator, School of Education (
[email protected])
Appendix 3 - Page 33 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Because WiscWeb isn't as user friendly as open‐source options such as Drupal or WordPress, I've steered many campus colleagues to both of those CMS. Campus should support Drupal and WordPress and provide some sort of entry point, whether through DoIT or University Marketing, for people who want to do a website on either platform. There should also be a central resource site that describes options for building websites on campus and getting services for building a website on campus. Campus should have few options that can provide 90% all that departments/groups/etc. need, and provide some consulting (at no cost) on information architecture, site planning, etc. In general people have too many options and it's too easy to say "Well, we could do XYZ." but there is too often no discussion of what the needs are, what the audience needs to get from the site, etc. etc. Then the student or whoever put the original site together moves on, or the funding runs out, or someone loses interest, and then the site is obsolete and unmaintained. Cathy Riley and Michael Tessmer are to be commended for their help in supporting the development of new and revised classifications sytems for the cytologic diagnoses of Cervical Cancer and Urinary Bladder Cancer. They allowed a consortium of international professional organization to assess the current state of thee art and produce two atlases that will most likely be essential texts in most hospital and clinical laboratories accross the world. I can't say enough about their help. CMS training (like most most computer training sessions I have taken) are not particularly effective for me. Instead of a 4 hour session (for introductory material) I would prefer multiple, shorter sessions. Instead of introducing all sorts of bells and whistles, stick with the most basic concepts and techniques. Build a foundation and frame out the shell. Add the porches, and exterior trim later. Four our sessions are not effective learning opportunities. DoiT is doing a great job bringing our campus into the 21century. Keep up the good work! DOIT WiscWeb CMS, Web Hosting and KB services and staff are excellent we appreciate all the services offered. Drupal is far too complex for the average user, in my opinion. Every dept need web programmers at some point in time, but usually not full time. Consider creating pools of programmers that can be utilized by all. every person on campus should have a UW Wordpress site. Everyone at DoIT was incredibly helpful in our learning curve ‐ from the very start to now. I enjoy the brown bags and all of the help that I get. I know that if I wanted to add something to our website that I've never used before, all I'd have to do is send an email and someone would actually COME to show me (that's how I learn best) if I couldn't figure it out from a KB. THANK YOU!! Extension is in a weird place w/r/t UW Campus and websites, and a lot of other things. I am working on an online course to be used for staff training ‐ Extension program staff ‐ and I would love to use Learn@UW, but I doubt I can, so I'll have to figure out what Extension has to offer and work with them (and I'd much rather work with DoIt). Because my position is funded through CALS, I can access all the great UW resources for my position but not for the work I do with the rest of Extension. First, we were early adopters of the WiscWeb CMS, and I've grown to dislike it immensely. It's clunky for users and, when my unit had a webmaster, seemed vastly out of the realm of her ability to redesign on her own. We'll be moving to a Wordpress platform in February 2016. / / Second, a big component of our website is faculty and staff profile pages—pages, particularly in the case of faculty, that allow people to list information ranging from research interests and job duties to campus affiliations, education and publications. We were forced to develop our own in‐house system to replace a prior version of an in‐house system that simply got too old to function properly. On this university campus, the university should provide a single, centralized tool (customizable) for all schools, colleges, departments and other units so that faculty and staff profiles are consistent across the university and potentially are linked to the HR system/university directory.
Appendix 3 - Page 34 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
For our group, the greatest threat/risk is accidental deletion of our site. This happened to us (not at DoIT), and it was a near‐miss disaster for a major conference. Floods and fires are always of concern, but human error is much more likely to strike from time to time. / / Reaching out to the correct site owner before removing a site is extremely important. If you call the wrong person and ask "are you using this site?" you can expect the answer to be "no" every time. Even if this person is a Director and your IT group feels they got the green light, it is not always correct. / / I'm happy to say we've never had anything like this happen to use at DoIT. So far we've had no issues.
For quite a while there was a slow movement towards standardization and using campus templates. Now there seems to be a very rapid fleeing away from campus templates to unique designs. The trend seems to be towards responsive design, with a lean towards mobile. / / The campus's level leadership related to responsive design and CMS has been very frustrating. I would expect the campus to be out front of this working with campus groups to determine a direction. But, instead campus has been nearly silent, while all the activity seems to be at the unit level. It feels like it is returning a bit to the wild west. I love the innovation side, but I fear will go the direction of becoming too scattered. / / The lack of info coming from campus and the lack of a long term vision (in the web sense) It has caused us to delay in order to figure out where campus is going. / / It seems pretty clear that there are a lot of fundamental problems with WiscWeb CMS, and thus that it is only a matter of time before it is abandoned as a campus solution. It seems that those who have the knowledge or resources have moved to Wordpress in large numbers. Yet the campus continues to promote primarily WiscWeb CMS while saying very little about the future of Wordpress. It would be very frustrating to move to WiscWeb CMS and then have to make another migration to WordPress or other CMS, so we have waited to see how things would pan out. / / I noticed recently that the web hosting service now has a WordPress installer in its hosting package. It would really be helpful for campus to come out with some stance on WordPress. it seems likt there is enough usage on campus that Wordpress should be identified as a formal service and the campus should be ramping up in terms of supporting it and providing a scalable platform so that we don't have tons of groups all over campus spending time mainting their own installs of Wordpress. / / It would also be very helpful for campus to come out with the plans and furture of WiscWeb CMS. If it is not long‐term, then it doesn't seem like new groups should continue to adopt it. / / What are the plans for the campus home page? / / Thanks for inviting this feedback. Hopefully it will result in some good conversation and some robust campus solutions that improve our web presence and services to students, while improving time and cost efficiency! For the most part WordPress has worked for us. It has its quirks but we were able to build our own pages for the site by ourselves and maintenance wasn't a problem until recently and that's because Carrington Build has issues. future technical support is of great concern Get rid of Drupal and get something that is more intuitive or easy to use. Get the UW Wordpress theme inline with the Bootstrap themes, more responsive, etc. Getting tenured faculty on board was the biggest challenge. Too many unwilling to change. Some were absolutely great ‐ jumped in with both feet. High‐degree of team "buy‐in." Too many others did not take ownership. Typical ivory tower stuff. Some felt it was beneath them to be responsible for web content, look, messaging.... too "corporate." Totally miss the boat, particularly in tough budget environment. Our "bread & butter" = students, students, students. they grew up in and live in a different ‐ digital, all‐things‐online ‐ world! Too many of our six‐figure cave‐people won't accept that, nor will they take ownership of it. Shouldn't surprise me. They seem not to care about students anyway. / / And, not all! We have some great tenured faculty leaders who "get it." Just not enough of them to make life better for all!
Appendix 3 - Page 35 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Hardest part is keeping up with faculty expectations of what they see elsewhere. Some sites are very dynamic and have a lot of "splash". I get "do that for us" alot. They do not realize there are full time staff and dedicated experts creating that, which we do not have. Makes it very difficult to do what I need to do and people get upset if I say I can't immediately do what they want. I am an editor, responsible for keeping faculty pages, our home page, events, and directory information current and up‐to‐date. Being a non‐IT person, it would be extremely helpful if there was an introductory/basic Drupal course available on campus. I am happy using wordpress for our web site I am never sure who to call when I run into issues as things keep changing. I am not sure about changing the platform when we got a communcation specialist she worked and updated pages on the web site not sure if she changed platforms but she added intranet to it. I am the manager of a research lab, and I would find it helpful if there were a UW website where lab members across campus could post protocols, seek input on experiment problems, opinions on equipment and supplies, etc. I appreciate the web/hosting team's pro‐active outreach and support. I believe we are going through a study with DoIt to get our websites consistent through all our divisions and have them be more user friendly. I don't know if my group is considering migration, as I do not have a say in that. / I enjoy being able to customize our content to what we think is helpful/necessary, but I am a bit frustrated by the limited control I have over it (ie no say in platform decisions, limited training/warning on changes, can't change design but can change (some) content, etc.) / / Overall, I am OK with the experiences I have had, but I do see opportunities for making an even better site (posting customized video training, online space reservation, online access to checking greenhouse settings, etc.) if more technologies were adopted and more training was available. And if all stakeholders would find it useful/allowable. I don't know what a different platform is. I'm pretty illiterate. We wanted a website, I asked around and started one. I find as with a lot of stuff on campus, it is kind of a "do‐it‐yourself" environment. I don't feel like I have any of the "real" technical expertise that is required, so we are probably doing the bare minimum. Ultimately, I'm not sure that is a good thing for us, but there is only so much time and I simply don't have the resources. Until it is a priority, it just isn't a priority. I have had great experiences with WiscWebCMS and the DoIT staff offering trainings and customizations. I do not have a computer/tech educational background and I have found it easy to use. HTML is NOT easy to use as a layman. I have recently used Mac Mail Merge and to to use FireFox to send emails to a list of recipients. DoIT has been very helpful in anwswering my questions, but the online instructions could have been more detailed and tested. I just wish I had more time to work on the websites I work with! There are so many features in Drupal that I can see ways that would enhance our site to meet the needs of our various user groups, I just don't have enough time in my day to do more than maintain the sites. I know my co‐worker has been extremely frustrated with the CMS we currently use. I manage a wordpress site. Although I diligently look up the knowledge base articles and try to solve problems on my own, it would be much more efficient for me to list my issues and schedule a one‐on‐one in person meeting with a help desk person to fix a bunch of things all at once and show me how. One hour every 6 months for example. I realize that various website quality is determined by many factors. In the end, I hold the website owner and their boss's, responsible. Overall, I think ‐you‐ all do great work. Considering the varied customers, end users and non‐tech people who you work with....you get A+. Good luck with your endeavors!
Appendix 3 - Page 36 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
I think having a cohesive web presence is important because although departments/office function independently from one another the general public sees the university as one entity. It can be used to help reduce confusion and promote consistency. I took the training class from Matt the other day, it was excellent. I was not the right person to take this survey I was promised a lot of help when migrating our website, I had one visit from Cathy Riley and one from Matt Goins. Matt provided a lot of useful information and I was promised follow up by Cathy, but did not receive a response or any further help. I ended up having to do the whole migration myself and publishing anyway, as we had a deadline. I went to the CMS training class and didn't come out with much. It's not intuitive in the least, and single changes can be distributed throughout the entire web page creating a ton of chaos. I dislike CMS very much. Not because it's new, but whoever is writing the software has abandoned the structure of how a program or web sites is used. The Kaltura interface looks like it's using similar human interface logic. I will plan to move my web content to the new responsive design template soon. Right now, it is giving me a time to ponder. In my opinion, websites reflect how open/collaborative or how closed/siloed the owners' units are. When trust isn't there among colleagues, we tend to have seperate websites in order to exercise our authonomy. When our customers must go through several different websites to gain required information, we are not serving our customers well. That's how we show up in our markets. That's how public sees us. Although it is tempting to keep 'my own' website with much autonomy & choice, I must put harmony & alignment among my colleagues as a priority in order to create a one‐stop website, such as an intranet (just like UW Housing/no login, just hidden). Lots of office politics will surface during web construction. However, if we design it well, it is a powerful tool to express and/or celebrate our unique position in the market and the world. I wish that I could somehow use the lab website to link to a cloud storage server that we maintain locally. I wish there was better coordination across the campus for WordPress users ‐‐ so many sites are using that platform, but there is no central core to support these activities. / I have evaluated WiscWeb several times for different projects since the university signed a contract with them, and that platform always fell short of WordPress. I would like to see the university redirect those WiscWeb resources toward what web teams really use and need. I would be really grateful if there were some basic web templates that any UW user could employ for their university‐related website. My lab would really benefit from this as would our department. I would like to see a centrally supported CMS ‐ ideally WordPress. Right now we are using a departmental instance, but a DoIT supported instance would ‐ I think ‐ be popular and increase adoption and user community on campus. I would like to see more interactive features on the user end, a chat feature, and a better web form. I would LOVE to see a campus‐wide, supported installation of WordPress multi‐site. I use, and love, WordPress as a CMS for several projects, and see real value in adopting it as a widely used, campus supported tool that has some degree of central administration (even if only at the college/school level). Would work wonders for all kinds of web projects (from both the design, development, and production side, as well as maintenance/security). I've got my fingers crossed ... If a decision is made to select a CMS‐of‐record for UW‐Madison, ALL offices, including DoIT, uMark and uComm should abide by the decision. A la carte use of multiple solutions as we have now just means we're duplicating and wasting resources by not being able to support and share with each other. In a perfect world, it would be nice if there were strong support for website development and programming on campus. We've had a very rocky experience getting started.
Appendix 3 - Page 37 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
In general I like the common look and feel of UW websites that use the template. WiscWeb CMS has most of the functionality we need. But some of the few things that are difficult to do are immensely frustrating and take many more steps than it seems like they should. In general, I think having UW Communications create the website and then have DOIT take over was a mistake. We would probably go outside the UW to ever create another website as our tech team is not able to keep up with the demands of our site and I don't think it is that large of an item compare to other online ordering websites on campus. It is not uncommon for us to have faculty come to us looking to build a WordPress site, for which they have to pay for development, even though there is a completely subsidized offering in WiscWeb CMS. Usability of the administration interface is one big reason they give us. They have also often "heard" that they don't want to use it from colleagues. / / In this tight budget environment, this speaks volumes about the needs on campus ‐ when people are willing to pay for a different approach to something they can get for free. / / Lastly, we have been able to execute a great deal of this development work using student talent overseen by senior developers. This is a model that could be further scaled, providing a more affordable price point for customers, as well as valuable real world experience for our students. It would be extremely helpful to have affordable (comparable to the shared hosting in the public sector) WordPress hosting on campus. That said, we would want to be able to use our own templates and plugins (which is realize is a security issue) and customize our own sites. It would be fantastic to have a single recommended campus‐level CMS platform with internal support. For example, if campus were to recommend WordPress, a campus‐level set of templates, approved plug‐ins, custom plug‐ins/integrations (e.g. netID sign‐on) would be extremely helpful. It would be great if we could share hosting, security, module support, etc. for WP. Eliminate duplicate efforts. It would be nice (and, I hope economical for all parties) if DoIT provided website design support, pros and cons of different platforms, and basic instruction on content management It would be nice if everyone used the same thing It would be nice if we had a support avenue for Sharepoint and Wordpress via DOIT. This would include but is not limited to design, and break fix support. It would help to have a more standard approach to developing websites on campus, with the needed technical support willing to help departments that do not have technical support on staff to help in the process. It's been quite difficult to find resources for building sites on campus‐‐glad you are looking into our experiences and hope that some plans to centralize websites and offer more resources to uw programs is in the works. Also, it seems that some departments don't realize that they need to put real money and resources towards having web presence. Also, on a side note, recently the department of population health sciences needed to upgrade the website and ended up going w/an outside consultant who charged up the wazoo and down the wazoo and back up the wazoo again. It's sad that we don't have better offerings on campus. We have entered an era of modernity where an institution like UW can't afford to continue such mediocrity. It's essential that people in the departments have an easy way to update their material. When I work on a given catalog, dozens of people submit material and edit within WiscWeb. It's important that enough "customer assistance" be readily available to help people right away when they get stuck on something, and that a product isn't rolled out before its time. In my case, my position is dedicated to the two catalogs.
Appendix 3 - Page 38 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
It's great to see more campus sites going to responsive designs. There has been a recent shift away from the old campus template towards more decentralized design and more variety. It's led to some great creativity and fresh design, although I wonder if some new centralized standards might be needed to make a good user experience across departments. WiscWeb has mostly worked pretty well for us, though it has some room for improvement to be more user‐friendly and more modern. I've been happy with the experience so far. You guys do all the patches and updates and provide us as much server space as we need (so far as I know). the only problem is that sometimes our test space (wwwtest) is really slow and unresponsive. That is exceedingly frustrating, but not a deal breaker. I've been very happy with wiscweb so far, and DoIt's tech support is always fantastic. We talked about Wiscweb at our LSDAN meeting, but I think a lot of depts still don't know its a great (free) option on campus Keep in mind that we need to compete with the price points available off campus for well‐supported commercial web hosting. If we can't compete, then contract this entire function out to a commercial hosting provider. LAMP is used primarily. Looking forward to moving from the standard web template to the responsive template. Lots of frustration with wisc web. Sizing of text, making text and paragraphs match, etc is irritating! many of the new versions of campus websites look primarily "functional" and very text heavy. they're not very contemporary looking Maybe this already exisits, but a couple variations of a responsive UW Wordpress theme would be awesome. More support in WordPress is needed. More support would be helpful. Most areas' CMS needs are not that complicated and they typically just want to use whatever official UW theme is available. WordPress is familiar and intuitive enough to let people just get up and going with their site. If the campus is looking to go in a new direction in CMS packages, WordPress has to be the favorite. My department, Biomolecular Chemistry migrated and created a new website with WiscWeb CMS. This was our first experience with a CMS system, and the initial learning curve was steep. We were very pleased with how our new website turned out. The WiscWeb developers were very helpful and responsive to our requests for designing our new web page templates. WiscWeb technical support was also very good, with issues/problems/questions being resolved in a timely manner and always to our satisfaction. I can't recommend WiscWeb highly enough. ‐Joe Oliva My experiences with WiscWeb have been uniformly awful. I chair a shared governance committee, but I ask the Secretary of the Academic Staff's office to post documents for me rather than deal with WiscWeb, embarrassing as that is for someone who spends a great deal of time developing web content. Official campus support for WordPress would be timely and align with a web platform already in substantial use across campus. It would also be preferable to subsidize WordPress (already in use) over OpenText in annual bill. On the last page, the last question asked if we were planning on changing. I don't know if we are or not, and I'm not sure I would be part of that conversation. I've recommended that our group look at the WordPress sites on campus as it seems like many of the other VCRGE sites are on WordPress and I think there's something to be said for a consistent theme across pages. But I don't think that kind of change is on anyone's radar at this point in time. One major advantage of CMS is that it allows you to make a change on one part of the website and that same change is also made on another part of the website (for example, adding references). One major disadvantage of CMS is that it is relatively complicated; it is NOT characterized by user‐friendliness.
Appendix 3 - Page 39 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Our campus is so decentralized and every unit is doing its own thing ... but it seems like it might be more cost effective for everyone if there was an enterprise‐level option available. WiscWeb is not a great option. Our group is committed to WordPress for the forseeable future, and have been migrating our sites off of other platforms including WiscWebCMS, and ASP.Net. We still have a couple of ASP.Net sites and a classic ASP site which I sincerely hope will also move to WordPress. Our problems are less technical and more human. In my opinion every department needs to have multiple skilled at some elements of web creation (html, css, js, native mobile, photo editing, video editing). This should be standard parts of hiring, training, and promotion paths within all classified and academic titles that are within the departments. If I had two or three competent collaborators, we could implement any CMS; but since I have to assume that no one has technical abilities beyond editing Word documents, I have to make a lot of difficult decisions around implementing a CMS. Please don't try to solve a human problem with a technical "solution." Our website is small and is hard to do a good job maintaining along with all of our other job duties. We need to develop a better system to keep things updated and current. Our website overhaul group investigated content management options and decided that WiscWeb CMS would be our best option, in part because we saw other campus sites that we like that are using WW and in part because DoIT provides excellent training and ongoing assistance with WiscWeb. Overall, CMS works well for my group's website. Overall, I think the systems in place serve a ton of differing needs, and does so with high quality. I really appreciate that about our approach. Please consider asking UW Communications to update their (dated, non‐responsive) campus WordPress theme. A lot of departments (us included) are throwing lots of money at rolling our own; I suspect many of us would be just as happy to adopt a good one from campus. Please contact our departmental IT director, Dan Bradely for any additional inputs. poor support ‐ need more really impressed with WiscWeb CMS. I think its one of the most innovative tools available on campus. Thank you! Really like to use enterprise systems to save everyone money! It would be great to use a wordpress‐like system that is more fully integrated with communication tools! Really wish we still had a dedicated staff person to help with website updates, upgrades, maintenance, etc... refer to our UHS IT and/or communications dept for more specific web info Ryan at the WWCMS help desk is the best. Smart, savvy, helpful, punctual. See comments to previous question. see previous comment see prior comment. Using wordpress will allow us more control over our websites and thus less dependent on tech support. Shouldn't this process be going through the EITDM? This is *exactly* what the EITDM is supposed to do? / / Please also separate out website design/implementation from the software being used. This is a non‐technical limiting factor that causes problems for people. While a group can implement WiscWeb because the WiscWeb group does all the work, that doesn't mean that they wouldn't be better served with something like WordPress Some formatting is difficult with WiscWeb, e.g., fonts, styles. survey not well designed.
Appendix 3 - Page 40 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
Thank you for providing WiscWebCMS. It is really helpful to our small department to have the institutional support from campus, including technical assistance, training, and DoIT staff hours to assist with migration at no charge back. The campus has an approach to the web that offers all entities a great deal of freedom to choose, which is excellent. However, the population of actual web developers and designers on campus is very small so how each department, organization, etc. get online isn't an easily visible path. As the CMS landscape is sure to change again in the future it is important that the campus remains agile and open to new platforms. The CMS system is cumbersome and difficult to use. I often write directly in html in order to fix formatting. The system is in need of simplification especially in opening multiple red dots to get to an editable section, multi‐step asset uploading, and suggestions to publish all following and all related that make little sense to the average user. The COE vhost platform is nice because edits can be made either from an editor (we use Dreamweaver) or using ssh and vi. The demand on our local development staff has made it hard to get application development for the main website prioritized. Increasingly, we are having to look towards 3 party applications as WP core is fairly limited. The 3rd party apps have been a bit of a disappointment and not a great match for our needs alot of the times. Also user permissions have been a pain. Personally, I would prefer to see us in a system with a more robust core so we don't have to rely on plugins as much. The IT support has been lacking. We as a group were introduced to Wordpress at our annual meeting but instead of each having a laptop to go through the steps individually, we were shown by a savvy technician what to do. Not much of this was retained when we had to managed the websites on our own and this IT person did not respond in timely fashion, if at all, unless repeatedly asked. The key features important to me/my group are (1) the ability to easily track and review changes [provided by git/github in our case] and (2) the ability to migrate the data when/if the time comes. The number one concern I have is the lack of financial support to individual units for web design, redesign, management, hardware, etc. Many units have not historically budgeted for these kinds of things (and these are typically units that also lack flexible gift funds) and in the past decade the impact of budget cuts to units has made it wholly impractical to allocate 101 funds to handle web site needs. For many units, web site maintenance is not part of the job description for any staff person, or forms such a small percentage of the job description to make it very difficult to even keep a web site up‐to‐date let alone do the periodic redesigns that are really necessary every few years. The programming skills necessary to manage a web site vary considerably among the different platforms and it has seemed like the University has encouraged reliance on platforms that are not the most user‐ friendly. It might be interesting to consider creating a block‐grant program to which units could apply to get $5,000‐$10,000 to cover the costs of web site redesign and on‐site training of a couple of staff people who would do the maintenance; and it would be great if units could reapply for funds every 3‐5 years to ensure that individual units are using up‐to‐date technology and have web sites that have a contemporary look. The online support request form never works, which can be frustrating. I usually end up having to email someone, but I do get help pretty quickly. There are some small things on our site that still fail to operate properly, particularly when it comes to signing into WordPress, etc. The problematic part of our website is not managed/hosted on campus The server still appears to be using Redhat 5. This operating system has known vulnerabilities and can not support stronger encryption ciphers and protocols. The weak ciphers have known exploits. These servers and their applications should be migrated to supported versions of the OS as a top priority.
Appendix 3 - Page 41 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
The Wisconsin Union, due to being told by UW Legal Ben Griffiths, is suggesting student groups potentially move away from using Google Sites, Facebook, WordPress and other non‐UW‐Madison‐created software. Please correct this perception of what UW‐Madison DoIT requires for campus groups (by contacting Union Assistant Director Jane Oberdorf ). Thank you. The WiscWeb CMS was so difficult and non‐intuitive to use. Not user friendly at all. And while the staff that maintained the CMS was very helpful and knowledgable, the program itself was outdated and teidious. The WiscWeb training was successful as a technical training, but too disconnected from organizational concerns and too long. Would be better to train people on web design processes. There is surprisingly little guidance, support, or funding for individual departmental web sites across the University. In many ways it's like the Wild West with support options, security, and experience being widely variable depending on what a group looks at or who they ask. Consolidated resources for this type of undertaking would be a boon to many of the smaller departments, and we are pleased that CALS has noticed this need and is attempting to fill it. There needs to be an easy to use WYSIWIG editor for faculty so that they and their students can create and maintain lab websites without having to expend a lot of energy trying to figure out the technical details...and so that it doesn't look like crap. Very happy with our WordPress sites. Could use a little more help keeping up on maintenance issues that pop up, but realize we are sharing tech people/resources with lots of other groups. Very happy with the functionality and support through WiscWeb CMS Very satistified with DoIT web hosting service. We are interested in having a campus supported and maintained Wordpress infrastructure. We would like campus to offer this as a service. We decided to use WordPress because the UW CMS seemed too cumbersome and complicated. We have always admired the CALS site, they did an outstanding job. I would like to see the campus home page more clearly frame the pillars (tell a story) of our purpose (grad, undergrad, research, outreach) and weave in alumni more intentionally. / / Thanks for asking for our feedback and ideas, glad to be part of the dialogue. We just migrated from HTML/Dreamweaver to Drupal the first week of August. Could not be happier with Learning Support Services and specifically Ryan Engel's support building our new website, and Drupal is a total dream compared to updating through Dreamweaver. I'd taken two classes in college on Dreamweaver and I still struggled with it, so imagine staff getting hired in my position (graduate coordinator) with NO experience! Moving to Drupal was strategic for the long‐term staffing of the Department as well as just being a relief for me. We pretty much designed and maintain our website by ourselves. We had someone design it for us in such a way that we could make changes directly to html files, which we have been doing for years. It is easy and we keep the site updated continuously. LONG ago we used dreamweaver to update website files and found that over time the html code was getting corrupted. Switching to direct editing of files without an intermediary platform has worked well for us. I'm not sure I'd want to change to something like WordPress. I've used that a tiny bit for a project outside of UW and didn't care for it, too restrictive. / / At the same time, I'm not at all savvy about what can be done to create great websites. I will always need someone with that expertise to create the design/shell, and teach me out to update content. So if there is a better way than what we are doing, I'd consider it. Our website will probably need to be revamped sometime in the future, but for now we think it's working fine for us. We really like the new design of our new website done by Cathy Riley a few years ago. The Website itself is wonderful...it's just a pain to work with...so much so that I can't even begin to teach others in my office because i just get the blank stare...so I just make all the changes to the website myself.
Appendix 3 - Page 42 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
We threw in with WiscWeb because it seemed to have the full campus backing and the UW Templates, but it's really not been a pleasant experience. Getting text to display correctly has been one of the most frustrating experiences I've had since arranging tables in Word 98. The CMS support team is sometimes great, sometimes they're just not there. / / Overall I've been much happier with CALs Wordpress in terms of functionality and ease of use but have had similar issues with support. We use Sitefinity primarily because it is trivially easy to add custom ASP.Net code to pages. DoIT manages some Sitefinity sites. The School of Education holds the site license for wisc.edu. We would consider another solution if it was as easy to add ASP.Net user controls. We work very hard to keep our website current, updated, and fresh. However, many units on campus do not do so. This is very frustrating. For example, websites often do not update names of new chairs and directors or staff people. Many departmental websites do not list the director of chair at all. Since web sites serve function as main directory, this is very frustrating. / I also do not like the design for the new MyUW‐‐those boxes. When I first logged on, Financial Services wasn't even listed, and I had to call DoIt to discover that I had to ADD this box. Why boxes at all??? I think a regular menu is much easier to use. web content management does two things well: 1) it creates an environment where non‐technical users can manage web site content and 2) it allows for the creation of reusable, shareable content. I think WiscWeb and others have made some progress on the first. I see little evidence of the latter. That is unfortunate because I think much of the power of web cms is in sharing content. Websites are too often out of date and cumbersome. Too generic. The branding for the university is great, but the identity of an individual unit such as a department is easily lost because of the desire for a standard framework. We've appreciated the css that's come through University Communications for all the years we've used them, but our marketing people wanted responsive design and easy to use (for them). We're in complete agreement that this was a good move. We've appreciated using the UW template as a starting place for the website, and I'll be curious to see what the new UW‐Madison version looks like after you launch in December. What the standards (design and tech) are for UW websites is a very confusing topic for me. What are my boundaries? What am I allowed to do? Because I inherited my sites with my job, they're incredibly dysfunctional and old. When picking a new cms for campus I think Doit will get the most buy‐in (willingness to adopt) and positive feedback on a tool that feels contemporary, simple and intuitive. Frequent updated interfaces that keep up with content trends, various media and social media are a bonus. Ability to make your own simple forms, another bonus. Ability to add your own net id users, also a bonus. Wiscweb felt like something from the 2000s that was never really updated. It was cumbersome for the user and slow in speed. There were too many steps to accomplish simple tasks. When we met with the wiscweb team, we were advised against converting to a CMS because of the extensive integration of php/mysql in our current site. When we were upgrading our website, I appreciated that resources that were available through UW Marketing for website templates and other design information. While Wordpress is fairly easy for content producers to use, its full functionality and design requires considerable support on the backend. WiscWeb (RedDot) was a disappointment. All of campus seems to be migrating to WP now, including those of us who made the move to Drupal rather than RedDot. But, at the time, WP wasn't able to do what it can now.
Appendix 3 - Page 43 of 44
Appendix 3 - CMS Assessment Committee - Survey Results - Comments Only
WiscWeb CMS has really proven to be an amazing resource, especially for small offices. We don't have an IT person so having any student or staff member with access being able to use this system and keep our website up‐ to‐date has really changed our web presence. We are so grateful that we found out about WiscWeb CMS! WiscWeb CMS is kind of clunky and not very intuitive. I find myself entering my own CSS because the defaults are not to my liking. Wordpress is the most versatile of the products I've used. WiscWeb is nice but the KB site is nicer from a tools perspective. In other words, putting a WYSIWYG tools interface into WiscWeb. WiscWeb is very user friendly. With the budget cuts, there's clearly an incentive to find solutions that are inexpensive ‐ and for units around campus to share information/experiences with others. Our group has been exploring WordPress, mainly because it seems to be the CMS that campus is pomoting ‐ and yet it seems that many of the plugins involve paying a one‐ time or annual fee. (Our current site is running on Drupal 7, for which all modules have been free.) If WordPress ends up being the official campus CMS, it would be great if we could access the plugins at a discount or for free. Without our ability to engage DoIT AT for assistance with developing our sites, they would likely not be remotely as robust (or as professional) as they are. Based on my experience developing these two sites over the last two years, having professional support and assistance with the creation and maintenance of campus/enterprise websites is critical to their success in meeting their purpose and unit mission. I've been fortunate that my unit has been able to secure resources to do this. I know that many units do not, which has implications for the quality and effectiveness of campus web resources on a broader scale. WordPress seems to be a good way to go, and it seems that overall more people are moving to it. WiscWeb was very particular, proprietary, and difficult to get user access to relative to WordPress. No CMS is perfect. And there is a pipe‐dream in CMS that it will make everyone update content all the time. That does not happen. Also, any CMS inherently limits choices to make it usable to nontechnical people, who then might not appreciate their choices being limited. Attaching to a widely‐used CMS like WordPress makes it easy to use JQuery or borrow from other people with the same or similar design needs. I think piggy‐backing on that is a good model for campus. Having some base templates that satisfy the desire of UW‐Communications for consistency is a win‐win for everyone I think (when provided by UW‐Communications). Working within the College of Engineering, we have access to their virtual host (vhost) services, which have been very easy to use, with good functionality, performance, and support. We haven't used other Campus resources because there just hasn't been a need yet, or we host sites elsewhere (e.g., Rackspace), but we're curious to learn more about what's available within UW. Would be nice to have a much more flexible, free option to use on campus that si more user friendly than OpenText. Would prefer to see the campus support WordPress or Drupal over OpenText. Would love to have more support with php development needs Would love to see doit offer a hosted Wordpress solution that is a reasonable cost YAY CAE! You had asked me to compare several CMS's, I hope this information helps, but I think the experience one has with a CMS is mostly dependent on how the CMS is used. For example, as a wordpress Developer, the Core is very stable and secure, but the manager of the site could create many problems in using a poor quality theme or plugin. This is not an inherent disadvantage, this flexibility is what clients want, and flexibility is needed for the diverse needs each university organization. In contrast, WiscWeb cannot match the flexibility offered by wordpress's plugins. Furthermore, it is easier to find coders skilled in WordPress, compared to developers familiar with WisWeb CMS. Drupal, joomla, sharepoint, I can't really comment on those.
Appendix 3 - Page 44 of 44
CMS Assessment Committee – Phase I Report Appendix 4 Acquia Report
Printed 11/17/2015
id subdomain root blog.icecube.wisc.edu blog.icecube wisc fruit.wisc.edu fruit wisc apps.vetmed.wisc.edu apps.vetmed wisc tc.engr.wisc.edu tc.engr wisc snapplus.wisc.edu snapplus wisc peersinschools.education.wisc.edu peersinschools.education wisc retailingexcellence.wisc.edu retailingexcellence wisc ccdtest.journalism.wisc.edu ccdtest.journalism wisc herringalab.psychiatry.wisc.edu herringalab.psychiatry wisc newbadgerpartnership.wisc.edu newbadgerpartnership wisc m.library.wisc.edu m.library wisc uwex-tv.cals.wisc.edu uwex-tv.cals wisc imdc.education.wisc.edu imdc.education wisc technology.genetics.wisc.edu technology.genetics wisc multiphaseflow.erc.wisc.edu multiphaseflow.erc wisc glasslab.art.wisc.edu glasslab.art wisc cue.morgridge.wisc.edu cue.morgridge wisc mckinley.aos.wisc.edu mckinley.aos wisc ewb.slc.engr.wisc.edu ewb.slc.engr wisc wwwtest.news.continuingstudies.wisc.edu wwwtest.news.continuingstudies wisc theweekly.wisc.edu theweekly wisc edinnovation.wisc.edu edinnovation wisc agronomy.wisc.edu agronomy wisc dcsmithgreenhouse.cals.wisc.edu dcsmithgreenhouse.cals wisc arlington.ars.wisc.edu arlington.ars wisc peninsular.ars.wisc.edu peninsular.ars wisc hancock.ars.wisc.edu hancock.ars wisc wisconsinidea.wisc.edu wisconsinidea wisc grants.library.wisc.edu grants.library wisc nutrisci.wisc.edu nutrisci wisc news.uhs.wisc.edu news.uhs wisc matinformatics.engr.wisc.edu matinformatics.engr wisc slh.wisc.edu slh wisc centerforglobalhealth.wisc.edu centerforglobalhealth wisc speakers.wisc.edu speakers wisc uclub.wisc.edu uclub wisc internships.international.wisc.edu internships.international wisc wwwtest.365transition.wisc.edu wwwtest.365transition wisc devwendt.engr.wisc.edu devwendt.engr wisc unionreinvestment.wisc.edu unionreinvestment wisc sciencehall.wisc.edu sciencehall wisc russell.wisc.edu russell wisc sal-cnc.me.wisc.edu sal-cnc.me wisc lifelonglearning.wisc.edu lifelonglearning wisc center4design.wisc.edu center4design wisc cclub.slc.engr.wisc.edu cclub.slc.engr wisc materialculture.wisc.edu materialculture wisc africa.wisc.edu africa wisc hanson.limnology.wisc.edu hanson.limnology wisc preview.profs.wisc.edu preview.profs wisc babcock.wisc.edu babcock wisc gle.wisc.edu gle wisc moodle.wisc.edu moodle wisc wioc.wisc.edu wioc wisc babcockhalldairystore.wisc.edu babcockhalldairystore wisc dsc.wisc.edu dsc wisc soils.wisc.edu soils wisc diversity.wisc.edu diversity wisc neuro.engr.wisc.edu neuro.engr wisc aarc.chess.wisc.edu aarc.chess wisc datacenterservices.wisc.edu datacenterservices wisc parents.wisc.edu parents wisc ccr.commarts.wisc.edu ccr.commarts wisc bio.wisc.edu bio wisc search.proquest.com.ezproxy.library.wisc.edu search.proquest.com.ezproxy.library wisc gshe.global.wisc.edu gshe.global wisc intlstudies.wisc.edu intlstudies wisc metc.wisc.edu metc wisc gobigread.cias.wisc.edu gobigread.cias wisc itc.wisc.edu itc wisc marshfield.ars.wisc.edu marshfield.ars wisc illumination.library.wisc.edu illumination.library wisc awards.advising.wisc.edu awards.advising wisc steenbock.library.wisc.edu steenbock.library wisc turf.wisc.edu turf wisc babcockhalldairyplant.wisc.edu babcockhalldairyplant wisc greenhouses.ars.wisc.edu greenhouses.ars wisc uncommonfruit.cias.wisc.edu uncommonfruit.cias wisc geography.library.wisc.edu geography.library wisc www-old.cae.wisc.edu www-old.cae wisc gargoyle.law.wisc.edu gargoyle.law wisc meatlab.ansci.wisc.edu meatlab.ansci wisc uwveterinarycare.wisc.edu uwveterinarycare wisc report.ls.wisc.edu report.ls wisc hrdesign.wisc.edu hrdesign wisc madisoninitiative.wisc.edu madisoninitiative wisc wendt.engr.wisc.edu wendt.engr wisc southasia.wisc.edu southasia wisc teachingacademy.wisc.edu teachingacademy wisc milkquality.wisc.edu milkquality wisc sciencedenial.wisc.edu sciencedenial wisc dtlconference.wisc.edu dtlconference wisc lsc.wisc.edu lsc wisc wp.aae.wisc.edu wp.aae wisc www-db.cs.wisc.edu www-db.cs wisc driftless.wisc.edu driftless wisc acstaff.wisc.edu acstaff wisc agrability.bse.wisc.edu agrability.bse wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress
Appendix 4 - Page 1 of 19 apache
mobile|php_5.3|platform_php
mobile|shoppingcart mobile|php_5.3|platform_php php_5.5|platform_dotnet|platform_php php_5.4|platform_php
mobile|php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php mobile|social_media_like mobile|php_5.3|platform_php|social_embed
Media Temsocial_embed|social_media_like
apache
iis
apache
apache apache apache apache apache apache apache
apache apache apache apache apache apache nginx apache apache apache apache
apache content_embed|mobile mobile|php_5.3|platform_php apache mobile|php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php social_embed mobile mobile|php_5.3|platform_php mobile html5|mobile|php_5.4|platform_php|social_embed|social_ content_embed|php_5.4|platform_php|ipv6
mobile|php_5.4|platform_php|ipv6 mobile mobile|social_embed mobile|php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 mobile social_media_like mobile|php_5.4|platform_php|ipv6 mobile mobile|php_5.4|platform_php
mobile|php_5.4|platform_php
mobile|php_5.3|platform_php Bluehost.comobile mobile|social_embed mobile|varnish php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php Dreamhost mobile|varnish mobile|php_5.4|platform_php|ipv6 mobile|php_5.5|platform_php mobile|php_5.3|platform_php
Dreamhost Media Tem
websrv apache apache apache apache apache apache apache apache apache apache apache apache apache apache apache apache
mobile|php_5.5|platform_php mobile|platform_dotnet platform_php mobile|varnish content_embed|php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 mobile mobile|social_embed mobile|php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 mobile|social_embed php_5.3|platform_php mobile mobile|php_5.3|platform_php mobile|php_5.3|platform_php|social_embed|social_media mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php php_5.3|platform_php mobile|varnish mobile|php_5.3|platform_php|social_embed mobile|php_5.3|platform_php html5|mobile|php_5.4|platform_php|social_embed|social_ mobile|php_5.4|platform_php mobile|php_5.5|platform_php mobile|php_5.3|platform_php
platform_php platform_php mobile
features html5 platform_php
mobile|platform_php mobile|platform_php mobile|platform_php mobile platform_php php_5.4|platform_php WebsiteWehtml5|mobile Dreamhost
cms_veprovider
title
redirect
dns_provid ip 128.104.255.25 wisc.edu 144.92.93.172 wisc.edu 128.104.212.115 1985-09-30 00:00:00 -0400 wisc.edu 144.92.225.247 wisc.edu 144.92.93.172 website.education.wisc.edu wisc.edu 144.92.146.107 sohe.wisc.edu wisc.edu 128.104.80.231 journalism.wisc.edu wisc.edu 144.92.22.140 wisc.edu 144.92.177.178 1985-09-30 00:00:00 -0400 budget.wisc.edu wisc.edu 144.92.9.200 1985-09-30 00:00:00 -0400 www.library.wisc.edu wisc.edu 128.104.46.191 wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 merit.education.wisc.edu wisc.edu 144.92.93.172 intranet.genetics.wisc.edu wisc.edu 144.92.93.172 wisc.edu 128.104.201.127 wisc.edu 144.92.146.16 wisc.edu 144.92.146.16 wisc.edu 144.92.131.146 wisc.edu 128.104.201.107 news.continuingstudies.wisc.ed wisc.edu 128.104.80.125 wisc.edu 144.92.9.53 wisc.edu 128.104.81.16 1985-09-30 00:00:00 -0400 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.53 www.library.wisc.edu wisc.edu 128.104.46.191 wisc.edu 144.92.93.172 wisc.edu 128.104.72.45 wisc.edu 128.104.201.96 1985-09-30 00:00:00 -0400 wisc.edu 144.92.248.152 1985-09-30 00:00:00 -0400 ghi.wisc.edu wisc.edu 128.104.23.171 wisc.edu 144.92.9.53 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.97 1985-09-30 00:00:00 -0400 wisc.edu 128.104.23.171 wisc.edu 128.104.80.40 wisc.edu 128.104.201.96 1985-09-30 00:00:00 -0400 wisc.edu 128.104.80.66 1985-09-30 00:00:00 -0400 wisc.edu 144.92.235.115 1985-09-30 00:00:00 -0400 home | russelabs.russell.wisc.edu wisc.edu 144.92.198.183 spatial.engr.wisc.edu wisc.edu 128.104.201.59 wisc.edu 128.104.80.210 sohe.wisc.edu wisc.edu 128.104.80.231 wisc.edu 128.104.201.70 uwmaterialculture.wordpress.co wisc.edu 192.0.78.13 1985-09-30 00:00:00 -0400 wisc.edu 128.104.23.171 wisc.edu 162.144.12.28 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.8 1985-09-30 00:00:00 -0400 babcock instdysci.wisc.edu wisc.edu 144.92.93.172 wisc.edu 128.104.201.71 1985-09-30 00:00:00 -0400 wisc.edu 128.104.201.47 wisc.edu 128.104.23.171 1985-09-30 00:00:00 -0400 wisc.edu 128.104.80.166 1985-09-30 00:00:00 -0400 wisc.edu 128.104.80.49 1985-09-30 00:00:00 -0400 wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.36 wisc.edu 128.104.201.59 wisc.edu 128.104.201.118 wisc.edu 128.104.80.110 parent.wisc.edu wisc.edu 144.92.9.200 wisc.edu 144.92.226.62 ocr.wisc.edu wisc.edu 144.92.9.200 www.library.wisc.edu wisc.edu 128.104.46.191 1985-09-30 00:00:00 -0400 international.wisc.edu wisc.edu 128.104.23.171 1985-09-30 00:00:00 -0400 international.wisc.edu wisc.edu 128.104.23.171 wisc.edu 192.185.90.29 75.119.211.47 wisc.edu 128.104.80.137 wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 www.uwilluminationjournal.com wisc.edu 50.87.248.219 wisc.edu 128.104.81.25 www.library.wisc.edu wisc.edu 128.104.46.191 1985-09-30 00:00:00 -0400 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 69.163.131.78 www.library.wisc.edu wisc.edu 128.104.46.191 1985-09-30 00:00:00 -0400 cae | compu www.cae.wisc.edu wisc.edu 128.104.201.49 wisc.edu 128.104.94.23 wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 wisc.edu 128.104.212.183 news.ls.wisc.edu wisc.edu 70.32.98.213 wisc.edu 128.104.80.178 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.53 wisc.edu 128.104.201.96 1985-09-30 00:00:00 -0400 wisc.edu 128.104.23.171 1985-09-30 00:00:00 -0400 teaching aca wisc.edu 144.92.239.181 wisc.edu 144.92.93.172 wisc.edu 144.92.9.53 wisc.edu 128.104.80.220 wisc.edu 144.92.93.172 wisc.edu 144.92.122.14 1985-09-30 00:00:00 -0400 wisc.edu 128.105.7.60 1985-09-30 00:00:00 -0400 wisc.edu 69.163.131.78 1985-09-30 00:00:00 -0400 wisc.edu 70.32.98.213 wisc.edu 144.92.93.172
domain_created
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048433, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1431335902, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1391404833, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1421828012, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1439082703, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1382042789, :type=>"cms"} {:from=>"drupal", :to=>nil, :ts=>1390831231, :type=>"cms"}|{:from=> {:from=>nil, :to=>"wordpress", :ts=>1378240618, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1373996605, :type=>"cms"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1403239666, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1419969557, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1417413741, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418233625, :type=>"cms"} {:from=>nil, :to=>"Dreamhost", :ts=>1428317978, :type=>"provider"} {:from=>nil, :to=>"wordpress", :ts=>1423774691, :type=>"cms"} {:from=>"drupal", :to=>"wordpress", :ts=>1380572179, :type=>"cms
{:from=>nil, :to=>"wordpress", :ts=>1376072348, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418233629, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1373995787, :type=>"cms"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1415249297, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1413734529, :type=>"cms"}
{:from=>nil, :to=>"WebsiteWelcome.com", :ts=>1431715015, :type=
{:from=>nil, :to=>"wordpress", :ts=>1405548427, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1389020880, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1388824229, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1429785991, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1405288747, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1375986536, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1384312424, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1440337372, :type=>"cms"}
{:from=>"6.28", :to=>nil, :ts=>1431097291, :type=>"cms_version"}|{: {:from=>nil, :to=>"wordpress", :ts=>1426616813, :type=>"cms"}
{:from=>"SoftLayer", :to=>nil, :ts=>1383692167, :type=>"provider"}
{:from=>nil, :to=>"wordpress", :ts=>1382067303, :type=>"cms"} {:from=>"6.28", :to=>"6.29", :ts=>1388215948, :type=>"cms_version {:from=>nil, :to=>"joomla", :ts=>1381430898, :type=>"cms"}|{:from= {:from=>nil, :to=>"wordpress", :ts=>1425649802, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1382042786, :type=>"cms"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1393845708, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1426795348, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1382424228, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1430401150, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1376112397, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1441467480, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1428198670, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1443024906, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1422819395, :type=>"cms"} {:from=>nil, :to=>"dotcms", :ts=>1374082448, :type=>"cms"}|{:from=
{:from=>nil, :to=>"wordpress", :ts=>1401077149, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1443229122, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1443223583, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1443223776, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418233627, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1403580175, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1435439321, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1420354938, :type=>"cms"}
{:from=>"sitefinity", :to=>"wordpress", :ts=>1428319236, :type=>"cm {:from=>nil, :to=>"wordpress", :ts=>1406522645, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1381430900, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1434794490, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1410371660, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1381475313, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1376079491, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1403812335, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1376012500, :type=>"cms"}
events
Appendix 4 - Acquia Report
id subdomain root wisdotresearchtest.engr.wisc.edu wisdotresearchtest.engr wisc safeu.wisc.edu safeu wisc asm.wisc.edu asm wisc gs1.gradsch.wisc.edu gs1.gradsch wisc textilecollection.wisc.edu textilecollection wisc rsasummerinstitute2015.wisc.edu rsasummerinstitute2015 wisc concepts.psych.wisc.edu concepts.psych wisc webhosting.doit.wisc.edu webhosting.doit wisc nitrogenseries.cals.wisc.edu nitrogenseries.cals wisc carboncycle2.aos.wisc.edu carboncycle2.aos wisc college.library.wisc.edu college.library wisc sc.cals.wisc.edu sc.cals wisc paulfricke.dysci.wisc.edu paulfricke.dysci wisc sleet.aos.wisc.edu sleet.aos wisc blogs.discovery.wisc.edu blogs.discovery wisc whyuwmadison.gradsch.wisc.edu whyuwmadison.gradsch wisc wicst.wisc.edu wicst wisc uwwritersinstitute.wisc.edu uwwritersinstitute wisc cgh.wisc.edu cgh wisc wisblawg.law.wisc.edu wisblawg.law wisc aci.wisc.edu aci wisc gshe.international.wisc.edu gshe.international wisc nanosoc.wisc.edu nanosoc wisc ediv.alexanderstreet.com.ezproxy.library.wisc ediv.alexanderstreet.com.ezproxy.lib wisc mobile.library.wisc.edu mobile.library wisc hpvc.slc.engr.wisc.edu hpvc.slc.engr wisc preview.mobile.wisc.edu preview.mobile wisc perspective.engr.wisc.edu perspective.engr wisc metc.med.wisc.edu metc.med wisc psgsc.wisc.edu psgsc wisc designgallery.wisc.edu designgallery wisc info.wisc.edu info wisc pubs.vip.wisc.edu pubs.vip wisc store.engr.wisc.edu store.engr wisc readon.education.wisc.edu readon.education wisc chemistry.library.wisc.edu chemistry.library wisc hospital.vetmed.wisc.edu hospital.vetmed wisc database.cs.wisc.edu database.cs wisc ip.cals.wisc.edu ip.cals wisc pgtp.wisc.edu pgtp wisc wid.wisc.edu wid wisc msc.wisc.edu msc wisc gratton.entomology.wisc.edu gratton.entomology wisc news.continuingstudies.wisc.edu news.continuingstudies wisc grazing.wisc.edu grazing wisc communityrelations.wisc.edu communityrelations wisc cggl.horticulture.wisc.edu cggl.horticulture wisc journalism.wisc.edu journalism wisc sts.wisc.edu sts wisc babcock.cals.wisc.edu babcock.cals wisc conneyproject.wisc.edu conneyproject wisc international.wisc.edu international wisc wisconsinintheworld.wisc.edu wisconsinintheworld wisc uwmadscience.news.wisc.edu uwmadscience.news wisc disabilitystudies.wisc.edu disabilitystudies wisc news.cals.wisc.edu news.cals wisc animalresearch.wisc.edu animalresearch wisc blog.journalism.wisc.edu blog.journalism wisc 365transition.wisc.edu 365transition wisc spooner.ars.wisc.edu spooner.ars wisc wvdl.wisc.edu wvdl wisc slislib.library.wisc.edu slislib.library wisc prelaw.wisc.edu prelaw wisc insideislam.wisc.edu insideislam wisc horticulture.wisc.edu horticulture wisc wpui.wisc.edu wpui wisc decorativearts.library.wisc.edu decorativearts.library wisc studyrooms.library.wisc.edu studyrooms.library wisc events.discovery.wisc.edu events.discovery wisc centerfornonprofits.wisc.edu centerfornonprofits wisc artsenterprise.wisc.edu artsenterprise wisc specialcollections.library.wisc.edu specialcollections.library wisc vote.wisc.edu vote wisc research.wisc.edu research wisc careercenter.education.wisc.edu careercenter.education wisc summer.wisc.edu summer wisc researchdata.wisc.edu researchdata wisc math.library.wisc.edu math.library wisc ethicsconference.journalism.wisc.edu ethicsconference.journalism wisc jewishstudies.wisc.edu jewishstudies wisc oceancarbon.aos.wisc.edu oceancarbon.aos wisc cae.wisc.edu cae wisc southasiaoutreach.wisc.edu southasiaoutreach wisc blog.commarts.wisc.edu blog.commarts wisc labs.russell.wisc.edu labs.russell wisc erp.wisc.edu erp wisc fellowships.international.wisc.edu fellowships.international wisc students.wisc.edu students wisc curb.journalism.wisc.edu curb.journalism wisc dare.news.wisc.edu dare.news wisc bridge.slc.engr.wisc.edu bridge.slc.engr wisc uwpd.wisc.edu uwpd wisc uwdcc.library.wisc.edu uwdcc.library wisc research.cals.wisc.edu research.cals wisc merit.education.wisc.edu merit.education wisc badgerengineers.engr.wisc.edu badgerengineers.engr wisc ipcm.wisc.edu ipcm wisc mediafluency.journalism.wisc.edu mediafluency.journalism wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress
websrv
Appendix 4 - Page 2 of 19
1985-09-30 00:00:00 -0400
php_5.4|platform_php
mobile|php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php
mobile|varnish mobile|php_5.3|platform_php mobile mobile content_embed|mobile mobile mobile|varnish mobile|php_5.5|platform_php|social_embed
mobile|php_5.3|platform_php php_5.4|platform_php|ipv6 php_5.3|platform_php|social_embed mobile|php_5.5|platform_php|social_embed
apache
apache
apache
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 cae | compu 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 university of
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
www.library.wisc.edu
www.library.wisc.edu
www.library.wisc.edu
sohe.wisc.edu
www.library.wisc.edu www.library.wisc.edu
www.library.wisc.edu
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 babcock instdysci.wisc.edu 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
www.library.wisc.edu uwveterinarycare.wisc.edu
sohe.wisc.edu
metc.wisc.edu
international.wisc.edu host.cals.wisc.edu www.library.wisc.edu www.library.wisc.edu
ghi.wisc.edu
grad.wisc.edu
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
info.wisc.edu
mobile|php_5.3|platform_php WebsiteWehtml5|mobile php_5.4|platform_php mobile|social_embed|social_media_like mobile|php_5.5|platform_php|social_embed mobile|php_5.3|platform_php|social_embed mobile|php_5.4|platform_php|ipv6 mobile mobile|varnish
Media Tem
grad.wisc.edu sohe.wisc.edu
uwpd.wisc.edu
redirect
1985-09-30 00:00:00 -0400
WebsiteWehtml5|mobile apache mobile|php_5.3|platform_php mobile apache mobile|php_5.3|platform_php apache mobile|platform_php|social_embed apache Dreamhost apache mobile|php_5.3|platform_php apache php_5.3|platform_php apache mobile|php_5.5|platform_php|social_embed apache Media Temakismet nginx mobile|php_5.3|platform_php apache Media Tem nginx php_5.4|platform_php apache php_5.4|platform_php apache content_embed|mobile|php_5.3|platform_php|social_embapache mobile apache mobile apache mobile|php_5.3|platform_php apache mobile|php_5.5|platform_php|social_embed apache apache mobile|php_5.3|platform_php apache mobile|php_5.3|platform_dotnet|platform_php iis mobile|varnish mobile|social_embed mobile|php_5.4|platform_php php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 mobile|varnish mobile|varnish mobile GoDaddy.c
title
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 www.library.wisc.edu 1985-09-30 00:00:00 -0400 error | drupa www.cals.wisc.edu
1985-09-30 00:00:00 -0400
domain_created
php_5.3|platform_php php_5.3|platform_php mobile|php_5.4|platform_php|ipv6 content_embed mobile|varnish
iis apache apache apache apache apache apache apache apache apache apache Dreamhost html5|mobile apache mobile|php_5.4|platform_php apache mobile|php_5.5|platform_php|social_embed|social_mediaapache mobile|social_media_like apache php_5.4|platform_php apache mobile|php_5.3|platform_php apache mobile apache mobile|varnish apache mobile|php_5.4|platform_php|ipv6 apache mobile apache php_5.4|platform_php|ipv6 apache WebsiteWehtml5|mobile nginx php_5.3|platform_php
mobile|php_5.3|platform_php html5|mobile|platform_dotnet|platform_php mobile mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|varnish mobile mobile|php_5.3|platform_php php_5.3|platform_php mobile mobile
features php_5.4|platform_php|ipv6 mobile Rackspace social_media_like content_embed|mobile
cms_veprovider
dns_provid ip wisc.edu 128.104.201.96 wisc.edu 144.92.239.248 wisc.edu 72.3.150.170 wisc.edu 128.104.81.157 wisc.edu 128.104.80.231 wisc.edu 144.92.226.67 wisc.edu 128.104.130.28 wisc.edu 128.104.80.146 wisc.edu 144.92.93.172 wisc.edu 144.92.131.146 wisc.edu 128.104.46.191 wisc.edu 144.92.93.164 wisc.edu 144.92.93.172 wisc.edu 144.92.131.231 wisc.edu 128.104.153.121 wisc.edu 128.104.81.157 wisc.edu 69.163.203.134 wisc.edu 128.104.80.130 wisc.edu 128.104.23.171 wisc.edu 128.104.94.64 wisc.edu 128.104.80.215 wisc.edu 128.104.23.171 wisc.edu 144.92.93.173 wisc.edu 128.104.46.191 wisc.edu 128.104.46.191 wisc.edu 128.104.201.107 wisc.edu 128.104.80.47 wisc.edu 128.104.201.96 wisc.edu 192.185.90.29 wisc.edu 144.92.93.172 wisc.edu 128.104.80.231 wisc.edu 144.92.9.53 wisc.edu 144.92.9.53 wisc.edu 128.104.201.96 wisc.edu 144.92.146.173 wisc.edu 128.104.46.191 wisc.edu 128.104.212.183 wisc.edu 128.105.7.60 wisc.edu 144.92.93.164 wisc.edu 192.185.90.30 wisc.edu 144.92.142.144 wisc.edu 128.104.80.18 wisc.edu 144.92.199.81 wisc.edu 128.104.80.125 wisc.edu 69.163.131.78 wisc.edu 144.92.9.53 wisc.edu 144.92.93.172 wisc.edu 144.92.22.140 wisc.edu 70.32.98.213 wisc.edu 144.92.93.172 wisc.edu 70.32.98.213 wisc.edu 128.104.23.171 wisc.edu 128.104.23.171 wisc.edu 144.92.9.53 wisc.edu 128.104.80.49 wisc.edu 144.92.93.164 wisc.edu 144.92.9.53 wisc.edu 144.92.22.140 wisc.edu 128.104.80.15 wisc.edu 144.92.93.172 wisc.edu 144.92.152.222 wisc.edu 128.104.46.191 wisc.edu 128.104.80.168 wisc.edu 128.104.23.171 wisc.edu 144.92.93.172 wisc.edu 128.104.201.94 wisc.edu 128.104.46.191 wisc.edu 128.104.46.191 wisc.edu 128.104.153.121 wisc.edu 128.104.80.231 wisc.edu 97.74.183.128 wisc.edu 128.104.46.191 wisc.edu 144.92.9.53 wisc.edu 128.104.80.20 wisc.edu 144.92.146.191 wisc.edu 128.104.81.101 wisc.edu 144.92.50.150 wisc.edu 128.104.46.191 wisc.edu 144.92.22.140 wisc.edu 70.32.98.213 wisc.edu 144.92.131.146 wisc.edu 128.104.201.49 wisc.edu 128.104.23.171 wisc.edu 144.92.226.62 wisc.edu 144.92.198.183 wisc.edu 192.185.90.29 wisc.edu 128.104.23.171 wisc.edu 128.104.81.107 wisc.edu 144.92.22.140 wisc.edu 144.92.9.53 wisc.edu 128.104.201.107 wisc.edu 144.92.239.248 wisc.edu 128.104.46.191 wisc.edu 144.92.93.164 wisc.edu 144.92.93.172 wisc.edu 128.104.201.96 wisc.edu 144.92.93.175 wisc.edu 144.92.22.140 {:from=>nil, :to=>"wordpress", :ts=>1442299161, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1443078127, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1406522643, :type=>"cms"} {:from=>"sitefinity", :to=>"wordpress", :ts=>1433612750, :type=>"cm
{:from=>nil, :to=>"wordpress", :ts=>1416786196, :type=>"cms"}
{:from=>nil, :to=>"WebsiteWelcome.com", :ts=>1426866545, :type=
{:from=>nil, :to=>"wordpress", :ts=>1403580301, :type=>"cms"} {:from=>"6.26", :to=>nil, :ts=>1382638278, :type=>"cms_version"}|{: {:from=>nil, :to=>"wordpress", :ts=>1382042789, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1439395865, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1441190912, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1412762419, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1410027420, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1441085046, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1425883369, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1439518748, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1412819173, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1383814281, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1427617770, :type=>"cms"}
{:from=>"6.26", :to=>nil, :ts=>1378082446, :type=>"cms_version"}|{:
{:from=>nil, :to=>"wordpress", :ts=>1418233633, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1379006783, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1440762577, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1400942025, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1425396025, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1400164443, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1390058144, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1370904053, :type=>"cms"} {:from=>"6.28", :to=>nil, :ts=>1431097112, :type=>"cms_version"}|{:
{:from=>"wordpress", :to=>nil, :ts=>1381455852, :type=>"cms"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1437114937, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1417256093, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1436974918, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1381768574, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1426102613, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1413403464, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1376004494, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1439082702, :type=>"cms"}
{:from=>nil, :to=>"WebsiteWelcome.com", :ts=>1431714918, :type= {:from=>nil, :to=>"wordpress", :ts=>1391290442, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1430051081, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1391670078, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1376095204, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1412659417, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418623609, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1382339810, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1417628263, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1422184755, :type=>"cms"} {:from=>"opentext_websolutions", :to=>"wordpress", :ts=>13760036 {:from=>nil, :to=>"wordpress", :ts=>1427133869, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1410830083, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1404003796, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1406836362, :type=>"cms"} {:from=>nil, :to=>"7.15", :ts=>1378526850, :type=>"cms_version"}|{: {:from=>nil, :to=>"wordpress", :ts=>1433658005, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1427160239, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1401493363, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1422179194, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1417675192, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1384395788, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1376039752, :type=>"cms"}
events {:from=>nil, :to=>"wordpress", :ts=>1431771501, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1444092016, :type=>"cms"} {:from=>"joomla", :to=>"wordpress", :ts=>1443811845, :type=>"cms
Appendix 4 - Acquia Report
id subdomain root giving.library.wisc.edu giving.library wisc evoc.wisc.edu evoc wisc blendedtoolkit.wisc.edu blendedtoolkit wisc biglearningevent.wisc.edu biglearningevent wisc uwfoundation.wisc.edu uwfoundation wisc cmcw2013.wisc.edu cmcw2013 wisc cals.wisc.edu cals wisc ecals.cals.wisc.edu ecals.cals wisc ars.wisc.edu ars wisc universityrelations.wisc.edu universityrelations wisc profs.wisc.edu profs wisc ippcc.polisci.wisc.edu ippcc.polisci wisc sohe.wisc.edu sohe wisc pddc.wisc.edu pddc wisc wyso.music.wisc.edu wyso.music wisc gobigread.wisc.edu gobigread wisc moocs.wisc.edu moocs wisc parent.wisc.edu parent wisc adminexcellence.wisc.edu adminexcellence wisc basis.wisc.edu basis wisc mobile.wisc.edu mobile wisc biology.library.wisc.edu biology.library wisc voices.wisc.edu voices wisc music.wisc.edu music wisc journalism.library.wisc.edu journalism.library wisc globalhealth.wisc.edu globalhealth wisc adf.wisc.edu adf wisc wwwtest.edinnovation.wisc.edu wwwtest.edinnovation wisc cooperhall.son.wisc.edu cooperhall.son wisc engineeringexpo.wisc.edu engineeringexpo wisc dawson.horticulture.wisc.edu dawson.horticulture wisc wisc.naxosmusiclibrary.com.ezproxy.library.w wisc.naxosmusiclibrary.com.ezproxy wisc staff.hsl.wisc.edu staff.hsl wisc mtle.wisc.edu mtle wisc meatandmore.wisc.edu meatandmore wisc staff.library.wisc.edu staff.library wisc grad.wisc.edu grad wisc ethics.journalism.wisc.edu ethics.journalism wisc vmthpub.vetmed.wisc.edu vmthpub.vetmed wisc yearofinnovation.wisc.edu yearofinnovation wisc clue.library.wisc.edu clue.library wisc cbc.cals.wisc.edu cbc.cals wisc pte.doit.wisc.edu pte.doit wisc mwec.wisc.edu mwec wisc rhetoric.commarts.wisc.edu rhetoric.commarts wisc parallelpress.library.wisc.edu parallelpress.library wisc plantcare.wisc.edu plantcare wisc umark.wisc.edu umark wisc lancaster.ars.wisc.edu lancaster.ars wisc epdnews.engr.wisc.edu epdnews.engr wisc uc.wisc.edu uc wisc insideuw.wisc.edu insideuw wisc climatequest.wisc.edu climatequest wisc fashionshow.wisc.edu fashionshow wisc badgerreport.journalism.wisc.edu badgerreport.journalism wisc archives.library.wisc.edu archives.library wisc business.library.wisc.edu business.library wisc physics.library.wisc.edu physics.library wisc wendt.library.wisc.edu wendt.library wisc info.gradsch.wisc.edu info.gradsch wisc mayrentinstitute.wisc.edu mayrentinstitute wisc es.carboncycle.aos.wisc.edu es.carboncycle.aos wisc genesisdev.wendt.wisc.edu genesisdev.wendt wisc dev.researchdata.wisc.edu dev.researchdata wisc casi.med.wisc.edu casi.med wisc wpindex.soils.wisc.edu wpindex.soils wisc advanceyourcareer.wisc.edu advanceyourcareer wisc news.ls.wisc.edu news.ls wisc digitalstudies.wisc.edu digitalstudies wisc bjb.engr.wisc.edu bjb.engr wisc bridgetest.slc.engr.wisc.edu bridgetest.slc.engr wisc arboretum.wisc.edu arboretum wisc dataplan.wisc.edu dataplan wisc socialsciref.library.wisc.edu socialsciref.library wisc grow.cals.wisc.edu grow.cals wisc prehealth.wisc.edu prehealth wisc wxguys.ssec.wisc.edu wxguys.ssec wisc sphere.ssec.wisc.edu sphere.ssec wisc mcrc.journalism.wisc.edu mcrc.journalism wisc secure.uwfoundation.wisc.edu secure.uwfoundation wisc support.journalism.wisc.edu support.journalism wisc jmq.sagepub.com.ezproxy.library.wisc.edu jmq.sagepub.com.ezproxy.library wisc sites.ophth.wisc.edu sites.ophth wisc vehicle.slc.engr.wisc.edu vehicle.slc.engr wisc ismajor.wisc.edu ismajor wisc dysci.wisc.edu dysci wisc wisa.cals.wisc.edu wisa.cals wisc sustainability.wisc.edu sustainability wisc ghi.wisc.edu ghi wisc doit.wisc.edu doit wisc graphics.cs.wisc.edu graphics.cs wisc graingerinstitute.engr.wisc.edu graingerinstitute.engr wisc birnlab.psychiatry.wisc.edu birnlab.psychiatry wisc kemp.wisc.edu kemp wisc fisc.cals.wisc.edu fisc.cals wisc wwwtest.evoc.wisc.edu wwwtest.evoc wisc cias.wisc.edu cias wisc organic.wisc.edu organic wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu s edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress mobile mobile|varnish mobile|php_5.3|platform_php mobile|platform_dotnet iis
mobile|varnish mobile|social_embed mobile|php_5.3|platform_php platform_dotnet iis mobile apache mobile mobile|varnish mobile|php_5.3|platform_php content_embed|mobile apache mobile|varnish mobile|php_5.5|platform_php mobile|php_5.5|platform_php apache mobile apache mobile nginx mobile|php_5.4|platform_php|ipv6 apache php_5.3|platform_php apache mobile apache php_5.5|platform_php apache mobile apache php_5.3|platform_php apache mobile mobile mobile|php_5.5|platform_php|social_embed|social_media
features websrv mobile|varnish content_embed mobile mobile html5|mobile mobile|social_embed mobile mobile mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile mobile|php_5.5|platform_php social_media_like mobile|php_5.3|platform_php|social_embed|social_media
Appendix 4 - Page 3 of 19 mobile|php_5.4|platform_php mobile|social_embed mobile|php_5.4|platform_php mobile|php_5.4|platform_php|ipv6 platform_dotnet mobile|php_5.3|platform_php mobile content_embed SingleHop html5|mobile|php_5.4|platform_php Dreamhost
apache apache apache apache apache
apache
content_embed|php_5.3|platform_php mobile|varnish php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.3|platform_php php_5.3|platform_php mobile content_embed content_embed|html5|mobile|php_5.5|platform_php|socia mobile|varnish mobile|varnish mobile|varnish mobile|php_5.4|platform_php|ipv6 mobile Media Tem apache mobile|php_5.3|platform_php mobile|php_5.4|platform_php|social_embed|ipv6 mobile php_5.5|platform_php php_5.3|platform_php apache mobile|social_media_like Media Tem apache mobile|php_5.3|platform_php php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php|ipv6 mobile mobile mobile|varnish mobile mobile php_5.4|platform_php|ipv6 php_5.4|platform_php|social_embed|ipv6 mobile|php_5.5|platform_php html5|mobile|platform_php apache mobile|platform_php apache mobile apache mobile|php_5.3|platform_php|ipv6 apache php_5.4|platform_php|ipv6 apache mobile|php_5.4|platform_php mobile|php_5.3|platform_php php_5.3|platform_php
Linode
Rackspace
cms_veprovider
title
www.supportuw.org
redirect www.library.wisc.edu
www.library.wisc.edu
www.library.wisc.edu
basis.ucdavis.edu
www.library.wisc.edu
secure.supportuw.org
researchdata.wisc.edu www.library.wisc.edu
www.library.wisc.edu www.library.wisc.edu www.library.wisc.edu wendt.engr.wisc.edu grad.wisc.edu
sohe.wisc.edu
www.library.wisc.edu
tt.doit.wisc.edu uwveterinarycare.wisc.edu
www.library.wisc.edu
uwveterinarycare.wisc.edu
www.library.wisc.edu
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 home - wisco 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 uw plant gro
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 julie dawson 1985-09-30 00:00:00 -0400 www.library.wisc.edu
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 plant diseaselabs.russell.wisc.edu 1985-09-30 00:00:00 -0400 www.wysomusic.org
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created
dns_provid ip wisc.edu 128.104.46.191 wisc.edu 128.104.80.139 wisc.edu 128.104.81.55 wisc.edu 128.104.80.133 wisc.edu 147.202.195.172 wisc.edu 128.104.80.105 wisc.edu 144.92.93.164 wisc.edu 144.92.93.164 wisc.edu 144.92.93.172 wisc.edu 144.92.9.53 wisc.edu 128.104.81.8 wisc.edu 144.92.158.36 wisc.edu 128.104.80.231 wisc.edu 144.92.198.183 wisc.edu 74.205.101.58 wisc.edu 128.104.46.19 wisc.edu 128.104.81.50 wisc.edu 144.92.9.53 wisc.edu 128.104.81.186 169.237.57.38 wisc.edu 128.104.80.47 wisc.edu 128.104.46.191 wisc.edu 144.92.9.53 wisc.edu 50.116.20.51 wisc.edu 128.104.46.191 wisc.edu 128.104.23.171 wisc.edu 144.92.158.36 wisc.edu 128.104.81.15 wisc.edu 192.0.78.13 wisc.edu 128.104.201.71 wisc.edu 144.92.93.172 wisc.edu 128.104.46.191 wisc.edu 144.92.50.151 wisc.edu 144.92.239.218 wisc.edu 144.92.93.172 wisc.edu 128.104.46.191 wisc.edu 128.104.81.157 wisc.edu 144.92.22.140 wisc.edu 128.104.212.183 wisc.edu 144.92.9.53 wisc.edu 128.104.46.191 wisc.edu 144.92.93.172 wisc.edu 128.104.81.186 wisc.edu 128.104.212.183 wisc.edu 144.92.226.62 wisc.edu 128.104.46.191 wisc.edu 144.92.93.172 wisc.edu 144.92.9.53 wisc.edu 144.92.93.172 wisc.edu 144.92.225.247 wisc.edu 144.92.9.53 wisc.edu 144.92.9.53 wisc.edu 128.104.80.206 wisc.edu 128.104.80.231 wisc.edu 144.92.22.140 wisc.edu 128.104.46.191 wisc.edu 128.104.46.191 wisc.edu 128.104.46.191 wisc.edu 128.104.201.96 wisc.edu 128.104.81.157 wisc.edu 70.32.98.213 wisc.edu 144.92.131.146 wisc.edu 128.104.201.123 wisc.edu 144.92.50.150 wisc.edu 144.92.50.141 wisc.edu 144.92.93.172 wisc.edu 128.104.81.70 wisc.edu 70.32.98.213 wisc.edu 144.92.226.67 wisc.edu 128.104.201.96 wisc.edu 128.104.201.70 wisc.edu 128.104.81.137 wisc.edu 144.92.50.150 wisc.edu 128.104.46.191 wisc.edu 144.92.93.164 wisc.edu 128.104.81.44 wisc.edu 128.104.108.105 wisc.edu 128.104.108.105 wisc.edu 144.92.22.140 wisc.edu 144.92.185.29 wisc.edu 144.92.22.140 wisc.edu 128.104.46.191 wisc.edu 128.104.254.100 wisc.edu 128.104.201.70 wisc.edu 128.104.23.171 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 128.104.81.171 wisc.edu 128.104.23.171 wisc.edu 128.104.80.153 wisc.edu 128.105.7.32 wisc.edu 128.104.201.59 wisc.edu 144.92.177.178 wisc.edu 144.92.93.172 wisc.edu 144.92.93.164 wisc.edu 144.92.239.191 wisc.edu 108.163.198.26 wisc.edu 69.163.131.78 {:from=>"Dreamhost", :to=>"SingleHop", :ts=>1390350823, :type=>"
{:from=>nil, :to=>"wordpress", :ts=>1415140400, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1401004167, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418233634, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1439039791, :type=>"cms"}
{:from=>"wordpress", :to=>"drupal", :ts=>1418330216, :type=>"cms
{:from=>nil, :to=>"wordpress", :ts=>1426867488, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1429183429, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1420900028, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1382033169, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1395024315, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1409179562, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1422118329, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1441149694, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1424631087, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1431651990, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1416786509, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1431920651, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1424813984, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1403580175, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1430401321, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1441319033, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1424838774, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1384296341, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1442047343, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1426401289, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1422187923, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1441821630, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1389245279, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1414135828, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1409072937, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1434917792, :type=>"cms"} {:from=>nil, :to=>"drupal", :ts=>1417931916, :type=>"cms"}|{:from=> {:from=>nil, :to=>"wordpress", :ts=>1414136032, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418233628, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1442980817, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1418313248, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1442323054, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1375542428, :type=>"cms"}
{:from=>nil, :to=>"drupal", :ts=>1419778372, :type=>"cms"}|{:from=> {:from=>nil, :to=>"wordpress", :ts=>1416519453, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1432170293, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1435084635, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1378685471, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1442180480, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1389216656, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1410308622, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1427049765, :type=>"cms"} {:from=>nil, :to=>"Linode", :ts=>1412926273, :type=>"provider"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1440618280, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1411669772, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1401236741, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1421050559, :type=>"cms"} {:from=>nil, :to=>"PEER 1", :ts=>1401284601, :type=>"provider"}|{:f
{:from=>"sharepoint", :to=>nil, :ts=>1373799401, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1417463125, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1404087333, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1372330797, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1375996187, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1440995669, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1416141988, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1382042788, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1418233250, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1381894169, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1442981174, :type=>"cms"}
events {:from=>nil, :to=>"wordpress", :ts=>1441709004, :type=>"cms"}
Appendix 4 - Acquia Report
id ocr.wisc.edu wwwtest.materialculture.wisc.edu wun.wisc.edu afs.slc.engr.wisc.edu hci.cs.wisc.edu staterelations.wisc.edu vetmed.wisc.edu chars.cals.wisc.edu chancellor.wisc.edu library.wisc.edu vip.wisc.edu sapir.psych.wisc.edu carboncycle.aos.wisc.edu preview.anthropology.wisc.edu spatial.engr.wisc.edu blog.studyabroad.wisc.edu academictech.doit.wisc.edu meathaccp.wisc.edu finduw.wisc.edu federalrelations.wisc.edu studentprint.rso.wisc.edu template.education.wisc.edu pserc.wisc.edu news.education.wisc.edu art.wisc.edu artonbascom.education.wisc.edu businessoffice.education.wisc.edu mspe.education.wisc.edu mentalhealthinkids.wisc.edu wd.education.wisc.edu biotech.wisc.edu elpa.education.wisc.edu counselingpsych.education.wisc.edu casi.education.wisc.edu campusconnections.education.wisc.edu insider.education.wisc.edu edpsych.education.wisc.edu kinesiology.education.wisc.edu eps.education.wisc.edu dance.wisc.edu womenshealth.wisc.edu eop.education.wisc.edu amedweek.education.wisc.edu ci.education.wisc.edu education.wisc.edu literacy.education.wisc.edu wire.wisc.edu aics.education.wisc.edu learningconnections.education.wisc.edu rpse.education.wisc.edu wiscape.wisc.edu union.wisc.edu learn.ansci.wisc.edu intranet.wei.wisc.edu intranet.bus.wisc.edu intranet.hip.wisc.edu home.intranet.hip.wisc.edu intranet2.bus.wisc.edu groups.ssec.wisc.edu tcvideo.engr.wisc.edu epdfiles.engr.wisc.edu akka.genetics.wisc.edu uwamic.wisc.edu paris.soc.wisc.edu polygon.engr.wisc.edu hipaa.wisc.edu pgwh.history.wisc.edu arthistory.wisc.edu publicart.wisc.edu legal.wisc.edu bethesda.soc.wisc.edu goldberg.history.wisc.edu clusters.wisc.edu wiscel.wisc.edu uwdg.rso.wisc.edu europaclub.rso.wisc.edu ballroom.rso.wisc.edu moodle.education.wisc.edu ay14-15.moodle.wisc.edu conference.education.wisc.edu ay15-16.moodle.wisc.edu ay.moodle.wisc.edu uonline.education.wisc.edu courses.moodle.wisc.edu ce.pharmacy.wisc.edu special.moodle.wisc.edu wiscipedia.wisc.edu pac.anesthesia.wisc.edu anesthesia.wisc.edu humonc.wisc.edu ncaacertification.wisc.edu orthoplan.sco.wisc.edu broadbandmap.sco.wisc.edu allen.neep.wisc.edu digital.library.wisc.edu siac.wisc.edu geoalliance.wisc.edu sciencespeakers.engr.wisc.edu
subdomain ocr wwwtest.materialculture wun afs.slc.engr hci.cs staterelations vetmed chars.cals chancellor library vip sapir.psych carboncycle.aos preview.anthropology spatial.engr blog.studyabroad academictech.doit meathaccp finduw federalrelations studentprint.rso template.education pserc news.education art artonbascom.education businessoffice.education mspe.education mentalhealthinkids wd.education biotech elpa.education counselingpsych.education casi.education campusconnections.education insider.education edpsych.education kinesiology.education eps.education dance womenshealth eop.education amedweek.education ci.education education literacy.education wire aics.education learningconnections.education rpse.education wiscape union learn.ansci intranet.wei intranet.bus intranet.hip home.intranet.hip intranet2.bus groups.ssec tcvideo.engr epdfiles.engr akka.genetics uwamic paris.soc polygon.engr hipaa pgwh.history arthistory publicart legal bethesda.soc goldberg.history clusters wiscel uwdg.rso europaclub.rso ballroom.rso moodle.education ay14-15.moodle conference.education ay15-16.moodle ay.moodle uonline.education courses.moodle ce.pharmacy special.moodle wiscipedia pac.anesthesia anesthesia humonc ncaacertification orthoplan.sco broadbandmap.sco allen.neep digital.library siac geoalliance sciencespeakers.engr
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms cms_veprovider wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress wordpress websphere_p tumblr squarespace squarespace sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity sitefinity silverstripe sharepoint sharepoint sharepoint sharepoint sharepoint sharepoint plone osxserver osxserver osxserver opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_wsm opentext_we opentext_we opentext_we moodle moodle moodle moodle moodle moodle moodle moodle moodle mediawiki mediawiki mediawiki 1.25.1 mediawiki 1.25.2 lotuswcm joomla joomla joomla joomla joomla joomla joomla
Appendix 4 - Page 4 of 19 php_5.3|platform_php php_5.3|platform_php php_5.4|platform_php|ipv6
php_5.3|platform_php php_5.3|platform_php php_5.4|platform_php|ipv6
php_5.4|platform_php|ipv6 mobile|php_5.5|platform_php mobile|php_5.4|platform_php|ipv6 php_5.1|platform_php
mobile|php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php|ipv6
mobile|php_5.4|platform_php|ipv6
ipv6
platform_dotnet
content_embed
mobile mobile mobile
platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet mobile|platform_dotnet platform_dotnet platform_dotnet mobile|platform_dotnet mobile|platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet|social_embed platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet content_embed|platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet mobile platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet platform_dotnet
features mobile|php_5.3|platform_php mobile php_5.4|platform_php php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php mobile|php_5.3|platform_php ipv6 mobile|php_5.3|platform_php mobile|php_5.3|platform_php mobile|varnish php_5.3|platform_php php_5.3|platform_php mobile|php_5.3|platform_php mobile mobile|php_5.4|platform_php|ipv6 php_5.5|platform_php|social_embed mobile platform_dotnet mobile php_5.3|platform_php
apache
apache
apache apache apache
apache
iis iis iis
apache apache apache iis apache apache apache apache apache
apache apache
iis iis iis iis iis iis zserver
iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis iis
iis
apache
websrv apache nginx apache apache apache
redirect dns_provid ip wisc.edu 144.92.9.53 uwmaterialculture.wordpress.co wisc.edu 192.0.78.12 international.wisc.edu wisc.edu 128.104.23.171 1985-09-30 00:00:00 -0400 wisc.edu 128.104.201.70 wisc.edu 128.105.7.55 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.53 wisc.edu 128.104.212.10 1985-09-30 00:00:00 -0400 welcome to t wisc.edu 144.92.93.172 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.53 1985-09-30 00:00:00 -0400 wisc.edu 128.104.46.191 1985-09-30 00:00:00 -0400 info.wisc.edu wisc.edu 144.92.9.53 wisc.edu 128.104.130.118 1985-09-30 00:00:00 -0400 wisc.edu 144.92.131.146 wisc.edu 144.92.190.47 wisc.edu 128.104.201.59 1985-09-30 00:00:00 -0400 wisc.edu 128.104.23.171 wisc.edu 128.104.80.153 1985-09-30 00:00:00 -0400 technology swww.doit.wisc.edu wisc.edu 128.104.81.186 wisc.edu 66.6.44.4 wisc.edu 144.92.9.53 1985-09-30 00:00:00 -0400 www.stuprint.org wisc.edu 198.49.23.144 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.119 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.186 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.69 wisc.edu 144.92.146.106 1985-09-30 00:00:00 -0400 news.education.wisc.edu wisc.edu 144.92.146.69 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 eptc.education.wisc.edu wisc.edu 144.92.146.69 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.69 1985-09-30 00:00:00 -0400 wisc.edu 144.92.52.158 wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 education.wisc.edu wisc.edu 144.92.146.121 news.education.wisc.edu wisc.edu 144.92.146.69 1985-09-30 00:00:00 -0400 news.education.wisc.edu wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 wisc.edu 144.92.146.86 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.27 wisc.edu 144.92.146.69 news.education.wisc.edu wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 wisc.edu 144.92.146.121 ci.education.wisc.edu 144.92.146.132 wisc.edu 128.104.80.225 education.wisc.edu wisc.edu 144.92.146.121 news.education.wisc.edu wisc.edu 144.92.146.69 wisc.edu 144.92.146.69 wisc.edu 144.92.146.118 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.111 wisc.edu 144.92.75.18 wisc.edu 144.92.98.190 connect.bus.wisc.edu wisc.edu 144.92.213.26 wisc.edu 128.104.140.155 wisc.edu 128.104.140.156 wisc.edu 144.92.212.53 1985-09-30 00:00:00 -0400 wisc.edu 128.104.108.82 wisc.edu 144.92.225.230 wisc.edu 144.92.225.222 wisc.edu 144.92.162.10 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.51 1985-09-30 00:00:00 -0400 www.engr.wisc.edu wisc.edu 128.104.201.59 wisc.edu 144.92.239.157 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 144.92.239.253 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.92 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 wisc.edu 128.104.201.125 128.104.81.249 128.104.81.94 128.104.81.94 1985-09-30 00:00:00 -0400 wisc.edu 144.92.146.17 wisc.edu 128.104.201.75 moodle.education.wisc.edu wisc.edu 144.92.146.17 wisc.edu 128.104.201.75 ay15-16.moodle.wisc.edu wisc.edu 128.104.201.75 wisc.edu 128.104.80.167 wisc.edu 128.104.201.75 1985-09-30 00:00:00 -0400 wisc.edu 128.104.115.238 wisc.edu 128.104.201.75 wisc.edu 144.92.74.97 wisc.edu 144.92.218.249 wisc.edu 144.92.218.249 wisc.edu 144.92.219.27 wisc.edu 144.92.9.53 wisc.edu 144.92.235.101 wisc.edu 144.92.235.101 wisc.edu 128.104.201.69 uwdc.library.wisc.edu wisc.edu 128.104.1.195 1985-09-30 00:00:00 -0400 wisc.edu 144.92.235.101 wisc.edu 144.92.235.101 wisc.edu 128.104.201.59
domain_created title 1985-09-30 00:00:00 -0400
events
{:from=>nil, :to=>"joomla", :ts=>1426818079, :type=>"cms"}
{:from=>nil, :to=>"joomla", :ts=>1400729585, :type=>"cms"} {:from=>nil, :to=>"joomla", :ts=>1380801003, :type=>"cms"}
{:from=>nil, :to=>"1.25.1", :ts=>1439335536, :type=>"cms_version"} {:from=>nil, :to=>"1.25.2", :ts=>1442210716, :type=>"cms_version"} {:from=>"lotuswcm", :to=>"websphere_portal", :ts=>1375448668, :ty
{:from=>nil, :to=>"moodle", :ts=>1432379879, :type=>"cms"}
{:from=>nil, :to=>"moodle", :ts=>1415716274, :type=>"cms"} {:from=>nil, :to=>"moodle", :ts=>1391772732, :type=>"cms"} {:from=>nil, :to=>"moodle", :ts=>1443622076, :type=>"cms"} {:from=>nil, :to=>"moodle", :ts=>1415715996, :type=>"cms"} {:from=>nil, :to=>"moodle", :ts=>1442909430, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1410189444, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1402115930, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1403345835, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1419336814, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1410632735, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1405619039, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1412105223, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1400465692, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1411609405, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1410632734, :type=>"cms"} {:from=>nil, :to=>"opentext_websolutions", :ts=>1374495662, :type= {:from=>nil, :to=>"opentext_wsm", :ts=>1403118010, :type=>"cms"}
{:from=>nil, :to=>"osxserver", :ts=>1441400749, :type=>"cms"}
{:from=>nil, :to=>"sitefinity", :ts=>1382650664, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1401049136, :type=>"cms"} {:from=>nil, :to=>"sharepoint", :ts=>1384948829, :type=>"cms"} {:from=>nil, :to=>"sharepoint", :ts=>1441612798, :type=>"cms"} {:from=>nil, :to=>"sharepoint", :ts=>1391703657, :type=>"cms"} {:from=>nil, :to=>"sharepoint", :ts=>1424679243, :type=>"cms"}
{:from=>nil, :to=>"sitefinity", :ts=>1429907460, :type=>"cms"} {:from=>nil, :to=>"sitefinity", :ts=>1400506230, :type=>"cms"}
{:from=>"sitefinity", :to=>nil, :ts=>1418903342, :type=>"cms"}|{:from
{:from=>nil, :to=>"sitefinity", :ts=>1416309535, :type=>"cms"} {:from=>nil, :to=>"sitefinity", :ts=>1376025079, :type=>"cms"}
{:from=>nil, :to=>"sitefinity", :ts=>1406512802, :type=>"cms"}
{:from=>nil, :to=>"sitefinity", :ts=>1384256547, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1392356986, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1403580046, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1440944914, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1410049860, :type=>"cms"} {:from=>"wordpress", :to=>nil, :ts=>1374767798, :type=>"cms"} {:from=>"6.25", :to=>"6.28", :ts=>1378486521, :type=>"cms_version {:from=>nil, :to=>"websphere_portal", :ts=>1383050902, :type=>"cm {:from=>"Rackspace", :to=>nil, :ts=>1376008336, :type=>"provider"} {:from=>nil, :to=>"squarespace", :ts=>1427467749, :type=>"cms"} {:from=>"Bluehost.com", :to=>nil, :ts=>1440332654, :type=>"provide
{:from=>"6.31", :to=>nil, :ts=>1413397705, :type=>"cms_version"}|{: {:from=>nil, :to=>"wordpress", :ts=>1381956296, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1407253583, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1373489615, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1427183804, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1375963919, :type=>"cms"}
Appendix 4 - Acquia Report
id news.sco.wisc.edu qrm.engr.wisc.edu designlab.wisc.edu glial.psych.wisc.edu sco.wisc.edu uwdc.library.wisc.edu ecohealth.wisc.edu upgrade.learnuw.wisc.edu commencement.engr.wisc.edu narrativestructures.wisc.edu linebreaks.wisc.edu ans.engr.wisc.edu quality-safety-innovation.wisc.edu msc.engr.wisc.edu comets.wisc.edu sober.philosophy.wisc.edu spa.wisc.edu teachonline.wisc.edu sharinglearningstories.wisc.edu preview.chazen.wisc.edu chazen.wisc.edu humanities.wisc.edu babel.lss.wisc.edu preview.iss.wisc.edu pop50.pophealth.wisc.edu lss.wisc.edu microscopy.wisc.edu atrium.math.wisc.edu mentoringresources.ictr.wisc.edu silvis.forest.wisc.edu neurology.wisc.edu whocancerpain.wisc.edu biocomplexity.limnology.wisc.edu wadem.medicine.wisc.edu pophealth.wisc.edu complit.lss.wisc.edu eall.wisc.edu ces.wisc.edu religiousstudies.lss.wisc.edu pfmp.wisc.edu physicianassistant.wisc.edu socwork.wisc.edu oconnorgiles.molbio.wisc.edu math.wisc.edu ccwpp.wisc.edu scandesign.scandinavian.wisc.edu kalejta.virology.wisc.edu odyssey.wisc.edu wibcerp.wisc.edu advising.wisc.edu hamers.chem.wisc.edu directory.genetics.wisc.edu jin.chem.wisc.edu pportal.primate.wisc.edu sla.wisc.edu evolution.wisc.edu www2.medicine.wisc.edu wbi.wisc.edu pathology.wisc.edu tcnl.med.wisc.edu chicla.wisc.edu frit.wisc.edu 2014slasymposium.lss.wisc.edu frit.lss.wisc.edu ups.physics.wisc.edu test.brazil.wisc.edu wacc.wisc.edu uwscfm.chem.wisc.edu neurosurgery.wisc.edu medievalstudies.wisc.edu cpcp.wisc.edu wwwtest.uwmrrc.wisc.edu qc.physics.wisc.edu softmatter.chem.wisc.edu iss.wisc.edu 508-255-refresh.trace.wisc.edu massspec.chem.wisc.edu meetings.wipac.wisc.edu wiqi.physics.wisc.edu gmwp.wisc.edu littlelisteners.waisman.wisc.edu dare.wisc.edu cinema.wisc.edu gafis.frit.wisc.edu wildlife.wisc.edu biocomp.wisc.edu iidd.wisc.edu lca.wisc.edu aipes.engr.wisc.edu plantpath.wisc.edu ling.wisc.edu helpdesk.hip.wisc.edu kaz.med.wisc.edu biochem.wisc.edu mbtg.wisc.edu app.medicine.wisc.edu languageinstitute.wisc.edu burstyn.chem.wisc.edu
subdomain news.sco qrm.engr designlab glial.psych sco uwdc.library ecohealth upgrade.learnuw commencement.engr narrativestructures linebreaks ans.engr quality-safety-innovation msc.engr comets sober.philosophy spa teachonline sharinglearningstories preview.chazen chazen humanities babel.lss preview.iss pop50.pophealth lss microscopy atrium.math mentoringresources.ictr silvis.forest neurology whocancerpain biocomplexity.limnology wadem.medicine pophealth complit.lss eall ces religiousstudies.lss pfmp physicianassistant socwork oconnorgiles.molbio math ccwpp scandesign.scandinavian kalejta.virology odyssey wibcerp advising hamers.chem directory.genetics jin.chem pportal.primate sla evolution www2.medicine wbi pathology tcnl.med chicla frit 2014slasymposium.lss frit.lss ups.physics test.brazil wacc uwscfm.chem neurosurgery medievalstudies cpcp wwwtest.uwmrrc qc.physics softmatter.chem iss 508-255-refresh.trace massspec.chem meetings.wipac wiqi.physics gmwp littlelisteners.waisman dare cinema gafis.frit wildlife biocomp iidd lca aipes.engr plantpath ling helpdesk.hip kaz.med biochem mbtg app.medicine languageinstitute burstyn.chem
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms cms_veprovider features websrv joomla php_5.3|platform_php joomla content_embed|php_5.4|platform_php|ipv6 joomla apache joomla php_5.2|platform_php joomla php_5.3|platform_php joomla joomla googlesites google content_embed|mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google googlesites google mobile google googlesites google mobile|ipv6 google googlesites google mobile google googlesites google mobile|ipv6 google googlesites google mobile|ipv6 google expressionen platform_php apache expressionen expressionen Bluehost.comobile apache drupal 6.22 apache drupal 7.38 mobile drupal 7.39 drupal php_5.4|platform_php|social_embed drupal 6.37 drupal 6.37 php_5.4|platform_php drupal 6.37 Pantheon varnish apache drupal 7.38 php_5.5|platform_php drupal 7.39 php_5.6|platform_dotnet|platform_php iis drupal platform_php apache drupal platform_php apache drupal mobile|platform_php nginx drupal 7.39 drupal php_5.3|platform_php drupal php_5.3|platform_php drupal php_5.3|platform_php drupal 6.37 php_5.3|platform_php|social_embed|social_media_like drupal php_5.3|platform_php|social_embed|social_media_like drupal php_5.3|platform_php|social_embed|social_media_like drupal content_embed|php_5.4|platform_php|shoppingcart|socia drupal 6.22 php_5.3|platform_dotnet|platform_php iis drupal 7.39 php_5.4|platform_php drupal php_5.3|platform_php drupal php_5.3|platform_php drupal 6.22 php_5.3|platform_dotnet|platform_php iis drupal varnish drupal 6.28 drupal 7.39 mobile drupal 7.39 php_5.3|platform_php drupal 7.39 php_5.3|platform_php drupal 7.39 mobile|php_5.3|platform_php drupal 7.32 platform_php apache drupal 7.0 mobile|php_5.4|platform_php drupal 7.39 content_embed drupal 7.0 mobile|php_5.3|platform_php apache drupal 7.0 mobile|php_5.3|platform_php drupal 7.39 php_5.6|platform_dotnet|platform_php iis drupal 7.37 php_5.4|platform_php|ipv6 drupal 7.0 mobile|php_5.4|platform_php drupal 7.0 mobile|php_5.4|platform_php drupal 7.0 mobile|php_5.4|platform_php|social_embed|social_media drupal 6.37 mobile|php_5.4|platform_php drupal 7.39 php_5.4|platform_php|ipv6 drupal 7.39 mobile|php_5.4|platform_php drupal 7.20 php_5.4|platform_php|ipv6 drupal 7.39 mobile|php_5.3|platform_php drupal 7.35 php_5.3|platform_dotnet|platform_php iis drupal 6.28 php_5.3|platform_php apache drupal 7.38 mobile|php_5.5|platform_php drupal 7.31 mobile apache drupal 7.0 php_5.4|platform_php|ipv6 drupal 7.39 php_5.3|platform_php drupal 7.38 mobile drupal 6.22 apache drupal 7.35 mobile|php_5.3|platform_php apache drupal 7.0 mobile|php_5.3|platform_php drupal 7.38 php_5.4|platform_php|ipv6 apache drupal 7.0 mobile|php_5.4|platform_php drupal 7.0 mobile|php_5.4|platform_php drupal php_5.3|platform_php|social_embed drupal 7.39 mobile|php_5.3|platform_php drupal 7.0 mobile|php_5.4|platform_php drupal 6.36 php_5.3|platform_php drupal 6.33 php_5.3|platform_php drupal php_5.3|platform_php drupal php_5.3|platform_php drupal 6.26 php_5.4|platform_php|ipv6 drupal 6.35 mobile drupal 6.37 php_5.3|platform_php drupal 7.39 mobile|php_5.3|platform_php drupal 7.37 php_5.4|platform_php|ipv6 drupal 7.39 php_5.6|platform_php drupal 7.33 mobile|php_5.3|platform_dotnet|platform_php iis drupal 7.39 mobile|php_5.3|platform_php apache drupal 7.0 mobile|php_5.4|platform_php drupal 7.39 php_5.3|platform_php
redirect
Appendix 4 - Page 5 of 19
mass spectr icecube mee welcome | w greater mad home | little 1985-09-30 00:00:00 -0400 dictionary of 1985-09-30 00:00:00 -0400 welcome to c 1985-09-30 00:00:00 -0400 welcome | ga 1985-09-30 00:00:00 -0400 home | fores 1985-09-30 00:00:00 -0400 michael h. co 1985-09-30 00:00:00 -0400 welcome to s 1985-09-30 00:00:00 -0400 welcome | la 1985-09-30 00:00:00 -0400 si-aipes rese 1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 about the de 1985-09-30 00:00:00 -0400 hip it helpde 1985-09-30 00:00:00 -0400 home | tcnl tcnl.bme.wisc.edu department o 1985-09-30 00:00:00 -0400 mbtg 1985-09-30 00:00:00 -0400 department o home | langu 1985-09-30 00:00:00 -0400 welcome to t
1985-09-29 20:00:00 -0400 l&s learning 1985-09-30 00:00:00 -0400 welcome to i 1985-09-30 00:00:00 -0400 phs home | p 1985-09-30 00:00:00 -0400 l&s learning 1985-09-30 00:00:00 -0400 microscopy a 1985-09-30 00:00:00 -0400 directory | op 1985-09-30 00:00:00 -0400 mentoringres 1985-09-30 00:00:00 -0400 silvis lab | sp department o 1985-09-30 00:00:00 -0400 welcome | ca 1985-09-30 00:00:00 -0400 north temperlter.limnology.wisc.edu 1985-09-30 00:00:00 -0400 department owww.medicine.wisc.edu 1985-09-30 00:00:00 -0400 phs home | p 1985-09-30 00:00:00 -0400 welcome | co 1985-09-30 00:00:00 -0400 eall home | e 1985-09-30 00:00:00 -0400 center for eu 1985-09-30 00:00:00 -0400 welcome! | re 1985-09-30 00:00:00 -0400 professional 1985-09-30 00:00:00 -0400 uw-madison www.fammed.wisc.edu 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 research ove 1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 the center on 1985-09-30 00:00:00 -0400 home | uw m 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 welcome | uw 1985-09-30 00:00:00 -0400 wisconsin br 1985-09-30 00:00:00 -0400 welcome to y 1985-09-30 00:00:00 -0400 hamers grou 1985-09-30 00:00:00 -0400 everyone | la 1985-09-30 00:00:00 -0400 jin group | de 1985-09-30 00:00:00 -0400 primate porta 1985-09-30 00:00:00 -0400 welcome | do 1985-09-30 00:00:00 -0400 about | j.f. cr 1985-09-30 00:00:00 -0400 university of www.medicine.wisc.edu 1985-09-30 00:00:00 -0400 bioenergy in energy.wisc.edu 1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 home | tcnl tcnl.bme.wisc.edu 1985-09-30 00:00:00 -0400 welcome | ch 1985-09-30 00:00:00 -0400 welcome | de 1985-09-30 00:00:00 -0400 home | 2014 1985-09-30 00:00:00 -0400 welcome | defrit.wisc.edu 1985-09-30 00:00:00 -0400 the physics c 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 wacc | wisco uw system c department o the program cpcp.wisc.ed welcome to u welcome | w wiqi.physics.wisc.edu 1985-09-30 00:00:00 -0400 home | mah 1985-09-30 00:00:00 -0400 welcome to i
www.spamadison.org
1985-09-30 00:00:00 -0400 community osites.google.com
www.atomicbadger.org
1985-09-30 00:00:00 -0400 narrative stru
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created title 1985-09-30 00:00:00 -0400
dns_provid ip wisc.edu 144.92.235.101 wisc.edu 128.104.201.59 wisc.edu 128.104.81.231 wisc.edu 128.104.130.59 wisc.edu 144.92.235.101 wisc.edu 128.104.1.195 wisc.edu 144.92.239.163 wisc.edu 74.125.141.121 wisc.edu 64.233.184.121 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 64.233.171.121 wisc.edu 216.58.209.174 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 74.125.29.121 wisc.edu 128.104.80.42 wisc.edu 128.104.80.42 wisc.edu 67.222.37.186 144.92.115.157 wisc.edu 144.92.239.153 wisc.edu 144.92.239.161 wisc.edu 144.92.190.42 wisc.edu 144.92.48.141 wisc.edu 144.92.166.28 wisc.edu 184.106.101.123 wisc.edu 144.92.199.195 wisc.edu 128.104.205.125 wisc.edu 128.104.81.112 144.92.62.194 144.92.76.40 wisc.edu 144.92.239.161 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 144.92.41.18 wisc.edu 144.92.158.32 wisc.edu 144.92.238.12 wisc.edu 144.92.166.28 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 144.92.238.12 wisc.edu 216.27.28.30 wisc.edu 144.92.239.196 wisc.edu 128.104.80.251 wisc.edu 128.104.70.5 wisc.edu 144.92.162.89 wisc.edu 128.104.71.108 wisc.edu 128.104.93.27 wisc.edu 144.92.158.32 wisc.edu 128.104.153.102 wisc.edu 144.92.76.40 wisc.edu 144.92.98.187 wisc.edu 144.92.28.35 wisc.edu 128.104.201.97 wisc.edu 144.92.158.32 wisc.edu 144.92.158.32 wisc.edu 144.92.158.32 wisc.edu 144.92.158.32 wisc.edu 128.104.160.19 wisc.edu 128.104.23.171 wisc.edu 128.104.201.94 wisc.edu 128.104.71.108 wisc.edu 144.92.80.22 wisc.edu 144.92.115.213 wisc.edu 144.92.73.51 wisc.edu 128.104.81.190 wisc.edu 128.104.160.19 wisc.edu 128.104.71.108 wisc.edu 144.92.239.153 128.104.192.44 wisc.edu 128.104.71.108 wisc.edu 128.104.5.107 wisc.edu 128.104.160.19 wisc.edu 144.92.158.32 wisc.edu 144.92.158.32 wisc.edu 144.92.115.213 wisc.edu 144.92.226.67 wisc.edu 144.92.158.32 wisc.edu 144.92.199.125 wisc.edu 144.92.237.198 wisc.edu 144.92.115.213 wisc.edu 144.92.115.213 wisc.edu 128.104.201.59 wisc.edu 144.92.198.11 wisc.edu 144.92.115.213 wisc.edu 128.104.140.158 wisc.edu 128.104.201.97 wisc.edu 128.104.119.180 wisc.edu 144.92.238.12 wisc.edu 144.92.76.40 wisc.edu 144.92.158.32 wisc.edu 128.104.71.108 {:from=>"6.28", :to=>"6.29", :ts=>1388232433, :type=>"cms_version {:from=>nil, :to=>"6.28", :ts=>1377401154, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.23", :ts=>1400791981, :type=>"cms_version"}|{: {:from=>nil, :to=>"6.28", :ts=>1376091762, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.34", :ts=>1425859811, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.9", :ts=>1393243058, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"7.21", :ts=>1382922559, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.0", :ts=>1429258335, :type=>"cms_version"}|{:fr {:from=>"6.28", :to=>"7.28", :ts=>1413397723, :type=>"cms_version
{:from=>nil, :to=>"7.35", :ts=>1432235467, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.0", :ts=>1431101988, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"7.37", :ts=>1432489297, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.0", :ts=>1427575436, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"7.0", :ts=>1429456273, :type=>"cms_version"}|{:fr {:from=>"6.28", :to=>nil, :ts=>1413927709, :type=>"cms_version"}|{: {:from=>"7.14", :to=>"7.23", :ts=>1381889455, :type=>"cms_version {:from=>nil, :to=>"7.34", :ts=>1418823339, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"6.30", :ts=>1391221172, :type=>"cms_version {:from=>"6.28", :to=>"6.33", :ts=>1416013604, :type=>"cms_version {:from=>"6.22", :to=>"6.28", :ts=>1376038838, :type=>"cms_version {:from=>"6.28", :to=>nil, :ts=>1408845913, :type=>"cms_version"}|{:
{:from=>nil, :to=>"6.28", :ts=>1381841118, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.22", :ts=>1381738267, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"7.22", :ts=>1377041236, :type=>"cms_version {:from=>nil, :to=>"7.23", :ts=>1383456736, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"6.33", :ts=>1416013600, :type=>"cms_version {:from=>"7.22", :to=>"7.24", :ts=>1392682484, :type=>"cms_version {:from=>nil, :to=>"7.34", :ts=>1419968835, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.24", :ts=>1391245615, :type=>"cms_version {:from=>nil, :to=>"7.0", :ts=>1434705780, :type=>"cms_version"} {:from=>nil, :to=>"7.0", :ts=>1426219193, :type=>"cms_version"} {:from=>nil, :to=>"drupal", :ts=>1378046810, :type=>"cms"}|{:from=> {:from=>nil, :to=>"6.28", :ts=>1376033958, :type=>"cms_version"}|{: {:from=>nil, :to=>"drupal", :ts=>1412976561, :type=>"cms"}|{:from=> {:from=>nil, :to=>"drupal", :ts=>1413216414, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.23", :ts=>1387086520, :type=>"cms_version"}|{: {:from=>"6.24", :to=>"6.28", :ts=>1381522300, :type=>"cms_version {:from=>nil, :to=>"7.27", :ts=>1413397817, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.24", :ts=>1386088102, :type=>"cms_version {:from=>nil, :to=>"7.20", :ts=>1381430844, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.39", :ts=>1442825017, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.35", :ts=>1440724403, :type=>"cms_version"}|{: {:from=>nil, :to=>"6.28", :ts=>1436745951, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.38", :ts=>1437876087, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.31", :ts=>1430481046, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.0", :ts=>1432489169, :type=>"cms_version"}|{:fr {:from=>"6.28", :to=>"7.28", :ts=>1413397741, :type=>"cms_version {:from=>nil, :to=>"7.22", :ts=>1382042789, :type=>"cms_version"}|{:
{:from=>"6.28", :to=>"6.30", :ts=>1391207398, :type=>"cms_version {:from=>"6.28", :to=>nil, :ts=>1407440647, :type=>"cms_version"}|{: {:from=>nil, :to=>"drupal", :ts=>1413403467, :type=>"cms"}|{:from=>
{:from=>"6.24", :to=>"6.28", :ts=>1383528881, :type=>"cms_version
{:from=>"6.28", :to=>"6.36", :ts=>1437708463, :type=>"cms_version {:from=>"6.24", :to=>"6.28", :ts=>1382632479, :type=>"cms_version {:from=>"6.28", :to=>nil, :ts=>1411996449, :type=>"cms_version"}|{: {:from=>"6.28", :to=>nil, :ts=>1442556755, :type=>"cms_version"} {:from=>nil, :to=>"6.28", :ts=>1376058878, :type=>"cms_version"}|{: {:from=>nil, :to=>"6.28", :ts=>1381651461, :type=>"cms_version"}|{:
{:from=>nil, :to=>"drupal", :ts=>1373591748, :type=>"cms"}|{:from=>
{:from=>nil, :to=>"7.22", :ts=>1382042793, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"6.36", :ts=>1437708303, :type=>"cms_version {:from=>"6.22", :to=>"6.28", :ts=>1378486530, :type=>"cms_version {:from=>"6.30", :to=>"6.36", :ts=>1437708503, :type=>"cms_version {:from=>"6.26", :to=>"6.28", :ts=>1383763820, :type=>"cms_version {:from=>"6.30", :to=>"6.33", :ts=>1413397749, :type=>"cms_version {:from=>"6.15", :to=>"7.38", :ts=>1442533189, :type=>"cms_version {:from=>nil, :to=>"oraclewebcenter", :ts=>1382840772, :type=>"cms
{:from=>nil, :to=>"expressionengine", :ts=>1373344502, :type=>"cm
{:from=>nil, :to=>"google", :ts=>1390712235, :type=>"provider"} {:from=>nil, :to=>"google", :ts=>1401004310, :type=>"provider"}|{:fro {:from=>"7.21", :to=>nil, :ts=>1391229510, :type=>"cms_version"}|{: {:from=>nil, :to=>"google", :ts=>1387587210, :type=>"provider"} {:from=>nil, :to=>"google", :ts=>1388330971, :type=>"provider"} {:from=>nil, :to=>"googlesites", :ts=>1380749954, :type=>"cms"}|{:fr {:from=>nil, :to=>"google", :ts=>1391776884, :type=>"provider"} {:from=>"6.28", :to=>nil, :ts=>1442360059, :type=>"cms_version"}|{: {:from=>nil, :to=>"google", :ts=>1392745739, :type=>"provider"}|{:fro {:from=>"PEER 1", :to=>nil, :ts=>1382650662, :type=>"provider"}|{:f {:from=>nil, :to=>"google", :ts=>1408552145, :type=>"provider"}|{:fro {:from=>nil, :to=>"google", :ts=>1390148088, :type=>"provider"}
{:from=>nil, :to=>"joomla", :ts=>1395384805, :type=>"cms"}
events
Appendix 4 - Acquia Report
id badminton.rso.wisc.edu tcnl.bme.wisc.edu drupal.wisc.edu cls.wisc.edu fwe.wisc.edu keely.molbio.wisc.edu dept.biostat.wisc.edu chembio.chem.wisc.edu epr.chem.wisc.edu brazil.wisc.edu yoon.chem.wisc.edu residents.neurology.wisc.edu keckcenter.chem.wisc.edu csl.cs.wisc.edu wcftr.commarts.wisc.edu bement.molbio.wisc.edu copycenter.chem.wisc.edu pharmacy.wisc.edu manduca.entomology.wisc.edu loci.wisc.edu ictr.wisc.edu materials.chem.wisc.edu mph.wisc.edu software.cae.wisc.edu carla.russell.wisc.edu spanport.lss.wisc.edu silagebreeding.agronomy.wisc.edu flycrispr.molbio.wisc.edu stahl.chem.wisc.edu rotcprojectgo.wisc.edu catalysiscenter.chem.wisc.edu wsc.limnology.wisc.edu energy.wisc.edu wisconsinadrc.wisc.edu blackwell.chem.wisc.edu celticstudies.wisc.edu german.wisc.edu scout.cs.wisc.edu emed.wisc.edu genchem.chem.wisc.edu pgsec.chem.wisc.edu biostat.wisc.edu biophysics.wisc.edu hip.wisc.edu zanni.chem.wisc.edu susnano.chem.wisc.edu keutsch.chem.wisc.edu cmb.wisc.edu comphelp.chem.wisc.edu lacis.wisc.edu chem.wisc.edu cmp.wisc.edu chops.chem.wisc.edu mvp.virology.wisc.edu buildingservices.chem.wisc.edu bocklabs.wisc.edu commarts.wisc.edu physics.wisc.edu gsflc.chem.wisc.edu african.lss.wisc.edu stemcells.wisc.edu african.wisc.edu uwmrrc.wisc.edu jchemed.chem.wisc.edu clsmedtech.wisc.edu slavic.lss.wisc.edu cardiovascular.medicine.wisc.edu forestandwildlifeecology.wisc.edu entomology.wisc.edu russianflagship.wisc.edu csumc.wisc.edu microbes.limnology.wisc.edu perryfreygroup.biochem.wisc.edu painpolicy.wisc.edu fammed.wisc.edu lter.limnology.wisc.edu analytical.chem.wisc.edu localroads.wisc.edu forestlandscape.wisc.edu folklore.wisc.edu cornbreeding.wisc.edu molbio.wisc.edu labs.pathology.wisc.edu urpl.wisc.edu cdh.med.wisc.edu stat.wisc.edu adrc.wisc.edu scout.wisc.edu languages.wisc.edu campagnola.molbio.wisc.edu wcmp.wisc.edu forest.wisc.edu cs.wisc.edu inside.fammed.wisc.edu german.lss.wisc.edu ortho.wisc.edu ohrd.wisc.edu orthorehab.wisc.edu
subdomain badminton.rso tcnl.bme drupal cls fwe keely.molbio dept.biostat chembio.chem epr.chem brazil yoon.chem residents.neurology keckcenter.chem csl.cs wcftr.commarts bement.molbio copycenter.chem pharmacy manduca.entomology loci ictr materials.chem mph software.cae carla.russell spanport.lss silagebreeding.agronomy flycrispr.molbio stahl.chem rotcprojectgo catalysiscenter.chem wsc.limnology energy wisconsinadrc blackwell.chem celticstudies german scout.cs emed genchem.chem pgsec.chem biostat biophysics hip zanni.chem susnano.chem keutsch.chem cmb comphelp.chem lacis chem cmp chops.chem mvp.virology buildingservices.chem bocklabs commarts physics gsflc.chem african.lss stemcells african uwmrrc jchemed.chem clsmedtech slavic.lss cardiovascular.medicine forestandwildlifeecology entomology russianflagship csumc microbes.limnology perryfreygroup.biochem painpolicy fammed lter.limnology analytical.chem localroads forestlandscape folklore cornbreeding molbio labs.pathology urpl cdh.med stat adrc scout languages campagnola.molbio wcmp forest cs inside.fammed german.lss ortho ohrd orthorehab
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal drupal dotnetnuke dotnetnuke dotnetnuke
Appendix 4 - Page 6 of 19 7.0
6.36 7.39
7.39 7.39 7.39 7.0 6.22
6.17 6.37 6.22 6.36 6.37 6.22 6.22 7.0 7.0
6.17
6.36 6.19
6.22 7.33 7.39 7.39 7.39 7.26 7.38 7.39 7.39 7.0 7.0 7.39 7.39 7.0 7.0 7.39 7.33 7.39 7.39 7.39 7.39 7.33 7.39 7.39 7.39 7.39 7.39 7.33 7.0 7.33 7.39 7.39 7.39 7.0 7.39 7.0 7.34 7.39
6.36 6.22 6.30 7.39 7.39 7.39 7.39 7.39 7.39 7.39 7.39 7.33 7.39 7.39 6.35 6.37 6.37 7.39 7.39 6.14 apache apache
apache
iis
iis
iis apache
iis
websrv
php_5.3|platform_dotnet|platform_php php_5.6|platform_dotnet|platform_php mobile|php_5.4|platform_php Pantheon varnish mobile|php_5.4|platform_php|social_embed mobile|php_5.3|platform_php mobile|mollom|php_5.3|platform_php mobile|php_5.4|platform_php php_5.3|platform_dotnet|platform_php mobile|platform_php php_5.3|platform_php mobile|php_5.4|platform_php php_5.3|platform_php|mobile mobile|php_5.4|platform_php platform_dotnet platform_dotnet platform_dotnet
php_5.3|platform_php php_5.3|platform_php
iis iis iis
iis nginx
apache
apache
iis iis
mobile|php_5.3|platform_dotnet|platform_php iis php_5.3|platform_php php_5.4|platform_php php_5.3|platform_php content_embed|php_5.3|platform_php mobile|php_5.3|platform_php|social_embed mobile|php_5.3|platform_php apache php_5.3|platform_php mobile|php_5.4|platform_php mobile|php_5.4|platform_php mobile|mollom|php_5.3|platform_php mobile|php_5.2|platform_php apache php_5.3|platform_php php_5.3|platform_php mobile|php_5.5|platform_php mobile|php_5.3|platform_dotnet|platform_php iis mobile|php_5.3|platform_php|social_embed mobile|php_5.3|platform_php php_5.3|platform_php php_5.3|platform_php mobile|php_5.3|platform_dotnet|platform_php iis mobile|mollom|php_5.3|platform_php mobile|php_5.4|platform_php|social_embed php_5.3|platform_php mobile|php_5.6|platform_dotnet|platform_php iis php_5.3|platform_php mobile|php_5.3|platform_dotnet|platform_php iis php_5.3|platform_php php_5.3|platform_dotnet|platform_php iis mobile|php_5.3|platform_php php_5.4|platform_php|ipv6 php_5.3|platform_php mobile|php_5.4|platform_php mobile mobile|php_5.4|platform_php mobile mobile|mollom|php_5.4|platform_php|social_embed|socia platform_dotnet|platform_php iis php_5.3|platform_php mobile|platform_php nginx php_5.3|platform_php mobile|php_5.2|platform_php|social_media_like php_5.4|platform_php content_embed|php_5.3|platform_php|social_embed php_5.3|platform_php php_5.6|platform_php php_5.2|platform_php php_5.3|platform_php|social_embed|mobile php_5.3|platform_php php_5.2|platform_php
php_5.3|platform_php
features php_5.4|platform_php php_5.4|platform_php|ipv6 mollom platform_dotnet|platform_php php_5.3|platform_php php_5.3|platform_dotnet|platform_php platform_php|mobile php_5.3|platform_php mobile|php_5.3|platform_php mobile|php_5.4|platform_php mobile|php_5.3|platform_php php_5.6|platform_dotnet|platform_php php_5.3|platform_php mobile|php_5.4|platform_php mobile|php_5.3|platform_php php_5.3|platform_dotnet|platform_php php_5.3|platform_php mobile|mollom mobile content_embed Pantheon varnish php_5.3|platform_php
cms_veprovider 7.39 7.37 7.39
1985-09-30 00:00:00 -0400 ortho.wisc.edu
1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 home | uw s cornbreeding.wisc.edu 1985-09-30 00:00:00 -0400 overview | fly 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 rotc project g 1985-09-30 00:00:00 -0400 welcome! | c 1985-09-30 00:00:00 -0400 water sustain 1985-09-30 00:00:00 -0400 home | wisco 1985-09-30 00:00:00 -0400 welcome to twww.adrc.wisc.edu 1985-09-30 00:00:00 -0400 home | black 1985-09-30 00:00:00 -0400 welcome! | c 1985-09-30 00:00:00 -0400 home | depa 1985-09-30 00:00:00 -0400 internet scouscout.wisc.edu 1985-09-30 00:00:00 -0400 mission | em 1985-09-30 00:00:00 -0400 general chemwww.chem.wisc.edu 1985-09-30 00:00:00 -0400 pgsec | uw mwww.chem.wisc.edu 1985-09-30 00:00:00 -0400 biostatistics 1985-09-30 00:00:00 -0400 biophysics 1985-09-30 00:00:00 -0400 health innov 1985-09-30 00:00:00 -0400 zanni group 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 the keutsch 1985-09-30 00:00:00 -0400 cmb 1985-09-30 00:00:00 -0400 comphelp | d 1985-09-30 00:00:00 -0400 home | lacis 1985-09-30 00:00:00 -0400 home | uw m 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 welcome | ch 1985-09-30 00:00:00 -0400 madison viro 1985-09-30 00:00:00 -0400 building servwww.chem.wisc.edu 1985-09-30 00:00:00 -0400 r. m. bock la 1985-09-30 00:00:00 -0400 welcome | co 1985-09-30 00:00:00 -0400 welcome | de 1985-09-30 00:00:00 -0400 home | gsflc 1985-09-30 00:00:00 -0400 welcome | afafrican.wisc.edu 1985-09-30 00:00:00 -0400 welcome to s 1985-09-30 00:00:00 -0400 welcome | af welcome to u 1985-09-30 00:00:00 -0400 chemical edu 1985-09-30 00:00:00 -0400 clinical labor www.pathology.wisc.edu 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 uw cardiovaswww.medicine.wisc.edu 1985-09-30 00:00:00 -0400 home | fores 1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 welcome | ru 1985-09-30 00:00:00 -0400 center for the 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 frey lab | bio biochem.wisc.edu 1985-09-30 00:00:00 -0400 home | pain 1985-09-30 00:00:00 -0400 uw family me 1985-09-30 00:00:00 -0400 welcome to n 1985-09-30 00:00:00 -0400 site off-line | 1985-09-30 00:00:00 -0400 local roads c 1985-09-30 00:00:00 -0400 home | fores 1985-09-30 00:00:00 -0400 home | the fo 1985-09-30 00:00:00 -0400 home | uw s 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 research lab www.pathology.wisc.edu home | urban 1985-09-30 00:00:00 -0400 collaborativeictr.wisc.edu 1985-09-30 00:00:00 -0400 home | depa 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 internet scou welcome to l 1985-09-30 00:00:00 -0400 research ove 1985-09-30 00:00:00 -0400 welcome to twww.adrc.wisc.edu 1985-09-30 00:00:00 -0400 home | fores 1985-09-30 00:00:00 -0400 uw-madison 1985-09-30 00:00:00 -0400 insidedfmch 1985-09-30 00:00:00 -0400 home | depagerman.wisc.edu
domain_created title redirect 1985-09-30 00:00:00 -0400 welcome | de 1985-09-30 00:00:00 -0400 home | tcnl 1985-09-30 00:00:00 -0400 drupal.wisc.e 1985-09-30 00:00:00 -0400 graduate cerwww.pathology.wisc.edu 1985-09-30 00:00:00 -0400 home | fores 1985-09-30 00:00:00 -0400 research ove 1985-09-30 00:00:00 -0400 home | biom 1985-09-30 00:00:00 -0400 welcome! | c electron para 1985-09-30 00:00:00 -0400 welcome to t 1985-09-30 00:00:00 -0400 yoon researc department o 1985-09-30 00:00:00 -0400 home | keck 1985-09-30 00:00:00 -0400 computer sy 1985-09-30 00:00:00 -0400 welcome | w 1985-09-30 00:00:00 -0400 bement lab | 1985-09-30 00:00:00 -0400 chemistry fa 1985-09-30 00:00:00 -0400 school of ph 1985-09-30 00:00:00 -0400 department o 1985-09-30 00:00:00 -0400 loci | laborato 1985-09-30 00:00:00 -0400 uw ictr, your 1985-09-30 00:00:00 -0400 materials ch mph home |
dns_provid ip wisc.edu 128.104.160.19 wisc.edu 128.104.201.97 wisc.edu 128.104.71.104 144.92.28.35 wisc.edu 144.92.199.125 wisc.edu 144.92.238.12 128.104.206.137 wisc.edu 128.104.71.108 wisc.edu 128.104.71.108 wisc.edu 128.104.23.171 wisc.edu 128.104.71.108 wisc.edu 128.104.205.125 wisc.edu 128.104.71.108 wisc.edu 128.105.7.42 wisc.edu 144.92.226.67 wisc.edu 144.92.238.12 wisc.edu 128.104.71.108 wisc.edu 128.104.115.232 wisc.edu 144.92.198.11 wisc.edu 144.92.48.140 wisc.edu 104.130.103.106 wisc.edu 128.104.71.108 wisc.edu 144.92.239.161 144.92.13.161 144.92.198.158 wisc.edu 144.92.115.213 wisc.edu 128.104.81.148 wisc.edu 144.92.238.12 wisc.edu 128.104.71.108 wisc.edu 128.104.23.171 wisc.edu 128.104.71.108 wisc.edu 144.92.62.194 wisc.edu 144.92.98.187 wisc.edu 144.92.76.40 wisc.edu 128.104.71.108 wisc.edu 144.92.158.32 wisc.edu 144.92.158.32 wisc.edu 144.92.170.202 wisc.edu 144.92.76.40 wisc.edu 128.104.70.5 wisc.edu 128.104.70.5 wisc.edu 144.92.73.51 wisc.edu 144.92.238.12 wisc.edu 128.104.140.159 wisc.edu 128.104.71.108 wisc.edu 128.104.71.170 wisc.edu 128.104.71.108 wisc.edu 144.92.238.12 wisc.edu 128.104.71.108 wisc.edu 128.104.23.171 wisc.edu 128.104.70.5 wisc.edu 144.92.28.40 wisc.edu 128.104.71.108 wisc.edu 144.92.238.12 wisc.edu 128.104.70.5 wisc.edu 144.92.238.12 wisc.edu 144.92.226.67 wisc.edu 128.104.160.19 wisc.edu 128.104.71.108 wisc.edu 144.92.158.32 wisc.edu 128.104.81.230 wisc.edu 144.92.158.32 wisc.edu 128.104.81.105 wisc.edu 128.104.240.17 144.92.28.35 wisc.edu 144.92.115.213 144.92.76.40 wisc.edu 144.92.199.125 wisc.edu 144.92.198.186 wisc.edu 144.92.158.32 wisc.edu 144.92.115.213 wisc.edu 144.92.62.194 wisc.edu 128.104.119.180 wisc.edu 128.104.208.69 wisc.edu 144.92.41.18 wisc.edu 144.92.62.194 wisc.edu 128.104.70.253 wisc.edu 128.104.80.28 wisc.edu 144.92.199.125 wisc.edu 144.92.115.213 wisc.edu 128.104.81.148 wisc.edu 144.92.238.12 wisc.edu 144.92.28.35 wisc.edu 144.92.158.32 wisc.edu 104.130.103.106 wisc.edu 128.105.7.14 wisc.edu 144.92.76.40 wisc.edu 144.92.170.202 wisc.edu 144.92.158.32 wisc.edu 144.92.238.12 wisc.edu 144.92.76.40 wisc.edu 144.92.199.125 wisc.edu 128.105.7.31 wisc.edu 144.92.41.18 wisc.edu 144.92.158.32 wisc.edu 144.92.106.128 wisc.edu 144.92.5.157 wisc.edu 144.92.106.128 {:from=>nil, :to=>"drupal", :ts=>1382868681, :type=>"cms"} {:from=>"6.28", :to=>"6.30", :ts=>1391197784, :type=>"cms_version {:from=>"6.22", :to=>"6.28", :ts=>1382544277, :type=>"cms_version {:from=>"6.28", :to=>nil, :ts=>1419968385, :type=>"cms_version"} {:from=>nil, :to=>"7.0", :ts=>1442358499, :type=>"cms_version"}
{:from=>"6.18", :to=>nil, :ts=>1387690872, :type=>"cms_version"}|{: {:from=>nil, :to=>"drupal", :ts=>1375998755, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.0", :ts=>1441408048, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"Pantheon", :ts=>1416013478, :type=>"provider"} {:from=>nil, :to=>"7.32", :ts=>1419350468, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.21", :ts=>1389405161, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.28", :ts=>1403601447, :type=>"cms_version {:from=>nil, :to=>"7.36", :ts=>1428907594, :type=>"cms_version"}|{:
{:from=>nil, :to=>"6.28", :ts=>1375800385, :type=>"cms_version"}|{: {:from=>"6.24", :to=>"6.28", :ts=>1382632465, :type=>"cms_version
{:from=>nil, :to=>"6.28", :ts=>1391240006, :type=>"cms_version"}|{:
{:from=>"6.30", :to=>"6.31", :ts=>1400790040, :type=>"cms_version {:from=>"6.24", :to=>"6.28", :ts=>1383983593, :type=>"cms_version {:from=>nil, :to=>"drupal", :ts=>1374462505, :type=>"cms"}|{:from=> {:from=>nil, :to=>"drupal", :ts=>1423031173, :type=>"cms"} {:from=>nil, :to=>"6.25", :ts=>1376113636, :type=>"cms_version"}|{: {:from=>"6.28", :to=>nil, :ts=>1419968377, :type=>"cms_version"}
{:from=>"6.28", :to=>"6.30", :ts=>1391229265, :type=>"cms_version
{:from=>nil, :to=>"7.9", :ts=>1393633427, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"7.34", :ts=>1420004577, :type=>"cms_version"}|{: {:from=>"7.27", :to=>"7.31", :ts=>1411982323, :type=>"cms_version {:from=>"6.28", :to=>"7.28", :ts=>1413397689, :type=>"cms_version {:from=>nil, :to=>"6.17", :ts=>1380437483, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.32", :ts=>1413918834, :type=>"cms_version {:from=>nil, :to=>"drupal", :ts=>1393805981, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.32", :ts=>1416224510, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.23", :ts=>1381449193, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.0", :ts=>1441736999, :type=>"cms_version"} {:from=>"7.22", :to=>"7.28", :ts=>1408801781, :type=>"cms_version {:from=>"6.25", :to=>"7.21", :ts=>1384883166, :type=>"cms_version {:from=>nil, :to=>"7.0", :ts=>1422853571, :type=>"cms_version"} {:from=>nil, :to=>"drupal", :ts=>1386093520, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.31", :ts=>1408885566, :type=>"cms_version"}|{: {:from=>"7.9", :to=>"7.33", :ts=>1419968366, :type=>"cms_version" {:from=>nil, :to=>"drupal", :ts=>1374059850, :type=>"cms"}|{:from=> {:from=>nil, :to=>"6.28", :ts=>1390860933, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.22", :ts=>1381522700, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.28", :ts=>1400790103, :type=>"cms_version {:from=>"7.9", :to=>"7.33", :ts=>1419968383, :type=>"cms_version" {:from=>"7.22", :to=>"7.28", :ts=>1400790101, :type=>"cms_version {:from=>"6.28", :to=>"6.29", :ts=>1389604174, :type=>"cms_version {:from=>"7.21", :to=>"7.24", :ts=>1391247465, :type=>"cms_version {:from=>nil, :to=>"7.23", :ts=>1391544577, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"7.28", :ts=>1409260704, :type=>"cms_version {:from=>nil, :to=>"7.9", :ts=>1403567301, :type=>"cms_version"}|{:fr {:from=>"6.28", :to=>nil, :ts=>1416013522, :type=>"cms_version"}|{: {:from=>"6.18", :to=>"6.22", :ts=>1387633097, :type=>"cms_version {:from=>"7.22", :to=>"7.23", :ts=>1380872126, :type=>"cms_version {:from=>"6.26", :to=>"7.23", :ts=>1382181815, :type=>"cms_version {:from=>"6.28", :to=>"7.28", :ts=>1406351274, :type=>"cms_version {:from=>nil, :to=>"Amazon AWS", :ts=>1373759661, :type=>"provid {:from=>"7.13", :to=>"7.34", :ts=>1419968380, :type=>"cms_version {:from=>nil, :to=>"drupal", :ts=>1410449483, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.34", :ts=>1430480816, :type=>"cms_version"}|{: {:from=>"drupal", :to=>nil, :ts=>1389027403, :type=>"cms"}|{:from=> {:from=>nil, :to=>"drupal", :ts=>1382252583, :type=>"cms"}
{:from=>"6.24", :to=>"6.28", :ts=>1384239045, :type=>"cms_version
events {:from=>nil, :to=>"7.23", :ts=>1391748597, :type=>"cms_version"}|{: {:from=>nil, :to=>"6.28", :ts=>1376114548, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.24", :ts=>1400717629, :type=>"cms_version {:from=>nil, :to=>"drupal", :ts=>1391544578, :type=>"cms"} {:from=>"6.28", :to=>"6.29", :ts=>1389583402, :type=>"cms_version {:from=>"6.18", :to=>"6.22", :ts=>1376116867, :type=>"cms_version {:from=>nil, :to=>"6.30", :ts=>1393965994, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"6.33", :ts=>1416013553, :type=>"cms_version {:from=>nil, :to=>"7.39", :ts=>1442825037, :type=>"cms_version"}|{: {:from=>nil, :to=>"drupal", :ts=>1373759647, :type=>"cms"}|{:from=> {:from=>nil, :to=>"7.34", :ts=>1422145838, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.39", :ts=>1443254447, :type=>"cms_version"}|{: {:from=>"6.28", :to=>"7.28", :ts=>1407396432, :type=>"cms_version {:from=>"7.22", :to=>"7.23", :ts=>1382042809, :type=>"cms_version {:from=>nil, :to=>"7.23", :ts=>1384858862, :type=>"cms_version"}|{: {:from=>nil, :to=>"7.9", :ts=>1383073313, :type=>"cms_version"}|{:fr {:from=>nil, :to=>"7.32", :ts=>1416142052, :type=>"cms_version"}|{: {:from=>"7.22", :to=>"7.24", :ts=>1391113700, :type=>"cms_version {:from=>"6.28", :to=>"6.30", :ts=>1391249263, :type=>"cms_version {:from=>"6.30", :to=>"6.36", :ts=>1437707963, :type=>"cms_version {:from=>"6.28", :to=>"6.29", :ts=>1391221241, :type=>"cms_version {:from=>"6.28", :to=>"6.33", :ts=>1416013560, :type=>"cms_version {:from=>nil, :to=>"7.39", :ts=>1442826479, :type=>"cms_version"}|{:
Appendix 4 - Acquia Report
id subdomain root wiki.doit.wisc.edu wiki.doit wisc win.wisc.edu win wisc theatre.wisc.edu theatre wisc qmhdb.commarts.wisc.edu qmhdb.commarts wisc chronicle.com.ezproxy.library.wisc.edu chronicle.com.ezproxy.library wisc infantmentalhealth.psychiatry.wisc.edu infantmentalhealth.psychiatry wisc faculty.history.wisc.edu faculty.history wisc historical.library.wisc.edu historical.library wisc humanitiesportal.wisc.edu humanitiesportal wisc middleware.doit.wisc.edu middleware.doit wisc research.son.wisc.edu research.son wisc buckychallenge.wisc.edu buckychallenge wisc wiki.humonc.wisc.edu wiki.humonc wisc biocore.wisc.edu biocore wisc secure.bus.wisc.edu secure.bus wisc trnrqst.isis.wisc.edu trnrqst.isis wisc pnas.org.ezproxy.library.wisc.edu pnas.org.ezproxy.library wisc historicalhumanities.wisc.edu historicalhumanities wisc asap.genetics.wisc.edu asap.genetics wisc ponderosa.nmrfam.wisc.edu ponderosa.nmrfam wisc depot.library.wisc.edu depot.library wisc ppsg.medicine.wisc.edu ppsg.medicine wisc medhist.wisc.edu medhist wisc handbook.education.wisc.edu handbook.education wisc webstreamer.doit.wisc.edu webstreamer.doit wisc d2p.wisc.edu d2p wisc netmigration.wisc.edu netmigration wisc rcr.gradsch.wisc.edu rcr.gradsch wisc healthsystems.engr.wisc.edu healthsystems.engr wisc caravan.astro.wisc.edu caravan.astro wisc keck.bioimaging.wisc.edu keck.bioimaging wisc wipod.pediatrics.wisc.edu wipod.pediatrics wisc greeklife.wisc.edu greeklife wisc hkn.slc.engr.wisc.edu hkn.slc.engr wisc baja.slc.engr.wisc.edu baja.slc.engr wisc humanproteomics.wisc.edu humanproteomics wisc ems.education.wisc.edu ems.education wisc sethares.engr.wisc.edu sethares.engr wisc aurora.meteor.wisc.edu aurora.meteor wisc dryice.ssec.wisc.edu dryice.ssec wisc sohe.ems.wisc.edu sohe.ems wisc m.accessmedicine.com.ezproxy.library.wisc.e m.accessmedicine.com.ezproxy.librawisc intra.pathology.wisc.edu intra.pathology wisc ime.med.wisc.edu ime.med wisc campfin.polisci.wisc.edu campfin.polisci wisc mcardle.oncology.wisc.edu mcardle.oncology wisc apw.polisci.wisc.edu apw.polisci wisc ayomembaca.wisc.edu ayomembaca wisc aging.wisc.edu aging wisc fountaincam.engr.wisc.edu fountaincam.engr wisc vnweb.hwwilsonweb.com.ezproxy.library.wisc vnweb.hwwilsonweb.com.ezproxy.lib wisc robotics.engr.wisc.edu robotics.engr wisc artsinstitute.wisc.edu artsinstitute wisc www3.interscience.wiley.com.ezproxy.library.wwww3.interscience.wiley.com.ezprox wisc wisdm.doit.wisc.edu wisdm.doit wisc wiscel-calendar.cae.wisc.edu wiscel-calendar.cae wisc calvin.biotech.wisc.edu calvin.biotech wisc onlinelibrary.wiley.com.ezproxy.library.wisc.edonlinelibrary.wiley.com.ezproxy.librarwisc ara.wipac.wisc.edu ara.wipac wisc bioinfo.bact.wisc.edu bioinfo.bact wisc mendota.english.wisc.edu mendota.english wisc southasiaconference.wisc.edu southasiaconference wisc alumni.polisci.wisc.edu alumni.polisci wisc uwpress.wisc.edu uwpress wisc wiseli.engr.wisc.edu wiseli.engr wisc sbel.wisc.edu sbel wisc zoology.wisc.edu zoology wisc eyephoto.ophth.wisc.edu eyephoto.ophth wisc ecow2.engr.wisc.edu ecow2.engr wisc wri.wisc.edu wri wisc ophth.wisc.edu ophth wisc carroll.molbio.wisc.edu carroll.molbio wisc cew.wisc.edu cew wisc wwwtest.womenshealth.wisc.edu wwwtest.womenshealth wisc inquire.bus.wisc.edu inquire.bus wisc lists.wisc.edu lists wisc research3.bus.wisc.edu research3.bus wisc lists.bmrb.wisc.edu lists.bmrb wisc cdp.wisc.edu cdp wisc agwx.soils.wisc.edu agwx.soils wisc econ.wisc.edu econ wisc innovation.wisc.edu innovation wisc contest.cs.wisc.edu contest.cs wisc admin.engr.wisc.edu admin.engr wisc neurosurg.wisc.edu neurosurg wisc aiche.slc.engr.wisc.edu aiche.slc.engr wisc rhinelander.ars.wisc.edu rhinelander.ars wisc dairyforage.ars.wisc.edu dairyforage.ars wisc uw.physics.wisc.edu uw.physics wisc wisp11.physics.wisc.edu wisp11.physics wisc plasma.wisc.edu plasma wisc psl.wisc.edu psl wisc mail.aims.wisc.edu mail.aims wisc hsx.wisc.edu hsx wisc wiki.icecube.wisc.edu wiki.icecube wisc internal.icecube.wisc.edu internal.icecube wisc intranet.genetics.wisc.edu intranet.genetics wisc photos.uc.wisc.edu photos.uc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms confluence angularjs akismet akismet Media Tem
cms_veprovider
features
Appendix 4 - Page 7 of 19
apache apache apache apache apache nginx apache iis iis apache iis apache apache apache iis apache apache apache apache iis iis apache apache apache iis apache iis apache iis iis apache iis
apache apache iis apache apache apache apache apache apache apache iis
apache
websrv
iis
platform_dotnet content_embed mobile|ipv6 content_embed|html5|mobile php_5.4|platform_php|ipv6 platform_dotnet ipv6 php_5.3|platform_php php_5.3|platform_php ipv6
php_5.3|platform_php platform_ruby
ipv6 php_5.4|platform_php platform_dotnet ipv6
iis iis
html5|platform_dotnet|social_embed
html5|mobile|platform_dotnet iis php_5.5|platform_php social_embed php_5.4|platform_php|ipv6 mobile|php_5.4|platform_php|social_embed|social_media platform_dotnet iis platform_dotnet iis ipv6 platform_dotnet mobile|php_5.3|platform_php|ipv6 platform_dotnet iis platform_dotnet iis platform_dotnet iis mobile|platform_dotnet iis
mobile|platform_ruby html5|mobile
ipv6
mobile ipv6 html5|mobile mobile|platform_ruby
ipv6 platform_dotnet mobile|platform_ruby platform_dotnet mobile|platform_java platform_dotnet platform_dotnet php_5.5|platform_php platform_dotnet php_5.4|platform_php
mobile|ipv6 ipv6 platform_dotnet platform_dotnet ipv6
ipv6 php_5.3|platform_php platform_dotnet
platform_dotnet platform_dotnet html5|mobile php_5.3|platform_dotnet|platform_php
platform_ruby
php_5.5|platform_php
mobile|platform_ruby
platform_dotnet
mobile
platform_dotnet platform_dotnet
html5|mobile|php_5.3|platform_php
mobile
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created
title
coeadmin.engr.wisc.edu email.neurosurgery.wisc.edu
bus.wisc.edu
patron.library.wisc.edu
patron.library.wisc.edu wayf.wisconsin.edu
www.med.wisc.edu
patron.library.wisc.edu
ieee.slc.engr.wisc.edu
www.pediatrics.wisc.edu
patron.library.wisc.edu
www.doit.wisc.edu
www.library.wisc.edu
redirect
dns_provid ip wisc.edu 144.92.74.226 wisc.edu 208.83.125.253 wisc.edu 70.32.98.213 wisc.edu 144.92.226.95 128.104.1.195 wisc.edu 144.92.177.178 wisc.edu 128.104.54.31 wisc.edu 128.104.1.195 wisc.edu 128.104.1.215 wisc.edu 128.104.80.153 wisc.edu 144.92.223.14 wisc.edu 144.92.9.53 wisc.edu 144.92.219.38 wisc.edu 144.92.115.213 wisc.edu 144.92.212.18 144.92.9.95 wisc.edu 128.104.46.219 wisc.edu 144.92.9.17 wisc.edu 144.92.136.13 wisc.edu 144.92.4.197 wisc.edu 144.92.11.124 wisc.edu 144.92.76.40 wisc.edu 128.104.80.165 wisc.edu 144.92.146.69 wisc.edu 144.92.9.153 wisc.edu 144.92.9.17 wisc.edu 144.92.122.50 wisc.edu 128.104.147.161 wisc.edu 128.104.201.96 wisc.edu 144.92.110.160 wisc.edu 128.104.220.84 wisc.edu 144.92.221.86 wisc.edu 144.92.9.17 wisc.edu 128.104.201.70 wisc.edu 128.104.201.70 144.92.81.205 wisc.edu 144.92.104.126 wisc.edu 128.104.201.96 wisc.edu 144.92.130.152 wisc.edu 128.104.108.105 wisc.edu 144.92.104.126 wisc.edu 128.104.46.219 wisc.edu 144.92.28.36 wisc.edu 144.92.154.150 wisc.edu 128.104.89.251 wisc.edu 128.104.81.186 wisc.edu 144.92.158.36 wisc.edu 128.104.23.170 wisc.edu 144.92.62.126 wisc.edu 128.104.181.37 wisc.edu 128.104.46.200 wisc.edu 128.104.201.59 wisc.edu 128.104.80.92 wisc.edu 128.104.46.219 wisc.edu 144.92.197.201 wisc.edu 128.104.201.49 wisc.edu 144.92.52.86 wisc.edu 128.104.46.219 wisc.edu 128.104.255.62 wisc.edu 144.92.239.46 wisc.edu 128.104.96.81 wisc.edu 128.104.23.170 wisc.edu 144.92.158.35 wisc.edu 128.104.81.146 wisc.edu 128.104.201.96 wisc.edu 128.104.201.71 wisc.edu 128.104.81.186 wisc.edu 144.92.148.200 wisc.edu 128.104.201.96 wisc.edu 144.92.44.226 wisc.edu 128.104.254.80 wisc.edu 144.92.238.12 wisc.edu 144.92.160.80 wisc.edu 128.104.54.10 wisc.edu 144.92.201.150 wisc.edu 144.92.9.49 wisc.edu 144.92.212.43 wisc.edu 144.92.167.220 wisc.edu 144.92.93.157 wisc.edu 144.92.93.171 wisc.edu 144.92.190.47 wisc.edu 128.104.201.71 wisc.edu 128.105.7.9 wisc.edu 128.104.201.96 wisc.edu 144.92.80.14 wisc.edu 128.104.201.107 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 128.104.160.19 wisc.edu 128.104.164.41 wisc.edu 128.104.201.94 wisc.edu 144.92.224.3 wisc.edu 128.104.155.52 wisc.edu 128.104.201.94 wisc.edu 128.104.255.40 wisc.edu 128.104.255.38 wisc.edu 144.92.93.172 wisc.edu 144.92.9.200 {:from=>nil, :to=>"wordpress", :ts=>1406522217, :type=>"cms"}|{:fro
{:from=>"wordpress", :to=>nil, :ts=>1412808040, :type=>"cms"}
{:from=>"moodle", :to=>nil, :ts=>1387394376, :type=>"cms"}
{:from=>"sitefinity", :to=>nil, :ts=>1406522391, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1407410791, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1426867487, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1406343732, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1406754306, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1415250986, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1425394835, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1409455888, :type=>"cms"}|{:fro {:from=>nil, :to=>"opentext_wsm", :ts=>1401528508, :type=>"cms"}
events {:from=>nil, :to=>"confluence", :ts=>1376033832, :type=>"cms"} {:from=>nil, :to=>"angularjs", :ts=>1439445600, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1373994146, :type=>"cms"}|{:fro {:from=>nil, :to=>"wordpress", :ts=>1392415884, :type=>"cms"}|{:fro
Appendix 4 - Acquia Report
id subdomain root nso.engr.wisc.edu nso.engr wisc ysa.engr.wisc.edu ysa.engr wisc trace.wisc.edu trace wisc nms.doit.wisc.edu nms.doit wisc invest.bus.wisc.edu invest.bus wisc cpd.fpm.wisc.edu cpd.fpm wisc moc.wisc.edu moc wisc jobs.wisc.edu jobs wisc seagrant.wisc.edu seagrant wisc apps.bus.wisc.edu apps.bus wisc jobboard.biochem.wisc.edu jobboard.biochem wisc itsc.aae.wisc.edu itsc.aae wisc kb.wisc.edu kb wisc garage.physics.wisc.edu garage.physics wisc uwcifs.wisc.edu uwcifs wisc amanda.wisc.edu amanda wisc southernpartnership.wisc.edu southernpartnership wisc trans.wisc.edu trans wisc restraintsgrid.bmrb.wisc.edu restraintsgrid.bmrb wisc pieper.engr.wisc.edu pieper.engr wisc mywcer.wisc.edu mywcer wisc uwnmbl.engr.wisc.edu uwnmbl.engr wisc artisthelp.wisc.edu artisthelp wisc mynetid.wisc.edu mynetid wisc ppd.psychiatry.wisc.edu ppd.psychiatry wisc elibrary.worldbank.org.ezproxy.library.wisc.ed elibrary.worldbank.org.ezproxy.librarywisc ls.wisc.edu ls wisc gubner.ece.wisc.edu gubner.ece wisc lafollette.wisc.edu lafollette wisc databases.library.wisc.edu databases.library wisc speedy.meteor.wisc.edu speedy.meteor wisc ecs.library.wisc.edu ecs.library wisc neutrino.physics.wisc.edu neutrino.physics wisc ssc.wisc.edu ssc wisc biologyofaging.wisc.edu biologyofaging wisc ictrcap.med.wisc.edu ictrcap.med wisc mail.obgyn.wisc.edu mail.obgyn wisc audiology.rso.wisc.edu audiology.rso wisc apps.music.wisc.edu apps.music wisc condor-wiki.cs.wisc.edu condor-wiki.cs wisc src.wisc.edu src wisc transportal.cee.wisc.edu transportal.cee wisc npp.wisc.edu npp wisc ems.union.wisc.edu ems.union wisc digital.library.wisc.edu.ezproxy.library.wisc.ed digital.library.wisc.edu.ezproxy.librarywisc mees.engr.wisc.edu mees.engr wisc blogs.nelson.wisc.edu blogs.nelson wisc water.wisc.edu water wisc mcb.wisc.edu mcb wisc uniontheater.wisc.edu uniontheater wisc corundum.education.wisc.edu corundum.education wisc vdt.cs.wisc.edu vdt.cs wisc newton.nmrfam.wisc.edu newton.nmrfam wisc slhstream.ad.slh.wisc.edu slhstream.ad.slh wisc daadcenter.wisc.edu daadcenter wisc spaceplace.wisc.edu spaceplace wisc gsa.bme.wisc.edu gsa.bme wisc noc.hep.wisc.edu noc.hep wisc my.gradsch.wisc.edu my.gradsch wisc bmolchem.wisc.edu bmolchem wisc uwim.recsports.wisc.edu uwim.recsports wisc lterquery.limnology.wisc.edu lterquery.limnology wisc hexagon.physics.wisc.edu hexagon.physics wisc hsl.wisc.edu hsl wisc pubs.wisc.edu pubs wisc lakesat.ssec.wisc.edu lakesat.ssec wisc video.engr.wisc.edu video.engr wisc uwamrc.ssec.wisc.edu uwamrc.ssec wisc apps.cfli.wisc.edu apps.cfli wisc radiology.wisc.edu radiology wisc careers.education.wisc.edu careers.education wisc iris.ophth.wisc.edu iris.ophth wisc fprcportal.ophth.wisc.edu fprcportal.ophth wisc vision.wisc.edu vision wisc eceserv0.ece.wisc.edu eceserv0.ece wisc postcards.vip.wisc.edu postcards.vip wisc soe-b5.ad.education.wisc.edu soe-b5.ad.education wisc cfk.education.wisc.edu cfk.education wisc photos.sohe.wisc.edu photos.sohe wisc admin.experts.wisc.edu admin.experts wisc data.uwcc.wisc.edu data.uwcc wisc apps.google.wisc.edu apps.google wisc law.wisc.edu law wisc enlight.engr.wisc.edu enlight.engr wisc ebm.wisc.edu ebm wisc union.ems.wisc.edu union.ems wisc uw-food-irradiation.engr.wisc.edu uw-food-irradiation.engr wisc wisenet.engr.wisc.edu wisenet.engr wisc digipub.library.wisc.edu digipub.library wisc smad.journalism.wisc.edu smad.journalism wisc vep.cs.wisc.edu vep.cs wisc reading.pediatrics.wisc.edu reading.pediatrics wisc education.ems.wisc.edu education.ems wisc afroamericanstudies.wisc.edu afroamericanstudies wisc mideast.wisc.edu mideast wisc search.library.wisc.edu search.library wisc ece.wisc.edu ece wisc wx.physics.wisc.edu wx.physics wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 8 of 19 iis
platform_dotnet
php_5.2|platform_php html5|mobile
php_5.4|platform_php|ipv6 ipv6 php_5.3|platform_php
html5|mobile|platform_dotnet platform_ruby platform_java platform_dotnet mobile|php_5.5|platform_php
iis iis
platform_dotnet platform_dotnet mobile|platform_ruby ipv6 ipv6
mobile
iis iis
iis google
iis apache
title
mcburney.wisc.edu
nelson.wisc.edu
htcondor-wiki.cs.wisc.edu
patron.library.wisc.edu
wipac.wisc.edu
www2.biochem.wisc.edu
redirect nso.wisc.edu
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
www.engr.wisc.edu
www.pediatrics.wisc.edu
drive.google.com
eop.education.wisc.edu photos.limnology.wisc.edu login.wisc.edu
www.engr.wisc.edu
ebling.library.wisc.edu
1985-09-30 00:00:00 -0400 welcome to nsecure.limnology.wisc.edu
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created
iis oracle_app_se
apache iis
iis
apache
iis iis
platform_dotnet platform_dotnet ipv6
iis
content_embed|platform_dotnet
mobile|php_5.6|platform_php|social_embed platform_dotnet
mobile
iis
iis apache iis
iis
iis
iis
platform_dotnet
platform_dotnet
php_5.4|platform_php php_5.5|platform_php platform_dotnet
ipv6 platform_dotnet php_5.4|platform_php|ipv6 platform_dotnet mobile platform_dotnet mobile|platform_ruby content_embed ipv6 platform_dotnet mobile|platform_ruby
iis
iis
iis coyote iis
platform_dotnet mobile|platform_dotnet mobile mobile|ipv6 content_embed|platform_dotnet html5|mobile platform_dotnet ipv6
iis iis
html5|platform_dotnet
websrv
content_embed|platform_dotnet
features php_5.4|platform_php|social_embed|ipv6 ipv6 php_4|platform_php
platform_dotnet CloudFlare cloudflare mobile platform_dotnet google php_5.3|platform_php ipv6 platform_dotnet platform_dotnet ipv6 ipv6
cms_veprovider
dns_provid ip wisc.edu 128.104.201.71 wisc.edu 128.104.201.59 wisc.edu 128.104.192.125 wisc.edu 128.104.81.58 wisc.edu 144.92.212.43 wisc.edu 144.92.9.17 wisc.edu 128.104.81.186 wisc.edu 144.92.9.17 wisc.edu 144.92.44.218 wisc.edu 144.92.212.18 128.104.116.80 wisc.edu 144.92.122.14 wisc.edu 128.104.22.180 wisc.edu 128.104.160.19 wisc.edu 128.104.23.170 wisc.edu 128.104.255.62 wisc.edu 128.104.81.186 wisc.edu 128.104.201.94 wisc.edu 144.92.217.20 wisc.edu 128.104.201.59 wisc.edu 144.92.160.59 wisc.edu 128.104.201.59 wisc.edu 128.104.155.42 wisc.edu 128.104.1.210 wisc.edu 144.92.177.178 wisc.edu 128.104.46.219 wisc.edu 128.104.88.40 wisc.edu 128.104.201.100 wisc.edu 144.92.45.23 wisc.edu 128.104.46.109 wisc.edu 144.92.130.140 wisc.edu 128.104.81.76 wisc.edu 128.104.160.19 wisc.edu 144.92.190.47 wisc.edu 144.92.62.126 wisc.edu 144.92.50.142 wisc.edu 144.92.66.241 144.92.74.0 wisc.edu 128.104.81.40 wisc.edu 128.105.7.112 wisc.edu 144.92.249.226 wisc.edu 128.104.128.110 wisc.edu 128.104.220.85 144.92.213.96 wisc.edu 128.104.46.200 wisc.edu 144.92.225.235 wisc.edu 144.92.235.112 wisc.edu 144.92.44.228 wisc.edu 128.104.81.77 wisc.edu 128.104.80.31 wisc.edu 144.92.146.16 wisc.edu 128.105.7.81 wisc.edu 144.92.4.144 wisc.edu 144.92.248.143 wisc.edu 128.104.23.170 wisc.edu 144.92.179.14 wisc.edu 128.104.201.60 wisc.edu 128.104.28.225 wisc.edu 128.104.147.177 wisc.edu 128.104.81.186 wisc.edu 128.104.31.118 144.92.62.252 wisc.edu 128.104.162.54 wisc.edu 144.92.50.151 wisc.edu 128.104.81.41 wisc.edu 128.104.108.105 wisc.edu 128.104.201.96 wisc.edu 128.104.109.32 wisc.edu 128.104.81.79 wisc.edu 128.104.228.50 wisc.edu 144.92.146.188 wisc.edu 144.92.148.130 wisc.edu 144.92.148.131 wisc.edu 144.92.9.62 wisc.edu 128.104.201.59 wisc.edu 128.104.81.65 wisc.edu 144.92.146.16 wisc.edu 144.92.146.69 wisc.edu 198.41.209.117 wisc.edu 128.104.1.207 wisc.edu 144.92.122.14 wisc.edu 216.58.217.142 wisc.edu 128.104.94.54 wisc.edu 128.104.201.59 wisc.edu 128.104.80.119 wisc.edu 144.92.104.126 wisc.edu 128.104.201.59 wisc.edu 128.104.201.59 wisc.edu 144.92.161.74 wisc.edu 144.92.22.140 wisc.edu 128.105.7.163 wisc.edu 144.92.221.86 wisc.edu 144.92.104.126 wisc.edu 144.92.115.213 wisc.edu 128.104.23.170 wisc.edu 128.104.46.254 wisc.edu 128.104.201.59 wisc.edu 128.104.160.19 {:from=>nil, :to=>"opentext_wsm", :ts=>1407745576, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1381672931, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1374079586, :type=>"cms"}|{:fro
{:from=>nil, :to=>"google", :ts=>1387778650, :type=>"provider"}
{:from=>nil, :to=>"sitefinity", :ts=>1394274469, :type=>"cms"}|{:from {:from=>"Akamai", :to=>nil, :ts=>1375989970, :type=>"provider"}|{:fr
{:from=>"opentext_websolutions", :to=>nil, :ts=>1376017618, :type= {:from=>"wordpress", :to=>nil, :ts=>1442907126, :type=>"cms"}
{:from=>nil, :to=>"Linode", :ts=>1376067124, :type=>"provider"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1405901948, :type=>"cms"}|{:fro {:from=>nil, :to=>"opentext_wsm", :ts=>1405755325, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1417960083, :type=>"cms"} {:from=>nil, :to=>"oraclewebcenter", :ts=>1380967328, :type=>"cms {:from=>nil, :to=>"opentext_wsm", :ts=>1401049972, :type=>"cms"}
events
Appendix 4 - Acquia Report
id subdomain root waisman.wisc.edu waisman wisc xyzhang.ece.wisc.edu xyzhang.ece wisc wcer.wisc.edu wcer wisc unidata2-new.ssec.wisc.edu unidata2-new.ssec wisc iotlab.wisc.edu iotlab wisc pages.discovery.wisc.edu pages.discovery wisc rehab.engr.wisc.edu rehab.engr wisc residency.pediatrics.wisc.edu residency.pediatrics wisc distancedegrees.engr.wisc.edu distancedegrees.engr wisc epdengr.wisc.edu epdwww.engr wisc sse.engr.wisc.edu sse.engr wisc ecs.engr.wisc.edu ecs.engr wisc gw.medicine.wisc.edu gw.medicine wisc projects.hsl.wisc.edu projects.hsl wisc gallery.polisci.wisc.edu gallery.polisci wisc madcat.library.wisc.edu madcat.library wisc robotics.me.wisc.edu robotics.me wisc cdw.fammed.wisc.edu cdw.fammed wisc studentems.rso.wisc.edu studentems.rso wisc cdr.wisc.edu cdr wisc cytotechprogram.wisc.edu cytotechprogram wisc extras.bmrb.wisc.edu extras.bmrb wisc lists.nmrfam.wisc.edu lists.nmrfam wisc ehs.wisc.edu ehs wisc ccbc.education.wisc.edu ccbc.education wisc wiscmail.wisc.edu wiscmail wisc search.ebscohost.com.ezproxy.library.wisc.edsearch.ebscohost.com.ezproxy.librar wisc tononi.psychiatry.wisc.edu tononi.psychiatry wisc jobcenter.wisc.edu jobcenter wisc housing.civc.wisc.edu housing.civc wisc services.recsports.wisc.edu services.recsports wisc seasia.wisc.edu seasia wisc polyglot.lss.wisc.edu polyglot.lss wisc rooms.engr.wisc.edu rooms.engr wisc uwphi.pophealth.wisc.edu uwphi.pophealth wisc apir.wisc.edu apir wisc photos.news.wisc.edu photos.news wisc chsra.wisc.edu chsra wisc dmc.wisc.edu dmc wisc education.mrsec.wisc.edu education.mrsec wisc landscape.zoology.wisc.edu landscape.zoology wisc beta.bus.wisc.edu beta.bus wisc courses.bus.wisc.edu courses.bus wisc bus.wisc.edu bus wisc benefits.wisc.edu benefits wisc familyvillage.wisc.edu familyvillage wisc speed.doit.wisc.edu speed.doit wisc mediasite.engr.wisc.edu mediasite.engr wisc website.education.wisc.edu website.education wisc ceo.wisc.edu ceo wisc epd.engr.wisc.edu epd.engr wisc wage.wisc.edu wage wisc transfer.wisc.edu transfer wisc careers.wisc.edu careers wisc lisar.lss.wisc.edu lisar.lss wisc ita.wisc.edu ita wisc voicemail.doit.wisc.edu voicemail.doit wisc myendnoteweb.com.ezproxy.library.wisc.edu myendnoteweb.com.ezproxy.library wisc beckman.cs.wisc.edu beckman.cs wisc arch-cs.wisc.edu arch-www.cs wisc wsbfiles.bus.wisc.edu wsbfiles.bus wisc cvrc.wisc.edu cvrc wisc wisc.eblib.com.ezproxy.library.wisc.edu wisc.eblib.com.ezproxy.library wisc psyphz.psych.wisc.edu psyphz.psych wisc libraryhelp.library.wisc.edu libraryhelp.library wisc chess.wisc.edu chess wisc xerxes.library.wisconsin.edu.ezproxy.library.w xerxes.library.wisconsin.edu.ezproxy wisc uwmarc.wisc.edu uwmarc wisc sfx.wisconsin.edu.ezproxy.library.wisc.edu sfx.wisconsin.edu.ezproxy.library wisc idea.ssec.wisc.edu idea.ssec wisc bcg.wisc.edu bcg wisc on.doit.wisc.edu on.doit wisc portal.isispub.wisc.edu portal.isispub wisc silverbucklepress.library.wisc.edu silverbucklepress.library wisc virtual-museum.soils.wisc.edu virtual-museum.soils wisc cogsci.wisc.edu cogsci wisc wcwts.wisc.edu wcwts wisc romano.physics.wisc.edu romano.physics wisc wai.wisc.edu wai wisc reactor.engr.wisc.edu reactor.engr wisc cp.commarts.wisc.edu cp.commarts wisc weatherstories.ssec.wisc.edu weatherstories.ssec wisc btcs.wisc.edu btcs wisc condor.bmrb.wisc.edu condor.bmrb wisc cinema.global.wisc.edu cinema.global wisc dmc.engr.wisc.edu dmc.engr wisc anatomy.wisc.edu anatomy wisc slisweb.lis.wisc.edu slisweb.lis wisc phytomorph.wisc.edu phytomorph wisc news.college.library.wisc.edu news.college.library wisc vetmedce.vetmed.wisc.edu vetmedce.vetmed wisc webmail.hep.wisc.edu webmail.hep wisc wwwtest.admissions.wisc.edu wwwtest.admissions wisc commonread.education.wisc.edu commonread.education wisc ltgapps.library.wisc.edu ltgapps.library wisc atlas-test.wail.wisc.edu atlas-test.wail wisc blog.gobigread.wisc.edu blog.gobigread wisc china.wisc.edu china wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 9 of 19 platform_dotnet
platform_dotnet mobile|platform_ruby
mobile mobile|platform_ruby
google
google
social_media_like platform_dotnet
mobile|php_5.4|platform_php
php_5.1|platform_php social_media_like|ipv6
platform_dotnet
platform_dotnet platform_php platform_dotnet
platform_dotnet
platform_java
platform_php
apache apache google iis
apache apache
apache apache apache iis apache apache apache apache apache iis apache iis apache iis apache apache google
apache apache apache apache apache
apache iis
coyote iis
iis
platform_dotnet|social_embed
php_5.4|platform_php|ipv6
iis iis
php_5.3|platform_php|ipv6 platform_dotnet
iis iis iis iis
iis
html5|mobile|platform_dotnet platform_dotnet html5|platform_dotnet|social_embed platform_dotnet
platform_dotnet platform_ruby platform_dotnet mobile content_embed
iis
iis iis iis
platform_dotnet platform_dotnet platform_dotnet php_5.4|platform_php|ipv6
iis
apache
platform_dotnet mobile mobile|platform_ruby mobile|platform_dotnet
html5|php_5.5|platform_php mobile|platform_ruby ipv6
ipv6
php_5.4|platform_php|ipv6
iis iis
platform_dotnet|social_embed
websrv
features html5|mobile ipv6 php_5.2|platform_dotnet|platform_php
Amazon AW platform_dotnet mobile html5|mobile|platform_php
cms_veprovider
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created title 1985-09-30 00:00:00 -0400
dns_provid ip wisc.edu 144.92.138.6 wisc.edu 128.104.201.63 wisc.edu 144.92.160.59 wisc.edu 128.104.109.52 wisc.edu 128.104.155.42 wisc.edu 128.104.153.112 uwcreate.engr.wisc.edu wisc.edu 128.104.201.59 www.pediatrics.wisc.edu wisc.edu 144.92.221.86 wisc.edu 144.92.225.235 epdweb.engr.wisc.edu wisc.edu 144.92.225.235 wisc.edu 144.92.225.235 wisc.edu 128.104.201.59 wisc.edu 128.104.208.29 wisc.edu 144.92.50.148 wisc.edu 144.92.158.36 search.library.wisc.edu wisc.edu 128.104.46.254 robotics.engr.wisc.edu wisc.edu 128.104.201.59 wisc.edu 144.92.41.18 144.92.74.126 wisc.edu 144.92.196.41 wisc.edu 144.92.9.17 wisc.edu 144.92.217.24 wisc.edu 144.92.4.177 wisc.edu 144.92.9.102 wisc.edu 144.92.146.69 login.wisc.edu wisc.edu 128.104.1.207 patron.library.wisc.edu wisc.edu 128.104.46.219 centerforsleepandconsciousnes wisc.edu 144.92.177.178 wisc.edu 128.104.81.216 wisc.edu 128.104.81.186 wisc.edu 128.104.31.122 wisc.edu 128.104.23.170 wisc.edu 144.92.115.213 wisc.edu 128.104.201.96 wisc.edu 144.92.239.172 wisc.edu 128.104.80.156 wisc.edu 144.92.9.200 wisc.edu 144.92.156.11 kb.wisc.edu wisc.edu 128.104.22.180 wisc.edu 144.92.9.17 wisc.edu 144.92.58.161 wisc.edu 144.92.104.14 wisc.edu 144.92.212.18 wisc.edu 144.92.212.43 www.bussvc.wisc.edu wisc.edu 128.104.73.77 wisc.edu 144.92.138.9 wisc.edu 144.92.194.22 wisc.edu 144.92.12.152 wisc.edu 144.92.146.107 wisc.edu 128.104.81.186 epdweb.engr.wisc.edu wisc.edu 144.92.225.235 wisc.edu 128.104.23.170 wisc.edu 144.92.239.222 csportal.engr.wisc.edu wisc.edu 128.104.201.96 wisc.edu 144.92.115.213 wisc.edu 128.104.80.140 login.wisc.edu wisc.edu 128.104.1.207 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 128.105.7.137 wisc.edu 128.105.17.33 wisc.edu 144.92.212.13 wisc.edu 128.104.20.19 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 128.104.232.31 wisc.edu 23.23.240.176 wisc.edu 128.104.189.11 wisc.edu 128.104.46.200 128.104.201.72 www.library.wisc.edu 128.104.1.195 www.star.nesdis.noaa.gov wisc.edu 140.90.107.15 wisc.edu 144.92.73.171 wisc.edu 128.104.1.210 wisc.edu 144.92.9.98 wisc.edu 128.104.1.195 wisc.edu 144.92.93.172 wisc.edu 144.92.146.16 wisc.edu 128.104.81.186 wisc.edu 128.104.160.19 wisc.edu 128.104.208.69 wisc.edu 128.104.201.96 wisc.edu 144.92.226.62 wisc.edu 128.104.108.105 wisc.edu 128.104.23.170 wisc.edu 144.92.167.254 wisc.edu 128.104.23.170 wisc.edu 144.92.225.235 wisc.edu 128.104.20.46 wisc.edu 128.104.96.79 wisc.edu 128.104.98.39 wisc.edu 74.125.29.121 128.104.212.10 rc.physics.wisc.edu wisc.edu 128.104.164.18 wisc.edu 128.104.81.156 wisc.edu 144.92.146.69 wisc.edu 128.104.46.228 wisc.edu 198.133.224.233 wisc.edu 216.239.32.21 wisc.edu 128.104.23.170
redirect
{:from=>nil, :to=>"google", :ts=>1388633858, :type=>"provider"}
{:from=>"sitefinity", :to=>nil, :ts=>1429074659, :type=>"cms"}
{:from=>nil, :to=>"google", :ts=>1387577298, :type=>"provider"}
{:from=>nil, :to=>"wordpress", :ts=>1406153169, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1418623609, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1424917302, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1408565436, :type=>"cms"}
{:from=>"moodle", :to=>nil, :ts=>1415675553, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1403885690, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1408024574, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1407570544, :type=>"cms"}|{:fro
{:from=>"opentext_websolutions", :to=>nil, :ts=>1373994148, :type=
{:from=>nil, :to=>"opentext_wsm", :ts=>1403650732, :type=>"cms"}
events {:from=>nil, :to=>"opentext_wsm", :ts=>1401154118, :type=>"cms"}
Appendix 4 - Acquia Report
id subdomain root wiki.hep.wisc.edu wiki.hep wisc fhybrid.slc.engr.wisc.edu fhybrid.slc.engr wisc biopop.pophealth.wisc.edu biopop.pophealth wisc mail.chem.wisc.edu mail.chem wisc rosebowl.wisc.edu rosebowl wisc cqpi.wisc.edu cqpi wisc patstore.wisc.edu patstore wisc rgraphics.limnology.wisc.edu rgraphics.limnology wisc fpm-www3.fpm.wisc.edu fpm-www3.fpm wisc biothreat.engr.wisc.edu biothreat.engr wisc cdha.ssc.wisc.edu cdha.ssc wisc wipac.wisc.edu wipac wisc readingthai.wisc.edu readingthai wisc kb.cae.wisc.edu kb.cae wisc wilson.engr.wisc.edu wilson.engr wisc psilab.ep.wisc.edu psilab.ep wisc wisli.wisc.edu wisli wisc dictionary.oed.com.ezproxy.library.wisc.edu dictionary.oed.com.ezproxy.library wisc wicci.wisc.edu wicci wisc dining.housing.wisc.edu dining.housing wisc tethered.cae.wisc.edu tethered.cae wisc cdn.education.wisc.edu cdn.education wisc rnmr.nmrfam.wisc.edu rnmr.nmrfam wisc flas.wisc.edu flas wisc devstudies.wisc.edu devstudies wisc digicoll-dev.library.wisc.edu digicoll-dev.library wisc survey.wisc.edu survey wisc isis.wisc.edu isis wisc wiscard.wisc.edu wiscard wisc aha.anesthesia.wisc.edu aha.anesthesia wisc lidar.ssec.wisc.edu lidar.ssec wisc warungsinema.wisc.edu warungsinema wisc philosophy.wisc.edu philosophy wisc services.education.wisc.edu services.education wisc csrosetta.bmrb.wisc.edu csrosetta.bmrb wisc carbon.chem.wisc.edu carbon.chem wisc gallery.icecube.wisc.edu gallery.icecube wisc homepages.cae.wisc.edu homepages.cae wisc envhist.wisc.edu envhist wisc asc.wisc.edu asc wisc ccr.aos.wisc.edu ccr.aos wisc us.history.wisc.edu us.history wisc dairyfoods.wisc.edu dairyfoods wisc foodsci.wisc.edu foodsci wisc mywebspace.wisc.edu mywebspace wisc chancellorsearch.wisc.edu chancellorsearch wisc aants.net.wisc.edu aants.net wisc bmec.wisc.edu bmec wisc cme.pediatrics.wisc.edu cme.pediatrics wisc global.wisc.edu global wisc greatu.wisc.edu greatu wisc bact.wisc.edu bact wisc intranet.anesthesia.wisc.edu intranet.anesthesia wisc legolas.ece.wisc.edu legolas.ece wisc fusion.wisc.edu fusion wisc slc.engr.wisc.edu slc.engr wisc tropic.ssec.wisc.edu tropic.ssec wisc twccc.che.wisc.edu twccc.che wisc ombuds.wisc.edu ombuds wisc tlsymposium.wisc.edu tlsymposium wisc guts.wisc.edu guts wisc condor-view.cs.wisc.edu condor-view.cs wisc web.ebscohost.com.ezproxy.library.wisc.edu web.ebscohost.com.ezproxy.library wisc htcondor-wiki.cs.wisc.edu htcondor-wiki.cs wisc yin.che.wisc.edu yin.che wisc ww.bus.wisc.edu ww.bus wisc mechatronics.me.wisc.edu mechatronics.me wisc kellerlab.bact.wisc.edu kellerlab.bact wisc preview.doit.wisc.edu preview.doit wisc eyh.wisc.edu eyh wisc web.library.wisc.edu web.library wisc humanrights.wisc.edu humanrights wisc uwlab.soils.wisc.edu uwlab.soils wisc ansci.wisc.edu ansci wisc raptor.physics.wisc.edu raptor.physics wisc apps.webofknowledge.com.ezproxy.library.wisapps.webofknowledge.com.ezproxy.lwisc rigel.neep.wisc.edu rigel.neep wisc willett.ece.wisc.edu willett.ece wisc mri.psychiatry.wisc.edu mri.psychiatry wisc ebling.library.wisc.edu ebling.library wisc psychiatry.wisc.edu psychiatry wisc crpbis.apl.wisc.edu crpbis.apl wisc arrow.wisc.edu arrow wisc drc.engr.wisc.edu drc.engr wisc psoup.math.wisc.edu psoup.math wisc login.wisc.edu login wisc helpdesk.shc.wisc.edu helpdesk.shc wisc newunion.wisc.edu newunion wisc remus.lss.wisc.edu remus.lss wisc libcd.law.wisc.edu libcd.law wisc mem.engr.wisc.edu mem.engr wisc bst.sagepub.com.ezproxy.library.wisc.edu bst.sagepub.com.ezproxy.library wisc rig.ssec.wisc.edu rig.ssec wisc ecology.wisc.edu ecology wisc weather.physics.wisc.edu weather.physics wisc mds.bussvc.wisc.edu mds.bussvc wisc psych.wisc.edu psych wisc pages.cs.wisc.edu pages.cs wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 10 of 19 mobile|platform_ruby ipv6 php_5.3|platform_php ipv6 platform_dotnet platform_dotnet mobile
php_5.3|platform_php mobile platform_dotnet
mobile|platform_ruby mobile ipv6 platform_dotnet mobile|php_5.5|platform_php platform_dotnet php_5.3|platform_dotnet|platform_php platform_dotnet mobile|ipv6
mobile php_5.3|platform_php php_5.3|platform_dotnet|platform_php platform_dotnet
ipv6 platform_dotnet ipv6 php_5.3|platform_php mobile|social_embed
mobile|platform_ruby
php_5.4|platform_php|ipv6 ipv6 mobile|ipv6 php_5.3|platform_php ipv6 platform_dotnet mobile|platform_dotnet social_embed|social_media_like
platform_dotnet platform_dotnet
mobile|ipv6 ipv6
ipv6 mobile|php_5.3|platform_php ipv6 php_5.3|platform_php platform_dotnet platform_dotnet
platform_dotnet php_5.3|platform_php platform_dotnet
iis iis
iis
iis iis
iis iis pws
apache apache iis iis apache apache apache apache apache apache apache iis iis apache apache apache apache apache iis apache apache apache apache
apache iis iis apache apache apache
iis apache apache apache apache
apache iis
iis iis apache
platform_dotnet platform_dotnet
platform_dotnet
apache iis apache apache apache iis apache apache iis apache iis apache iis
websrv apache apache apache apache apache apache iis nginx iis apache
html5|mobile platform_dotnet mobile|ipv6 ipv6 ipv6 platform_dotnet mobile|platform_ruby php_5.3|platform_php platform_dotnet ipv6 platform_dotnet
platform_dotnet
platform_dotnet
php_5.3|platform_php
features
1&1 Internephp_5.5|platform_php
cms_veprovider
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created
title
management.engr.wisc.edu patron.library.wisc.edu metobs.ssec.wisc.edu
www.union.wisc.edu
www.wisc.edu
login.wisc.edu
patron.library.wisc.edu fti.neep.wisc.edu
law.wisc.edu
patron.library.wisc.edu
login.wisc.edu www.engr.wisc.edu www.pediatrics.wisc.edu
nelson.wisc.edu
ahahq.org
patron.library.wisc.edu
kb.wisc.edu
epdweb.engr.wisc.edu
redirect
dns_provid ip 144.92.180.251 wisc.edu 128.104.201.107 128.104.99.167 wisc.edu 128.104.71.223 wisc.edu 144.92.9.53 wisc.edu 144.92.9.17 wisc.edu 128.104.54.37 wisc.edu 162.144.12.28 wisc.edu 144.92.175.161 wisc.edu 144.92.225.235 wisc.edu 144.92.190.192 wisc.edu 128.104.255.62 wisc.edu 128.104.23.170 wisc.edu 128.104.22.180 wisc.edu 128.104.201.59 wisc.edu 128.104.201.64 wisc.edu 128.104.23.170 wisc.edu 128.104.46.219 wisc.edu 144.92.235.112 wisc.edu 144.92.27.193 wisc.edu 128.104.201.95 wisc.edu 144.92.146.69 wisc.edu 144.92.4.144 wisc.edu 128.104.81.17 wisc.edu 128.104.81.92 wisc.edu 144.92.161.55 wisc.edu 128.104.81.42 wisc.edu 128.104.81.125 wisc.edu 144.92.239.224 wisc.edu 108.175.11.87 wisc.edu 128.104.108.80 wisc.edu 128.104.23.170 wisc.edu 144.92.115.213 wisc.edu 128.104.149.167 wisc.edu 144.92.167.251 wisc.edu 128.104.71.241 wisc.edu 128.104.255.43 wisc.edu 144.92.13.84 wisc.edu 144.92.235.112 wisc.edu 128.104.201.94 wisc.edu 144.92.130.91 wisc.edu 128.104.80.225 wisc.edu 128.104.81.242 wisc.edu 128.104.81.124 wisc.edu 128.104.22.38 wisc.edu 144.92.9.53 wisc.edu 128.104.1.207 wisc.edu 128.104.201.59 wisc.edu 144.92.221.86 wisc.edu 128.104.23.170 wisc.edu 128.104.81.186 wisc.edu 144.92.49.76 wisc.edu 144.92.218.233 wisc.edu 128.104.201.100 wisc.edu 128.104.201.71 wisc.edu 128.104.201.96 wisc.edu 128.104.108.131 wisc.edu 128.104.201.99 wisc.edu 128.104.81.186 wisc.edu 128.104.81.186 wisc.edu 70.39.232.40 wisc.edu 128.105.7.152 wisc.edu 128.104.46.219 wisc.edu 128.105.7.112 wisc.edu 128.104.201.62 wisc.edu 144.92.212.18 wisc.edu 128.104.201.104 wisc.edu 144.92.49.119 wisc.edu 128.104.80.153 wisc.edu 144.92.206.29 wisc.edu 128.104.46.166 wisc.edu 128.104.94.54 wisc.edu 128.104.168.146 wisc.edu 144.92.75.11 wisc.edu 128.104.164.100 wisc.edu 128.104.46.219 wisc.edu 128.104.184.130 wisc.edu 128.104.201.63 wisc.edu 144.92.177.178 wisc.edu 144.92.50.151 wisc.edu 144.92.177.178 wisc.edu 144.92.122.50 wisc.edu 128.104.22.162 wisc.edu 128.104.1.207 wisc.edu 144.92.166.28 wisc.edu 128.104.1.223 wisc.edu 144.92.235.115 wisc.edu 128.104.80.31 wisc.edu 144.92.115.220 wisc.edu 128.104.94.43 wisc.edu 144.92.225.235 wisc.edu 128.104.46.219 wisc.edu 128.104.108.105 wisc.edu 144.92.235.112 wisc.edu 128.104.160.19 wisc.edu 128.104.73.84 wisc.edu 128.104.130.152 wisc.edu 128.105.7.26 {:from=>nil, :to=>"joomla", :ts=>1382721406, :type=>"cms"}|{:from=
{:from=>nil, :to=>"wordpress", :ts=>1412597369, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1427160289, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1410309310, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1412392805, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1400531410, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1403646781, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1402508621, :type=>"cms"}
{:from=>nil, :to=>"1&1 Internet", :ts=>1376113371, :type=>"provider
{:from=>nil, :to=>"wordpress", :ts=>1421116660, :type=>"cms"}|{:fro
{:from=>"theplanet", :to=>"SoftLayer", :ts=>1376113477, :type=>"pr
{:from=>"wordpress", :to=>nil, :ts=>1389789796, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1403261844, :type=>"cms"}
events
Appendix 4 - Acquia Report
id subdomain root adclub.journalism.wisc.edu adclub.journalism wisc tellus.ssec.wisc.edu tellus.ssec wisc weedecology.wisc.edu weedecology wisc silver.neep.wisc.edu silver.neep wisc histsci.wisc.edu histsci wisc my.aae.wisc.edu my.aae wisc proquest.umi.com.ezproxy.library.wisc.edu proquest.umi.com.ezproxy.library wisc nucth.physics.wisc.edu nucth.physics wisc sciencedirect.com.ezproxy.library.wisc.edu sciencedirect.com.ezproxy.library wisc figs.wisc.edu figs wisc medphysics.wisc.edu medphysics wisc sacm.cs.wisc.edu sacm.cs wisc www-auth.cs.wisc.edu www-auth.cs wisc maps.aqua.wisc.edu maps.aqua wisc webmail.cs.wisc.edu webmail.cs wisc honors.ls.wisc.edu honors.ls wisc accessmedicine.com.ezproxy.library.wisc.edu accessmedicine.com.ezproxy.library wisc morris.commarts.wisc.edu morris.commarts wisc deweylab.biostat.wisc.edu deweylab.biostat wisc ioa126.medsch.wisc.edu ioa126.medsch wisc pin.primate.wisc.edu pin.primate wisc ipad.primate.wisc.edu ipad.primate wisc bmedesign.engr.wisc.edu bmedesign.engr wisc uwrightnow.wisc.edu uwrightnow wisc continuingstudies.wisc.edu continuingstudies wisc nislab.ece.wisc.edu nislab.ece wisc solimserver.geography.wisc.edu solimserver.geography wisc ocpd.wisc.edu ocpd wisc nowak.ece.wisc.edu nowak.ece wisc agroecology.wisc.edu agroecology wisc flows.net.wisc.edu flows.net wisc foodsafety.wisc.edu foodsafety wisc cup.aos.wisc.edu cup.aos wisc lists.fammed.wisc.edu lists.fammed wisc uwmmsl.chem.wisc.edu uwmmsl.chem wisc dev.loci.wisc.edu dev.loci wisc bpa.wisc.edu bpa wisc efellow.housing.wisc.edu efellow.housing wisc uwcc.wisc.edu uwcc wisc show.wisc.edu show wisc snow.icecube.wisc.edu snow.icecube wisc icf4.neep.wisc.edu icf4.neep wisc ktgroup.me.wisc.edu ktgroup.me wisc training.apl.wisc.edu training.apl wisc www2.uwfoundation.wisc.edu www2.uwfoundation wisc engage.doit.wisc.edu engage.doit wisc facstaff.wcer.wisc.edu facstaff.wcer wisc hts.wisc.edu hts wisc emergency.wisc.edu emergency wisc nmmc.engr.wisc.edu nmmc.engr wisc payback.wisc.edu payback wisc pma.doit.wisc.edu pma.doit wisc uwpolice.wisc.edu uwpolice wisc stemcellarchives.library.wisc.edu stemcellarchives.library wisc csld.wisc.edu csld wisc relief.ersc.wisc.edu relief.ersc wisc cbemain.cbe.wisc.edu cbemain.cbe wisc guestnetid.wisc.edu guestnetid wisc senes.biochem.wisc.edu senes.biochem wisc webmail.ssc.wisc.edu webmail.ssc wisc uwallies.rso.wisc.edu uwallies.rso wisc wendt.wisc.edu wendt wisc admiss.gradsch.wisc.edu admiss.gradsch wisc meritnews.education.wisc.edu meritnews.education wisc dev.soils.wisc.edu dev.soils wisc biology.wisc.edu biology wisc libraries.arcasearch.com.ezproxy.library.wisc. libraries.arcasearch.com.ezproxy.libr wisc topology.cs.wisc.edu topology.cs wisc aud.wisc.edu aud wisc wi.ssc.wisc.edu wi.ssc wisc engels.genetics.wisc.edu engels.genetics wisc fiscdorms.cals.wisc.edu fiscdorms.cals wisc apple.doit.wisc.edu apple.doit wisc hae.slc.engr.wisc.edu hae.slc.engr wisc matmodel.engr.wisc.edu matmodel.engr wisc ans.neep.wisc.edu ans.neep wisc bus.ems.wisc.edu bus.ems wisc mynursingce.son.wisc.edu mynursingce.son wisc tohru.trace.wisc.edu tohru.trace wisc ag.uwmf.wisc.edu ag.uwmf wisc microbialsciences.wisc.edu microbialsciences wisc scimedgrs.wisc.edu scimedgrs wisc classlists.wisc.edu classlists wisc paleodb.geology.wisc.edu paleodb.geology wisc bullyingundefined.journalism.wisc.edu bullyingundefined.journalism wisc stellar.wcer.wisc.edu stellar.wcer wisc builds.icecube.wisc.edu builds.icecube wisc jhppl.dukejournals.org.ezproxy.library.wisc.ed jhppl.dukejournals.org.ezproxy.librarywisc msme.engr.wisc.edu msme.engr wisc wca.wisc.edu wca wisc ncs.wisc.edu ncs wisc newfac.sysbio.discovery.wisc.edu newfac.sysbio.discovery wisc www2.housing.wisc.edu www2.housing wisc pxrdwebcam.chem.wisc.edu pxrdwebcam.chem wisc mail.physics.wisc.edu mail.physics wisc access.wisc.edu access wisc announcements.microbialsciences.wisc.edu announcements.microbialsciences wisc digitallibrary.sae.org.ezproxy.library.wisc.edu digitallibrary.sae.org.ezproxy.library wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 11 of 19
features
platform_dotnet mobile|platform_ruby
platform_dotnet
ipv6
platform_dotnet|platform_php php_5.3|platform_php mobile
platform_dotnet
platform_php platform_dotnet platform_php mobile
platform_dotnet
mobile
html5|mobile platform_dotnet mobile
php_5.4|platform_php|ipv6 platform_ruby|social_embed content_embed|html5|mobile|platform_dotnet ipv6 platform_dotnet platform_dotnet ipv6 html5|mobile mobile|ipv6 platform_dotnet
php_5.4|platform_php
php_5.4|platform_php php_5.4|platform_php mobile|php_5.4|platform_php platform_dotnet mobile php_5.3|platform_php
php_5.3|platform_php platform_dotnet mobile|platform_ruby ipv6 mobile|platform_ruby html5|mobile php_5.3|platform_php
ipv6 php_5.3|platform_php
mobile|platform_ruby
php_5.4|platform_php|ipv6 platform_dotnet
platform_dotnet platform_dotnet
platform_dotnet
mobile|platform_ruby
mobile mobile
platform_dotnet mobile ipv6 ipv6 ipv6 platform_dotnet Amazon AW platform_php
cms_veprovider
apache iis apache apache
nginx apache zserver lighttpd apache apache iis apache iis iis
iis apache iis apache apache apache apache iis apache apache apache apache apache
apache apache apache iis apache apache iis apache apache apache iis apache apache apache iis apache apache apache apache apache apache apache apache iis apache iis apache apache
iis
iis
iis iis
iis
iis
iis
websrv
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created
title
dns_provid ip wisc.edu 144.92.22.140 wisc.edu 128.104.108.105 wisc.edu 144.92.93.172 wisc.edu 128.104.184.243 wisc.edu 144.92.115.213 wisc.edu 144.92.122.14 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 128.104.160.19 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 144.92.9.17 wisc.edu 128.104.3.58 wisc.edu 128.105.17.21 wisc.edu 128.105.7.30 wisc.edu 144.92.44.215 wisc.edu 128.105.7.103 wisc.edu 128.104.81.29 wisc.edu 128.104.46.200 wisc.edu 144.92.226.62 wisc.edu 144.92.73.51 wisc.edu 144.92.62.126 wisc.edu 128.104.92.17 wisc.edu 128.104.92.31 wisc.edu 128.104.201.96 wisc.edu 128.104.22.215 wisc.edu 128.104.155.42 wisc.edu 128.104.201.100 wisc.edu 144.92.235.40 wisc.edu 128.104.81.69 wisc.edu 128.104.201.100 wisc.edu 144.92.9.17 login.wisc.edu wisc.edu 128.104.1.207 wisc.edu 128.104.81.186 wisc.edu 144.92.130.175 wisc.edu 144.92.41.61 wisc.edu 128.104.71.199 wisc.edu 144.92.48.145 wisc.edu 144.92.175.175 www.housing.wisc.edu wisc.edu 128.104.81.174 wisc.edu 144.92.122.14 www.med.wisc.edu wisc.edu 144.92.154.150 gallery.icecube.wisc.edu 128.104.255.43 fti.neep.wisc.edu 128.104.184.130 128.104.201.104 144.92.122.50 wisc.edu 144.92.185.242 wisc.edu 128.104.144.187 wisc.edu 144.92.160.59 wisc.edu 128.104.208.69 wisc.edu 128.104.1.227 wisc.edu 128.104.201.96 wisc.edu 144.92.160.80 wisc.edu 128.104.81.92 wisc.edu 144.92.239.167 wisc.edu 128.104.1.195 wisc.edu 128.104.89.251 www.ersc.wisc.edu wisc.edu 128.104.108.105 wisc.edu 144.92.111.199 wisc.edu 128.104.80.75 wisc.edu 128.104.119.237 wisc.edu 144.92.190.178 144.92.74.0 wendt.engr.wisc.edu wisc.edu 128.104.201.96 wisc.edu 128.104.147.179 wisc.edu 144.92.146.69 wisc.edu 144.92.93.172 wisc.edu 128.104.80.225 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 128.105.7.151 wisc.edu 144.92.57.237 wisc.edu 144.92.191.152 wisc.edu 128.104.80.203 wisc.edu 144.92.93.157 kb.wisc.edu wisc.edu 128.104.22.180 wisc.edu 128.104.201.70 wisc.edu 128.104.201.96 wisc.edu 128.104.201.96 wisc.edu 144.92.104.126 wisc.edu 107.20.220.47 wisc.edu 128.104.201.134 wisc.edu 144.92.250.64 wisc.edu 144.92.72.106 wisc.edu 144.92.49.95 login.wisc.edu wisc.edu 128.104.1.207 paleobiodb.org wisc.edu 144.92.206.79 wisc.edu 144.92.22.140 144.92.160.52 wisc.edu 128.8.164.165 patron.library.wisc.edu wisc.edu 128.104.46.219 distancedegrees.engr.wisc.edu wisc.edu 144.92.225.235 WCA.wisc.edu wisc.edu 144.92.160.80 wisc.edu 144.92.119.36 wisc.edu 128.104.81.186 wisc.edu 128.104.56.38 wisc.edu 128.104.71.141 sm.physics.wisc.edu wisc.edu 128.104.164.10 wisc.edu 128.104.80.115 wisc.edu 144.92.72.100 patron.library.wisc.edu wisc.edu 128.104.46.219 osse.ssec.wisc.edu
redirect
{:from=>nil, :to=>"wordpress", :ts=>1409203140, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1425443290, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1404866437, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401255619, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1413567890, :type=>"cms"}|{:fro
{:from=>"wordpress", :to=>nil, :ts=>1413478216, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1425470200, :type=>"cms"}
{:from=>nil, :to=>"websphere_portal", :ts=>1417171195, :type=>"cm
{:from=>nil, :to=>"wordpress", :ts=>1418623203, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1410881608, :type=>"cms"}|{:fro {:from=>nil, :to=>"opentext_wsm", :ts=>1410348624, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1413147412, :type=>"cms"}|{:fro
events
Appendix 4 - Acquia Report
id jspc.library.wisc.edu aurora.aos.wisc.edu aspi.wisc.edu brainmap.wisc.edu derc.wisc.edu newsroom.stemcells.wisc.edu coursedashboard.learnuw.wisc.edu blick.engr.wisc.edu internationalinstitute.wisc.edu m.mdconsult.com.ezproxy.library.wisc.edu thompson.commarts.wisc.edu conserve.wisc.edu mrgcvd.engr.wisc.edu phoenix.chem.wisc.edu soar.wisc.edu preview.center4design.wisc.edu nitrolab.engr.wisc.edu music.library.wisc.edu engage.wisc.edu sohecam.aims.wisc.edu c4.discovery.wisc.edu delta.bussvc.wisc.edu services.commarts.wisc.edu dsmig.pediatrics.wisc.edu profhorn.aos.wisc.edu adac.wisc.edu currentaccount.lafollette.wisc.edu parrot.cs.wisc.edu ats.doit.wisc.edu courses.journalism.wisc.edu wendtcs.engr.wisc.edu wins.engr.wisc.edu testing.doit.wisc.edu next.discovery.wisc.edu wistep.wisc.edu in-cnerg.engr.wisc.edu tools.wisccal.wisc.edu sahalab.bme.wisc.edu medil.medsch.wisc.edu virology.wisc.edu venus.wisc.edu budget.wisc.edu wisp.physics.wisc.edu go.wisc.edu api.hecc.wisc.edu cow.physics.wisc.edu badgersabroad.wisc.edu pi.wisc.edu learnuw.wisc.edu xray-calendar.chem.wisc.edu cress-external.engr.wisc.edu ewh.slc.engr.wisc.edu labweb.education.wisc.edu dev.law.wisc.edu users.polisci.wisc.edu outreach.sbel.wisc.edu erc.cals.wisc.edu healthcaregames.wisc.edu visualculture.wisc.edu telepresence.wisc.edu public.my.wisc.edu embarkkiosk.chazen.wisc.edu dionysus.psych.wisc.edu asabe.bse.wisc.edu hvacr.wisc.edu onlineservices.housing.wisc.edu ccp.wisc.edu aissmartprevention.wisc.edu brainimaging.waisman.wisc.edu agingresearch.wisc.edu digicoll.library.wisc.edu worldcat.org.ezproxy.library.wisc.edu mepes.engr.wisc.edu wi.global.wisc.edu news.wisc.edu primatelit.library.wisc.edu wiscareers.wisc.edu social.wisc.edu pec.engr.wisc.edu visp.wisc.edu tdl.wisc.edu ntp.neuroscience.wisc.edu wcceal.chsra.wisc.edu apps.pharmacy.wisc.edu comdis.wisc.edu journals.library.wisc.edu wisconsinsuperbikes.rso.wisc.edu oed.wisc.edu www2.fpm.wisc.edu deposit.bmrb.wisc.edu deposit-beta.bmrb.wisc.edu jcr.wisc.edu sife.rso.wisc.edu worms.zoology.wisc.edu residents.housing.wisc.edu genetics.wisc.edu cqpi.engr.wisc.edu hmongrp.wisc.edu
subdomain jspc.library aurora.aos aspi brainmap derc newsroom.stemcells coursedashboard.learnuw blick.engr internationalinstitute m.mdconsult.com.ezproxy.library thompson.commarts conserve mrgcvd.engr phoenix.chem soar preview.center4design nitrolab.engr music.library engage sohecam.aims c4.discovery delta.bussvc services.commarts dsmig.pediatrics profhorn.aos adac currentaccount.lafollette parrot.cs ats.doit courses.journalism wendtcs.engr wins.engr testing.doit next.discovery wistep in-cnerg.engr tools.wisccal sahalab.bme medil.medsch virology venus budget wisp.physics go api.hecc cow.physics badgersabroad pi learnuw xray-calendar.chem cress-external.engr ewh.slc.engr labweb.education dev.law users.polisci outreach.sbel erc.cals healthcaregames visualculture telepresence public.my embarkkiosk.chazen dionysus.psych asabe.bse hvacr onlineservices.housing ccp aissmartprevention brainimaging.waisman agingresearch digicoll.library worldcat.org.ezproxy.library mepes.engr wi.global news primatelit.library wiscareers social pec.engr visp tdl ntp.neuroscience wcceal.chsra apps.pharmacy comdis journals.library wisconsinsuperbikes.rso oed www2.fpm deposit.bmrb deposit-beta.bmrb jcr sife.rso worms.zoology residents.housing genetics cqpi.engr hmongrp
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
cms_veprovider
Appendix 4 - Page 12 of 19 mobile social_embed ipv6 platform_php
platform_php
content_embed platform_dotnet
php_5.2|platform_dotnet|platform_php
platform_dotnet platform_ruby|social_embed content_embed|ipv6 platform_dotnet php_5.2|platform_php
platform_dotnet mobile|platform_ruby
mobile|platform_ruby
mobile|php_5.3|platform_php php_5.3|platform_dotnet|platform_php
mobile|php_5.3|platform_php php_5.4|platform_php|ipv6
mobile
php_5.5|platform_php
mobile platform_dotnet mobile|php_5.4|platform_php|ipv6
mobile platform_dotnet php_5.3|platform_php ipv6 ipv6
php_5.4|platform_php platform_dotnet ipv6
mobile|php_5.3|platform_php
php_5.4|platform_php mobile platform_dotnet
php_5.4|platform_php|ipv6 ipv6 platform_dotnet mobile platform_dotnet ipv6
platform_dotnet mobile
platform_php
platform_php
html5|mobile|platform_dotnet|social_embed
mobile ipv6 platform_dotnet mobile|platform_ruby php_5.3|platform_php platform_dotnet ipv6
platform_dotnet platform_ruby ipv6
features
iis apache apache iis apache apache iis apache apache iis apache apache apache apache apache iis apache apache apache apache apache apache apache apache apache
iis
iis
iis
iis
iis coyote apache apache apache iis apache
apache apache apache apache apache iis
apache apache apache
apache iis
apache iis apache apache iis apache apache iis apache apache apache apache
websrv apache apache iis apache apache apache
title
redirect
dns_provid ip wisc.edu 144.92.161.31 wisc.edu 144.92.130.152 wisc.edu 128.104.80.225 wisc.edu 144.92.76.37 wisc.edu 128.104.201.94 wisc.edu 144.92.9.200 login.wisc.edu wisc.edu 128.104.1.207 nanomachines.com wisc.edu 212.162.13.230 intl-institute.wisc.edu wisc.edu 128.104.23.170 1985-09-30 00:00:00 -0400 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 144.92.226.62 wisc.edu 128.104.64.28 wisc.edu 128.104.201.59 wisc.edu 128.104.71.81 wisc.edu 128.104.81.186 wisc.edu 128.104.81.130 wisc.edu 128.104.201.96 wisc.edu 128.104.1.195 wisc.edu 128.104.144.187 144.92.90.0 wisc.edu 128.104.153.112 wisc.edu 128.104.73.89 login.wisc.edu wisc.edu 128.104.1.207 www.pediatrics.wisc.edu wisc.edu 144.92.221.86 wisc.edu 144.92.131.143 wisc.edu 128.104.81.92 wisc.edu 144.92.45.30 research.cs.wisc.edu wisc.edu 128.105.7.58 wisc.edu 128.104.144.187 wisc.edu 144.92.22.140 1985-09-30 00:00:00 -0400 wts.wisc.edu wisc.edu 144.92.13.148 wisc.edu 128.104.201.59 wisc.edu 128.104.144.154 wisc.edu 128.104.153.124 wisc.edu 128.104.81.186 login.engr.wisc.edu wisc.edu 144.92.13.70 wisc.edu 128.104.80.79 wisc.edu 128.104.201.97 wisc.edu 144.92.9.17 wisc.edu 144.92.238.12 wisc.edu 128.104.109.83 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.53 wisc.edu 128.104.164.41 wisc.edu 128.104.201.42 wisc.edu 144.92.122.14 wisc.edu 128.104.160.19 wisc.edu 128.104.23.171 login.wisc.edu wisc.edu 128.104.1.207 wisc.edu 128.104.81.201 wisc.edu 128.104.71.30 wisc.edu 128.104.201.96 wisc.edu 128.104.201.70 wisc.edu 144.92.146.16 login.wisc.edu wisc.edu 128.104.1.207 www.polisci.wisc.edu wisc.edu 128.104.81.186 wisc.edu 128.104.201.94 www.uwex.edu wisc.edu 128.104.248.62 wisc.edu 144.92.50.149 1985-09-30 00:00:00 -0400 home | cente wisc.edu 144.92.9.17 kb.wisc.edu wisc.edu 128.104.22.180 1985-09-30 00:00:00 -0400 myuw-madis wisc.edu 144.92.197.135 wisc.edu 144.92.202.198 wisc.edu 128.104.130.200 wisc.edu 144.92.93.172 wisc.edu 128.104.201.94 wisc.edu 144.92.74.100 communityrelations.wisc.edu wisc.edu 144.92.9.53 wisc.edu 144.92.122.50 wisc.edu 128.104.232.24 wisc.edu 128.104.81.92 uwdc.library.wisc.edu wisc.edu 128.104.1.195 1985-09-30 00:00:00 -0400 patron.library.wisc.edu wisc.edu 128.104.46.219 distancedegrees.engr.wisc.edu wisc.edu 144.92.225.235 wisc.edu 128.104.23.170 wisc.edu 144.92.9.200 wisc.edu 144.92.161.37 WisCareers.wisc.edu wisc.edu 144.92.160.80 wisc.edu 144.92.9.200 wisc.edu 128.104.201.59 Continuingstudies.wisc.edu wisc.edu 128.104.155.42 1985-09-30 00:00:00 -0400 wisc.edu 144.92.198.11 1985-09-30 00:00:00 -0400 wisc.edu 144.92.239.227 wisc.edu 144.92.156.25 1985-09-30 00:00:00 -0400 school of ph wisc.edu 128.104.115.242 1985-09-30 00:00:00 -0400 csd.wisc.edu wisc.edu 128.104.80.37 digipub.library.wisc.edu wisc.edu 144.92.161.74 144.92.74.126 1985-09-30 00:00:00 -0400 wisc.edu 128.104.81.92 wisc.edu 128.104.64.28 wisc.edu 144.92.217.19 wisc.edu 144.92.217.30 www.ejcr.org wisc.edu 198.20.241.41 144.92.74.0 wisc.edu 144.92.238.225 wisc.edu 128.104.174.50 wisc.edu 144.92.9.17 1985-09-30 00:00:00 -0400 uw laborator 1985-09-30 00:00:00 -0400 center for qucqpi.wisc.edu wisc.edu 144.92.9.17 wisc.edu 144.92.64.40
domain_created
{:from=>"6.26", :to=>nil, :ts=>1383456717, :type=>"cms_version"}|{: {:from=>nil, :to=>"opentext_wsm", :ts=>1401047190, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1403654258, :type=>"cms"}
{:from=>"drupal", :to=>nil, :ts=>1406511846, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1401047035, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1408192299, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1425649917, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1411866640, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1426616811, :type=>"cms"}|{:fro
{:from=>nil, :to=>"drupal", :ts=>1416574784, :type=>"cms"}|{:from=>
{:from=>"6.24", :to=>"6.28", :ts=>1381262550, :type=>"cms_version
{:from=>"wordpress", :to=>nil, :ts=>1384453278, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1437555797, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1413520038, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1382042788, :type=>"cms"}|{:fro
{:from=>nil, :to=>"wordpress", :ts=>1408339863, :type=>"cms"}|{:fro
events
Appendix 4 - Acquia Report
id subdomain root home-heinonline-org.ezproxy.library.wisc.edu home-heinonline-org.ezproxy.library wisc prelaw.ls.wisc.edu prelaw.ls wisc smrs.biostat.wisc.edu smrs.biostat wisc memorial.library.wisc.edu memorial.library wisc cfs.wisc.edu cfs wisc african.history.wisc.edu african.history wisc cfli.wisc.edu cfli wisc classics.lss.wisc.edu classics.lss wisc sysadm.aos.wisc.edu sysadm.aos wisc mbo.wisc.edu mbo wisc hep.wisc.edu hep wisc knovel.com.ezproxy.library.wisc.edu knovel.com.ezproxy.library wisc meritservices.education.wisc.edu meritservices.education wisc m.ebling.library.wisc.edu m.ebling.library wisc books.google.com.ezproxy.library.wisc.edu books.google.com.ezproxy.library wisc globalroadwarrior.com.ezproxy.library.wisc.ed globalroadwarrior.com.ezproxy.librarywisc hfes.rso.wisc.edu hfes.rso wisc students.commarts.wisc.edu students.commarts wisc oqi.wisc.edu oqi wisc canoe.slc.engr.wisc.edu canoe.slc.engr wisc wwwscout.cs.wisc.edu wwwscout.cs wisc arts.wisc.edu arts wisc volcano.ssec.wisc.edu volcano.ssec wisc rf-ablation.engr.wisc.edu rf-ablation.engr wisc login.uc.wisc.edu login.uc wisc medicaldevice.wisc.edu medicaldevice wisc ssfastar.services.wisc.edu ssfastar.services wisc events.icecube.wisc.edu events.icecube wisc bridge.library.wisc.edu bridge.library wisc asme.slc.engr.wisc.edu asme.slc.engr wisc wwwtest.center4design.wisc.edu wwwtest.center4design wisc microbiology.wisc.edu microbiology wisc peopleprogram.wisc.edu peopleprogram wisc experts.news.wisc.edu experts.news wisc cellnet2013.cs.wisc.edu cellnet2013.cs wisc www-clinicalkey-com.ezproxy.library.wisc.edu www-clinicalkey-com.ezproxy.library wisc bmrb.wisc.edu bmrb wisc officehours.polisci.wisc.edu officehours.polisci wisc library.law.wisc.edu library.law wisc cancer.wisc.edu cancer wisc epdweb.engr.wisc.edu epdweb.engr wisc ccas.wisc.edu ccas wisc eastasia.wisc.edu eastasia wisc recsports.wisc.edu recsports wisc mcburney.wisc.edu mcburney wisc lgbt.wisc.edu lgbt wisc hmongstudies.wisc.edu hmongstudies wisc visit.wisc.edu visit wisc conservation-training.wisc.edu conservation-training wisc eosweb.ssec.wisc.edu eosweb.ssec wisc amrc-new.ssec.wisc.edu amrc-new.ssec wisc myprofdev.wisc.edu myprofdev wisc msdisc.wisc.edu msdisc wisc wavesatseacaves.cee.wisc.edu wavesatseacaves.cee wisc account.library.wisc.edu account.library wisc images.library.wisc.edu images.library wisc wcrc.chsra.wisc.edu wcrc.chsra wisc vcru.wisc.edu vcru wisc aos.wisc.edu aos wisc tim.lss.wisc.edu tim.lss wisc wisdom.cs.wisc.edu wisdom.cs wisc dighum.wisc.edu dighum wisc directory.engr.wisc.edu directory.engr wisc transportation.wisc.edu transportation wisc quad.aos.wisc.edu quad.aos wisc wisccharge.wisc.edu wisccharge wisc redd.commarts.wisc.edu redd.commarts wisc licensing.wisc.edu licensing wisc herbarium.wisc.edu herbarium wisc seassi.wisc.edu seassi wisc ipib.wisc.edu ipib wisc nsec.wisc.edu nsec wisc medmicro.wisc.edu medmicro wisc av.aqua.wisc.edu av.aqua wisc conferences.library.wisc.edu conferences.library wisc morgridge.wisc.edu morgridge wisc myinfo.wisc.edu myinfo wisc pine.nmrfam.wisc.edu pine.nmrfam wisc fitness.pediatrics.wisc.edu fitness.pediatrics wisc library-new.law.wisc.edu library-new.law wisc ecow.engr.wisc.edu ecow.engr wisc knownissues.moodle.wisc.edu knownissues.moodle wisc aac.wisc.edu aac wisc webmail.neurology.wisc.edu webmail.neurology wisc pubs.bus.wisc.edu pubs.bus wisc kidspeech.waisman.wisc.edu kidspeech.waisman wisc narsn.commarts.wisc.edu narsn.commarts wisc dm-ice.physics.wisc.edu dm-ice.physics wisc mailman.cae.wisc.edu mailman.cae wisc blanchard.ep.wisc.edu blanchard.ep wisc pheno.wisc.edu pheno wisc limnology.wisc.edu limnology wisc www2.biotech.wisc.edu www2.biotech wisc my.research.wisc.edu my.research wisc mi.wisc.edu mi wisc vehicles.wisc.edu vehicles wisc russorch.wisc.edu russorch wisc corn.agronomy.wisc.edu corn.agronomy wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 13 of 19 apache
platform_ruby
php_5.2|platform_dotnet|platform_php
iis iis
platform_dotnet mobile|platform_dotnet
title
login.wisc.edu
patron.library.wisc.edu
redirect
iis iis
apache
login.wisc.edu
1985-09-30 00:00:00 -0400 welcome | de 1985-09-30 00:00:00 -0400 mobile ipv6 ipv6 platform_dotnet platform_dotnet|social_embed
1985-09-29 20:00:00 -0400 cae mailmankb.wisc.edu
apache
mobile ipv6
login.wisc.edu ecow2.engr.wisc.edu
digipub.library.wisc.edu
www.engr.wisc.edu
www.uwhealth.org
iis iis
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 Welcome | L 1985-09-30 00:00:00 -0400 wisdom
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
loginqa.wisc.edu
login.wisc.edu
1985-09-30 00:00:00 -0400 internet scouamser.org
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created
platform_dotnet mobile|platform_dotnet
mobile ipv6 php_5.4|platform_php|ipv6
iis
apache
platform_dotnet php_5.6|platform_php
php_5.3|platform_php
iis
iis
iis iis
iis
platform_dotnet
php_5.3|platform_php platform_dotnet platform_dotnet ipv6 mobile|platform_ruby
iis iis
apache
iis
apache
apache apache apache
apache
apache apache apache apache apache
apache apache
iis apache apache
apache apache apache iis apache iis apache apache iis apache
websrv
html5|mobile platform_dotnet html5|mobile|platform_dotnet
php_5.3|platform_dotnet|platform_php php_5.3|platform_php mobile|platform_java
mobile
platform_ruby
mobile|php_5.4|platform_php|social_embed|ipv6 mobile php_5.3|platform_php
php_5.3|platform_php mobile ipv6 php_5.3|platform_php html5|mobile php_5.3|platform_php ipv6 mobile ipv6 platform_java
mobile mobile|platform_dotnet mobile|php_5.5|platform_php mobile|platform_ruby mobile
platform_dotnet
content_embed|platform_dotnet
platform_dotnet|social_embed
features mobile
mobile Bluehost.co ipv6 platform_dotnet
cms_veprovider
dns_provid ip wisc.edu 128.104.46.200 wisc.edu 128.104.88.40 wisc.edu 144.92.73.188 wisc.edu 128.104.1.195 wisc.edu 128.104.80.225 wisc.edu 144.92.9.17 wisc.edu 128.104.81.249 wisc.edu 144.92.115.213 wisc.edu 144.92.131.142 wisc.edu 144.92.175.177 wisc.edu 128.104.28.26 wisc.edu 128.104.46.200 wisc.edu 144.92.146.69 wisc.edu 144.92.50.151 wisc.edu 128.104.46.219 wisc.edu 128.104.46.200 144.92.74.126 wisc.edu 144.92.226.67 128.104.1.207 wisc.edu 128.104.201.107 wisc.edu 144.92.170.202 wisc.edu 144.92.9.17 wisc.edu 128.104.108.131 wisc.edu 128.104.201.94 wisc.edu 128.104.1.207 wisc.edu 128.104.201.71 wisc.edu 144.92.9.99 wisc.edu 128.104.255.35 wisc.edu 128.104.1.195 wisc.edu 128.104.201.107 wisc.edu 128.104.1.202 wisc.edu 144.92.72.107 wisc.edu 144.92.239.230 wisc.edu 144.92.9.200 wisc.edu 128.105.7.114 wisc.edu 128.104.46.200 wisc.edu 144.92.217.20 wisc.edu 128.104.89.251 wisc.edu 128.104.94.54 wisc.edu 144.92.216.45 wisc.edu 144.92.225.235 wisc.edu 128.104.80.60 wisc.edu 128.104.23.170 wisc.edu 128.104.81.239 wisc.edu 128.104.81.77 wisc.edu 128.104.80.152 wisc.edu 128.104.23.170 wisc.edu 144.92.9.53 wisc.edu 144.92.93.169 wisc.edu 128.104.108.112 wisc.edu 128.104.109.32 wisc.edu 128.104.81.186 wisc.edu 144.92.66.151 wisc.edu 128.104.201.61 wisc.edu 128.104.46.149 wisc.edu 144.92.161.67 wisc.edu 144.92.156.41 wisc.edu 128.104.238.27 wisc.edu 144.92.131.146 wisc.edu 144.92.115.213 wisc.edu 128.105.7.94 wisc.edu 69.89.31.137 wisc.edu 128.104.201.59 wisc.edu 128.104.155.45 wisc.edu 144.92.131.155 wisc.edu 128.104.81.112 wisc.edu 144.92.226.62 wisc.edu 128.104.81.92 wisc.edu 144.92.9.17 wisc.edu 128.104.23.170 wisc.edu 128.104.116.47 wisc.edu 144.92.9.17 wisc.edu 144.92.72.104 wisc.edu 144.92.44.240 wisc.edu 144.92.161.74 wisc.edu 128.104.81.186 wisc.edu 128.104.81.26 wisc.edu 144.92.4.197 wisc.edu 144.92.221.86 wisc.edu 128.104.1.207 wisc.edu 128.104.201.96 wisc.edu 128.104.201.21 wisc.edu 128.104.81.220 wisc.edu 128.104.205.58 wisc.edu 144.92.212.18 wisc.edu 144.92.22.153 wisc.edu 144.92.226.62 wisc.edu 128.104.255.56 wisc.edu 128.104.22.180 wisc.edu 128.104.201.101 wisc.edu 128.104.160.19 wisc.edu 162.144.12.28 wisc.edu 144.92.52.86 wisc.edu 128.104.1.207 wisc.edu 128.104.201.94 wisc.edu 128.104.201.71 wisc.edu 128.104.23.170 wisc.edu 144.92.93.155 {:from=>nil, :to=>"7.32", :ts=>1422479927, :type=>"cms_version"}|{: {:from=>"SoftLayer", :to=>nil, :ts=>1382180903, :type=>"provider"}|{
{:from=>"drupal", :to=>nil, :ts=>1384971438, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1417560059, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1381418947, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1400277828, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401051100, :type=>"cms"}
{:from=>nil, :to=>"7.22", :ts=>1377026123, :type=>"cms_version"}|{: {:from=>"bluehost", :to=>"Bluehost.com", :ts=>1375986296, :type=> {:from=>nil, :to=>"opentext_wsm", :ts=>1401004195, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1407434028, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401046201, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1419951575, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1383823393, :type=>"cms"}|{:fro
{:from=>nil, :to=>"7.22", :ts=>1376046469, :type=>"cms_version"}|{: {:from=>nil, :to=>"opentext_wsm", :ts=>1426867343, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1406131373, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1408024343, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048134, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1403592891, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1415250535, :type=>"cms"}
events
Appendix 4 - Acquia Report
id subdomain root courses.engr.wisc.edu courses.engr wisc apps.union.wisc.edu apps.union wisc foodsecurity.wisc.edu foodsecurity wisc webtma-ls-1.housing.wisc.edu webtma-ls-1.housing wisc eastasia.history.wisc.edu eastasia.history wisc wcwpds.wisc.edu wcwpds wisc cmb.physics.wisc.edu cmb.physics wisc monitor.chtc.wisc.edu monitor.chtc wisc maps.sco.wisc.edu maps.sco wisc cable.doit.wisc.edu cable.doit wisc careers.vetmed.wisc.edu careers.vetmed wisc gers.engr.wisc.edu gers.engr wisc library.primate.wisc.edu library.primate wisc cccp.journalism.wisc.edu cccp.journalism wisc mosseprogram.wisc.edu mosseprogram wisc spiders.entomology.wisc.edu spiders.entomology wisc history.wisc.edu history wisc find.galegroup.com.ezproxy.library.wisc.edu find.galegroup.com.ezproxy.library wisc admin.today.wisc.edu admin.today wisc softmaterials.engr.wisc.edu softmaterials.engr wisc che.nelson.wisc.edu che.nelson wisc juis.global.wisc.edu juis.global wisc status.moodle.wisc.edu status.moodle wisc metj.engr.wisc.edu metj.engr wisc hebrew.wisc.edu hebrew wisc campusareahousing.wisc.edu campusareahousing wisc ohr.wisc.edu ohr wisc diversityplan2013.wisc.edu diversityplan2013 wisc qbi.wisc.edu qbi wisc mail.ortho.wisc.edu mail.ortho wisc tools.wiscwebcms.wisc.edu tools.wiscwebcms wisc menus.housing.wisc.edu menus.housing wisc geoscience.wisc.edu geoscience wisc tbp.slc.engr.wisc.edu tbp.slc.engr wisc ezproxy.library.wisc.edu ezproxy.library wisc w9yt.engr.wisc.edu w9yt.engr wisc wfabba.ssec.wisc.edu wfabba.ssec wisc geography.wisc.edu geography wisc ncra.wisc.edu ncra wisc narrativestructures.doit.wisc.edu narrativestructures.doit wisc firewalltraining.doit.wisc.edu firewalltraining.doit wisc management.engr.wisc.edu management.engr wisc asce.slc.engr.wisc.edu asce.slc.engr wisc facilities.fpm.wisc.edu facilities.fpm wisc jstor.org.ezproxy.library.wisc.edu jstor.org.ezproxy.library wisc delta.wisc.edu delta wisc crb.wisc.edu crb wisc www-atoms.physics.wisc.edu www-atoms.physics wisc mvta.engr.wisc.edu mvta.engr wisc csac.history.wisc.edu csac.history wisc ghapps.global.wisc.edu ghapps.global wisc grahamgroup.che.wisc.edu grahamgroup.che wisc botit.botany.wisc.edu botit.botany wisc remote2.hip.wisc.edu remote2.hip wisc webmail.medicine.wisc.edu webmail.medicine wisc classrooms.hslc.wisc.edu classrooms.hslc wisc hslc.wisc.edu hslc wisc planning.lic.wisc.edu planning.lic wisc library.wisc.edu.ezproxy.library.wisc.edu library.wisc.edu.ezproxy.library wisc mcrctest.journalism.wisc.edu mcrctest.journalism wisc rwjscholars.pophealth.wisc.edu rwjscholars.pophealth wisc agenda.hep.wisc.edu agenda.hep wisc today.wisc.edu today wisc iris.wisc.edu iris wisc researchguides.library.wisc.edu researchguides.library wisc guide.cfli.wisc.edu guide.cfli wisc disc.wisc.edu disc wisc uwsc.wisc.edu uwsc wisc wonders.physics.wisc.edu wonders.physics wisc metalib.wisconsin.edu.ezproxy.library.wisc.ed metalib.wisconsin.edu.ezproxy.librarywisc cancerbiology.wisc.edu cancerbiology wisc cio.wisc.edu cio wisc innovation.engr.wisc.edu innovation.engr wisc mcardle.wisc.edu mcardle wisc yess.housing.wisc.edu yess.housing wisc informaworld.com.ezproxy.library.wisc.edu informaworld.com.ezproxy.library wisc teosinte.wisc.edu teosinte wisc mrsec.wisc.edu mrsec wisc ahec.wisc.edu ahec wisc apply.mph.wisc.edu apply.mph wisc labs.medmicro.wisc.edu labs.medmicro wisc thedairylandinitiative.vetmed.wisc.edu thedairylandinitiative.vetmed wisc intranet.lss.wisc.edu intranet.lss wisc madison.isis.wisc.edu madison.isis wisc quality.wisc.edu quality wisc sites.google.wisc.edu sites.google wisc vote.asm.wisc.edu vote.asm wisc techstore.doit.wisc.edu techstore.doit wisc datn.wisc.edu datn wisc tandempress.wisc.edu tandempress wisc calendars.microscopy.wisc.edu calendars.microscopy wisc eucenter.wisc.edu eucenter wisc infra.doit.wisc.edu infra.doit wisc nature.com.ezproxy.library.wisc.edu nature.com.ezproxy.library wisc uconnect.wisc.edu uconnect wisc whirlwind.meteor.wisc.edu whirlwind.meteor wisc scholar.google.com.ezproxy.library.wisc.edu scholar.google.com.ezproxy.library wisc creeca.wisc.edu creeca wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Appendix 4 - Page 14 of 19 mobile
php_5.5|platform_php mobile
platform_dotnet ipv6 ipv6 platform_dotnet
mobile|platform_ruby platform_dotnet platform_dotnet ipv6 ipv6
ipv6
redirect
nelson.wisc.edu
patron.library.wisc.edu login.wisc.edu
patron.library.wisc.edu
diversityframework.wisc.edu
login.wisc.edu
patron.library.wisc.edu
www.med.wisc.edu
patron.library.wisc.edu
iis
1985-09-30 00:00:00 -0400
patron.library.wisc.edu
patron.library.wisc.edu
mobile|platform_ruby platform_dotnet|social_embed
www.doit.wisc.edu iis iis iis
www.google.com
platform_dotnet platform_dotnet platform_dotnet mobile|platform_ruby
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400 home | wisco
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
ncra.info 1985-09-30 00:00:00 -0400 narrative stru
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 department ocanes.wisc.edu
1985-09-30 00:00:00 -0400
google iis iis
iis
iis
iis
iis
title
1985-09-30 00:00:00 -0400 site off-line | www.engr.wisc.edu
domain_created
ipv6 platform_dotnet platform_dotnet mobile
platform_dotnet
html5|mobile platform_dotnet
platform_dotnet html5|mobile social_embed mobile|platform_ruby platform_dotnet content_embed|mobile|social_embed ipv6 platform_dotnet mobile mobile
iis apache
iis apache
iis
iis iis
apache
iis
platform_dotnet html5|mobile|php_5.5|platform_php ipv6 mobile|platform_ruby ipv6 ipv6
iis iis
platform_dotnet platform_dotnet
iis
nginx iis
iis
platform_dotnet ipv6
platform_dotnet mobile|platform_ruby mobile ipv6 mobile|php_5.6|platform_php platform_dotnet ipv6
iis
ipv6 mobile|platform_ruby platform_dotnet SoftLayer mobile
google
websrv iis iis iis
platform_dotnet ipv6
features php_5.4|platform_php|ipv6 platform_dotnet php_5.3|platform_dotnet|platform_php platform_dotnet
1&1 Interneplatform_php|social_embed
cms_veprovider
dns_provid ip wisc.edu 128.104.201.59 wisc.edu 128.104.80.31 wisc.edu 144.92.122.50 wisc.edu 128.104.175.130 wisc.edu 144.92.9.174 wisc.edu 128.104.81.186 wisc.edu 128.104.160.19 wisc.edu 128.105.244.16 wisc.edu 144.92.235.110 wisc.edu 144.92.67.153 wisc.edu 144.202.255.71 wisc.edu 128.104.201.59 wisc.edu 128.104.92.17 wisc.edu 144.92.22.140 wisc.edu 144.92.9.17 wisc.edu 144.92.198.22 wisc.edu 128.104.54.32 wisc.edu 128.104.46.219 wisc.edu 128.104.1.207 wisc.edu 128.104.201.59 wisc.edu 144.92.235.112 wisc.edu 128.104.23.170 wisc.edu 144.92.13.238 wisc.edu 144.92.225.235 wisc.edu 144.92.9.14 wisc.edu 128.104.81.186 wisc.edu 128.104.81.120 wisc.edu 144.92.9.17 wisc.edu 144.92.9.17 wisc.edu 128.104.140.138 wisc.edu 128.104.81.186 wisc.edu 144.92.27.202 wisc.edu 144.92.206.29 wisc.edu 128.104.201.107 wisc.edu 128.104.46.219 wisc.edu 128.104.201.59 wisc.edu 128.104.108.105 wisc.edu 144.92.235.115 wisc.edu 74.208.239.185 wisc.edu 128.104.144.187 wisc.edu 128.104.80.113 wisc.edu 144.92.225.235 wisc.edu 128.104.201.70 wisc.edu 144.92.9.17 wisc.edu 128.104.46.219 wisc.edu 128.104.81.186 wisc.edu 128.104.20.82 wisc.edu 128.104.160.19 wisc.edu 128.104.201.96 wisc.edu 144.92.9.17 wisc.edu 128.104.23.170 wisc.edu 128.104.201.62 wisc.edu 128.104.26.71 wisc.edu 128.104.140.162 wisc.edu 144.92.76.40 wisc.edu 144.92.50.139 wisc.edu 144.92.154.150 wisc.edu 144.92.119.36 wisc.edu 128.104.46.200 wisc.edu 144.92.22.140 wisc.edu 144.92.190.47 wisc.edu 128.104.28.14 wisc.edu 128.104.22.215 wisc.edu 128.104.23.170 wisc.edu 75.126.221.51 wisc.edu 144.92.9.17 wisc.edu 144.92.190.196 wisc.edu 144.92.239.202 wisc.edu 144.92.9.17 wisc.edu 128.104.46.219 wisc.edu 128.104.81.186 wisc.edu 128.104.80.141 wisc.edu 128.104.201.59 wisc.edu 128.104.81.186 wisc.edu 128.104.1.207 wisc.edu 128.104.46.200 wisc.edu 144.92.239.238 wisc.edu 144.92.9.17 wisc.edu 128.104.81.215 wisc.edu 144.92.201.167 wisc.edu 144.92.72.109 wisc.edu 128.104.212.194 wisc.edu 144.92.115.90 wisc.edu 144.92.201.250 wisc.edu 144.92.239.225 wisc.edu 216.58.209.164 wisc.edu 128.104.81.78 wisc.edu 144.92.74.21 wisc.edu 128.104.80.153 wisc.edu 144.92.146.16 wisc.edu 128.104.200.180 wisc.edu 128.104.23.170 wisc.edu 128.104.1.188 wisc.edu 128.104.46.219 wisc.edu 144.92.216.230 wisc.edu 144.92.131.212 wisc.edu 128.104.46.219 wisc.edu 128.104.23.170 {:from=>nil, :to=>"wordpress", :ts=>1406805288, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048625, :type=>"cms"} {:from=>nil, :to=>"google", :ts=>1389126164, :type=>"provider"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401125205, :type=>"cms"} {:from=>"7.13", :to=>"7.32", :ts=>1419968401, :type=>"cms_version
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048785, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1423515108, :type=>"cms"} {:from=>nil, :to=>"wordpress", :ts=>1417887090, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1403536599, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1395024413, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1410632734, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1413403469, :type=>"cms"}|{:fro
{:from=>"7.21", :to=>nil, :ts=>1391243175, :type=>"cms_version"}|{:
{:from=>nil, :to=>"wordpress", :ts=>1410499126, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401523221, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1420499411, :type=>"cms"}
{:from=>"6.28", :to=>nil, :ts=>1441904249, :type=>"cms_version"}|{:
{:from=>nil, :to=>"wordpress", :ts=>1411466351, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401358492, :type=>"cms"}
{:from=>"6.25", :to=>nil, :ts=>1413927709, :type=>"cms_version"}|{:
events
Appendix 4 - Acquia Report
id outages.doit.wisc.edu greenlab.psych.wisc.edu wiki.genetics.wisc.edu cycleforsight.wisc.edu apps.cals.wisc.edu status.cae.wisc.edu veterans.wisc.edu omai.wisc.edu future.aae.wisc.edu oeo.engr.wisc.edu vc.wisc.edu asm.uwsc.wisc.edu coestudentshop.engr.wisc.edu acct.aae.wisc.edu scholarships.wisc.edu uwcreate.engr.wisc.edu jbrche.wisc.edu parenthood.library.wisc.edu diversityframework.wisc.edu mmb.bme.wisc.edu metaframe.uwmf.wisc.edu dblife.cs.wisc.edu rarc.wisc.edu aae.wisc.edu aix50years.wisc.edu midus.wisc.edu uhs.wisc.edu wiki.physics.wisc.edu nrotc.wisc.edu itg1.meteor.wisc.edu masterplan.wisc.edu sasli.wisc.edu cibm.wisc.edu med.wisc.edu sysadm.meteor.wisc.edu helios.meteor.wisc.edu cae.ls.wisc.edu epdcoursematerials.engr.wisc.edu def.my.cae.wisc.edu link.springer.com.ezproxy.library.wisc.edu finaid.wisc.edu mail.bmrb.wisc.edu rdc.wisc.edu glacier.sage.wisc.edu tusal.cee.wisc.edu didnt.doit.wisc.edu ice.ssec.wisc.edu mel.wisc.edu ncbi.nlm.nih.gov.ezproxy.library.wisc.edu seniorlearning.wisc.edu registrar.wisc.edu bugs.icecube.wisc.edu reic.uwcc.wisc.edu ssec.wisc.edu cpam.engr.wisc.edu trflp.limnology.wisc.edu sts.doit.wisc.edu pims.fammed.wisc.edu eao.wisc.edu forms.bus.wisc.edu wts.wisc.edu library.ems.wisc.edu cx.engr.wisc.edu mki.wisc.edu tv.wisc.edu uwpreschoollab.wisc.edu bacter.wisc.edu badgerskydivingclub.rso.wisc.edu mandm.engr.wisc.edu ediphy.wisc.edu cmestreaming.pediatrics.wisc.edu ieee.slc.engr.wisc.edu software.wisc.edu mycourseguide.wisc.edu emeraldinsight.com.ezproxy.library.wisc.edu subbook.college.library.wisc.edu fri.wisc.edu wcam.engr.wisc.edu legalinformationcenter.rso.wisc.edu winstreamer.doit.wisc.edu api.library.wisc.edu upl.cs.wisc.edu jira.doit.wisc.edu datasearch.limnology.wisc.edu sunbeam.ece.wisc.edu dairy.wisc.edu uwservice.wisc.edu lcnl.wisc.edu policy-weaving.cs.wisc.edu so.engr.wisc.edu hum.lss.wisc.edu das.doit.wisc.edu forms.my.cae.wisc.edu study.uwsc.wisc.edu asap.ahabs.wisc.edu ce.vetmed.wisc.edu helpdesk.doit.wisc.edu admin.login.wisc.edu
subdomain outages.doit greenlab.psych wiki.genetics cycleforsight apps.cals status.cae veterans omai future.aae oeo.engr vc asm.uwsc coestudentshop.engr acct.aae scholarships uwcreate.engr jbrwww.che parenthood.library diversityframework mmb.bme metaframe.uwmf dblife.cs rarc aae aix50years midus uhs wiki.physics nrotc itg1.meteor masterplan sasli cibm med sysadm.meteor helios.meteor cae.ls epdcoursematerials.engr def.my.cae link.springer.com.ezproxy.library finaid mail.bmrb rdc glacier.sage tusal.cee didnt.doit ice.ssec mel ncbi.nlm.nih.gov.ezproxy.library seniorlearning registrar bugs.icecube reic.uwcc ssec cpam.engr trflp.limnology sts.doit pims.fammed eao forms.bus wts library.ems cx.engr mki tv uwpreschoollab bacter badgerskydivingclub.rso mandm.engr ediphy cmestreaming.pediatrics ieee.slc.engr software mycourseguide emeraldinsight.com.ezproxy.library subbook.college.library fri wcam.engr legalinformationcenter.rso winstreamer.doit api.library upl.cs jira.doit datasearch.limnology sunbeam.ece dairy uwservice lcnl policy-weaving.cs so.engr hum.lss das.doit forms.my.cae study.uwsc asap.ahabs ce.vetmed helpdesk.doit admin.login
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
PEER 1
cms_veprovider
Appendix 4 - Page 15 of 19 mobile php_5.3|platform_php
php_5.5|platform_php
social_embed mobile|php_5.4|platform_php|ipv6
mobile|platform_php php_5.2|platform_php php_5.4|platform_php php_5.4|platform_php|ipv6
mobile html5|mobile|platform_php platform_java platform_java
mobile
platform_dotnet
mobile platform_dotnet
php_5.4|platform_php|ipv6 platform_dotnet
ipv6 platform_dotnet php_5.3|platform_php platform_dotnet mobile content_embed|html5|mobile|platform_dotnet social_embed|social_media_like php_5.3|platform_php platform_dotnet ipv6 ipv6 platform_java platform_dotnet html5|mobile|platform_ruby
platform_dotnet
ipv6 mobile|platform_ruby
mobile
html5|mobile|social_embed platform_dotnet
mobile|platform_ruby platform_dotnet platform_dotnet php_5.4|platform_php social_embed ipv6
ipv6
apache apache
coyote apache apache apache apache apache apache apache apache apache apache apache
apache
apache apache apache apache
apache iis apache apache apache iis apache iis apache apache
iis
iis
apache iis
iis
iis
iis
iis
iis
apache
iis ssws
iis iis
iis
php_5.4|platform_php|ipv6 mobile mobile|social_embed|social_media_like php_5.4|platform_php|ipv6 ipv6
iis
php_5.3|platform_php ipv6 platform_dotnet
websrv iis
ipv6 html5|mobile|platform_dotnet
html5|mobile
features mobile|platform_dotnet content_embed
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created
title
kb.wisc.edu www.wisc.edu
wayf.wisconsin.edu
login.wisc.edu
public.my.wisc.edu
www.pediatrics.wisc.edu win.wisc.edu
www.doit.wisc.edu
epdweb.engr.wisc.edu
secure.limnology.wisc.edu
continuingstudies.wisc.edu
lists.bmrb.wisc.edu
patron.library.wisc.edu
ag.uwmf.wisc.edu
login.wisc.edu
epdweb.engr.wisc.edu
vision.wisc.edu
redirect
dns_provid ip wisc.edu 144.92.9.241 wisc.edu 144.92.9.17 wisc.edu 144.92.162.45 wisc.edu 144.92.9.62 wisc.edu 144.92.93.194 wisc.edu 144.92.12.39 wisc.edu 128.104.81.186 wisc.edu 144.92.239.198 wisc.edu 144.92.93.150 wisc.edu 144.92.225.235 144.92.174.65 wisc.edu 144.92.239.201 wisc.edu 128.104.201.59 wisc.edu 128.104.1.207 wisc.edu 128.104.31.87 wisc.edu 128.104.201.59 wisc.edu 128.104.201.99 wisc.edu 144.92.161.31 wisc.edu 144.92.9.17 wisc.edu 128.104.201.60 wisc.edu 144.92.250.64 wisc.edu 128.105.121.60 wisc.edu 144.92.217.160 wisc.edu 144.92.122.14 wisc.edu 128.104.23.170 wisc.edu 144.92.62.126 wisc.edu 128.104.72.43 wisc.edu 128.104.164.218 wisc.edu 144.92.9.35 wisc.edu 144.92.131.143 wisc.edu 144.92.9.17 wisc.edu 128.104.23.170 wisc.edu 65.39.205.54 wisc.edu 144.92.154.150 wisc.edu 144.92.131.142 wisc.edu 144.92.130.157 wisc.edu 144.92.9.17 wisc.edu 144.92.225.236 wisc.edu 128.104.201.110 wisc.edu 128.104.46.219 wisc.edu 128.104.80.248 wisc.edu 144.92.167.220 wisc.edu 144.92.122.14 wisc.edu 144.92.10.160 wisc.edu 128.104.201.61 wisc.edu 128.104.18.35 wisc.edu 128.104.109.32 wisc.edu 128.104.20.62 wisc.edu 128.104.46.200 wisc.edu 128.104.155.42 wisc.edu 128.104.81.220 wisc.edu 128.104.255.52 wisc.edu 144.92.122.14 wisc.edu 128.104.108.105 wisc.edu 128.104.201.59 wisc.edu 144.92.62.252 wisc.edu 128.104.80.232 wisc.edu 144.92.41.104 wisc.edu 144.92.9.132 wisc.edu 144.92.212.43 wisc.edu 144.92.13.148 wisc.edu 144.92.104.126 wisc.edu 144.92.225.235 wisc.edu 144.92.115.213 128.104.80.153 128.104.80.225 128.104.116.0 144.92.74.126 wisc.edu 128.104.184.243 wisc.edu 144.92.146.121 wisc.edu 144.92.221.86 wisc.edu 208.83.125.253 wisc.edu 128.104.80.86 wisc.edu 144.92.197.135 wisc.edu 128.104.46.200 wisc.edu 144.92.22.51 wisc.edu 144.92.49.96 wisc.edu 128.104.201.59 144.92.74.0 wisc.edu 144.92.74.252 wisc.edu 128.104.1.207 wisc.edu 128.105.45.17 wisc.edu 144.92.197.201 144.92.62.252 wisc.edu 128.104.201.100 wisc.edu 144.92.122.188 wisc.edu 128.104.80.38 wisc.edu 128.104.130.59 wisc.edu 128.105.7.34 wisc.edu 128.104.201.59 wisc.edu 144.92.115.213 wisc.edu 144.92.194.22 wisc.edu 128.104.201.111 wisc.edu 144.92.239.200 wisc.edu 144.92.136.13 wisc.edu 128.104.212.119 wisc.edu 128.104.22.180 wisc.edu 128.104.1.223
events
{:from=>nil, :to=>"opentext_wsm", :ts=>1406142711, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401045645, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1411751645, :type=>"cms"}|{:fro {:from=>nil, :to=>"opentext_wsm", :ts=>1401045625, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401011297, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1403702522, :type=>"cms"}
{:from=>"sharepoint", :to=>nil, :ts=>1404158820, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1406039225, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1409179555, :type=>"cms"} {:from=>"wordpress", :to=>nil, :ts=>1442909304, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1422057571, :type=>"cms"}
Appendix 4 - Acquia Report
id uwits.slc.engr.wisc.edu ct.wisc.edu quickstep.cs.wisc.edu microbes.wisc.edu continuingstudies-stage.aims.wisc.edu custportal.wvdl.wisc.edu live.videos.med.wisc.edu academic.son.wisc.edu corprelations.wisc.edu pw.hip.wisc.edu home.physics.wisc.edu vdw.ece.wisc.edu lubar.wisc.edu morrow.ece.wisc.edu students.med.wisc.edu csp.ece.wisc.edu pacsy.nmrfam.wisc.edu ersc.ssec.wisc.edu test5.education.wisc.edu msbshop.wisc.edu unionsouth2.doit.wisc.edu cgi.cae.wisc.edu art.library.wisc.edu dermatology.wisc.edu hecc.wisc.edu apps.mbo.wisc.edu tools.advising.wisc.edu ieeerobo.slc.engr.wisc.edu kalinlab.psychiatry.wisc.edu imp.lss.wisc.edu musicraceempire.global.wisc.edu msep.engr.wisc.edu socialwork.library.wisc.edu bmes.slc.engr.wisc.edu lists.discovery.wisc.edu remote.neurology.wisc.edu maps.wisc.edu foodsystems.wisc.edu arcat.library.wisc.edu uwictr.wisc.edu xray.chem.wisc.edu attie.wisc.edu uas.ls.wisc.edu mnsa.ece.wisc.edu amsu.ssec.wisc.edu swe.slc.engr.wisc.edu exams.wisc.edu nmrfam.wisc.edu garagecam.engr.wisc.edu myuhs.uhs.wisc.edu support.doit.wisc.edu research.cs.wisc.edu amrc.ssec.wisc.edu intl-institute.wisc.edu searchwisconsinidea.wisc.edu ruralenergy.wisc.edu eadc.engr.wisc.edu advising.ls.wisc.edu match.wisc.edu physiology.wisc.edu neuro.wisc.edu neurophys.wisc.edu stratos.cs.wisc.edu sas.college.library.wisc.edu kb.doit.wisc.edu international.engr.wisc.edu polisci.wisc.edu wcws.cals.wisc.edu iec.neep.wisc.edu biotron.wisc.edu ojnoer.ars.wisc.edu westmadison.ars.wisc.edu wmsserv2.ssec.wisc.edu lib.uchicago.edu.ezproxy.library.wisc.edu regics.athletics.wisc.edu bas.wisc.edu cow.waisman.wisc.edu net.doit.wisc.edu irp.wisc.edu occfr.wisc.edu nesstar.ssc.wisc.edu admin.lists.wisc.edu weedid.wisc.edu dpls.dacc.wisc.edu portal.isis.wisc.edu iaeste.slc.engr.wisc.edu mediasite.cae.wisc.edu strata.geology.wisc.edu sage.wisc.edu flux.aos.wisc.edu coastal.lic.wisc.edu plasma.physics.wisc.edu supportthebadgers.athletics.wisc.edu wsum.wisc.edu intranet.housing.wisc.edu yearofthearts.wisc.edu vep-test.cs.wisc.edu demo1.physics.wisc.edu
subdomain uwits.slc.engr ct quickstep.cs microbes continuingstudies-stage.aims custportal.wvdl live.videos.med academic.son corprelations pw.hip home.physics vdw.ece lubar morrow.ece students.med csp.ece pacsy.nmrfam ersc.ssec test5.education msbshop unionsouth2.doit cgi.cae art.library dermatology hecc apps.mbo tools.advising ieeerobo.slc.engr kalinlab.psychiatry imp.lss musicraceempire.global msep.engr socialwork.library bmes.slc.engr lists.discovery remote.neurology maps foodsystems arcat.library uwictr xray.chem attie uas.ls mnsa.ece amsu.ssec swe.slc.engr exams nmrfam garagecam.engr myuhs.uhs support.doit research.cs amrc.ssec intl-institute searchwisconsinidea ruralenergy eadc.engr advising.ls match physiology neuro neurophys stratos.cs sas.college.library kb.doit international.engr polisci wcws.cals iec.neep biotron ojnoer.ars westmadison.ars wmsserv2.ssec lib.uchicago.edu.ezproxy.library regics.athletics bas cow.waisman net.doit irp occfr nesstar.ssc admin.lists weedid dpls.dacc portal.isis iaeste.slc.engr mediasite.cae strata.geology sage flux.aos coastal.lic plasma.physics supportthebadgers.athletics wsum intranet.housing yearofthearts vep-test.cs demo1.physics
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
platform_dotnet platform_ruby php_5.3|platform_dotnet|platform_php
php_5.4|platform_php|ipv6
platform_dotnet ipv6
social_embed|ipv6 platform_dotnet
html5|mobile|platform_dotnet platform_dotnet platform_dotnet
ipv6
php_5.3|platform_php|ipv6
php_5.4|platform_php|ipv6
ipv6
platform_dotnet platform_dotnet ipv6 ipv6
mobile html5|mobile|platform_dotnet platform_java mobile|platform_ruby
features social_embed|social_media_like|ipv6 mobile
Appendix 4 - Page 16 of 19
title
ipv6
arts.wisc.edu
www.disc.wisc.edu
login.wisc.edu
www.doit.wisc.edu
kb.wisc.edu
iris.wisc.edu
kb.wisc.edu
tropic.ssec.wisc.edu
saa.ls.wisc.edu
www.engr.wisc.edu
www.wisconsinrobotics.org
www.mhdtg.net
login.wisc.edu
redirect
php_5.3|platform_php content_embed|mobile|platform_dotnet|social_embed|so iis platform_dotnet iis platform_dotnet iis apache
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 uw ictr, your
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created
nelson.wisc.edu
iis apache
apache iis
coyote
iis
iis
iis iis iis iis
iis
iis
iis
apache apache apache apache
apache apache iis iis iis apache apache apache apache iis apache apache apache apache iis apache iis apache
apache
iis coyote apache apache iis iis apache apache apache apache apache apache apache apache
apache
websrv apache
mobile|php_5.6|platform_php
mobile php_5.3|platform_php platform_dotnet platform_java php_5.4|platform_php|ipv6 platform_dotnet
mobile|ipv6 social_embed content_embed|social_embed
php_5.4|platform_php|ipv6 platform_dotnet php_5.3|platform_php php_5.4|platform_php|ipv6 html5|mobile php_5.3|platform_php php_5.3|platform_php mobile|php_5.3|platform_php mobile platform_dotnet
platform_dotnet platform_dotnet platform_dotnet platform_dotnet php_5.4|platform_php
php_5.3|platform_php platform_dotnet html5|php_5.3|platform_php platform_dotnet ipv6
ipv6 platform_dotnet
ipv6 ipv6 php_5.4|platform_php|social_media_like|ipv6
php_5.3|platform_php
Pantheon varnish
Weebly
cms_veprovider
dns_provid ip wisc.edu 128.104.201.70 wisc.edu 128.104.1.207 wisc.edu 128.105.7.143 wisc.edu 216.185.153.132 wisc.edu 128.104.155.53 wisc.edu 128.104.246.51 wisc.edu 144.92.50.109 wisc.edu 144.92.223.20 wisc.edu 128.104.64.28 wisc.edu 128.104.140.157 wisc.edu 128.104.160.19 wisc.edu 128.104.201.100 wisc.edu 144.92.115.213 wisc.edu 128.104.201.63 144.92.50.0 wisc.edu 128.104.201.63 wisc.edu 144.92.4.197 wisc.edu 128.104.108.105 wisc.edu 144.92.146.55 wisc.edu 144.92.49.111 128.104.156.0 wisc.edu 128.104.201.95 wisc.edu 128.104.1.195 wisc.edu 128.104.81.186 wisc.edu 144.92.122.14 wisc.edu 128.104.80.87 wisc.edu 144.92.9.119 wisc.edu 199.34.228.57 wisc.edu 144.92.177.178 wisc.edu 144.92.115.213 wisc.edu 128.104.23.170 wisc.edu 128.104.201.59 wisc.edu 128.104.1.195 wisc.edu 128.104.201.70 wisc.edu 128.104.153.90 wisc.edu 128.104.205.114 wisc.edu 144.92.9.186 wisc.edu 144.92.122.50 wisc.edu 144.92.11.52 wisc.edu 104.130.103.106 wisc.edu 128.104.71.108 wisc.edu 128.104.116.207 wisc.edu 144.92.9.17 wisc.edu 128.104.201.63 wisc.edu 128.104.108.131 wisc.edu 128.104.201.70 wisc.edu 128.104.80.55 wisc.edu 144.92.9.17 wisc.edu 128.104.201.96 wisc.edu 128.104.72.15 wisc.edu 128.104.22.180 wisc.edu 128.105.7.58 wisc.edu 128.104.109.32 wisc.edu 128.104.23.170 wisc.edu 144.92.9.200 wisc.edu 96.31.33.51 wisc.edu 128.104.201.59 wisc.edu 128.104.88.40 wisc.edu 144.92.156.45 wisc.edu 128.104.21.151 wisc.edu 128.104.20.45 wisc.edu 128.104.21.149 wisc.edu 128.105.7.118 wisc.edu 144.92.22.51 wisc.edu 128.104.22.180 wisc.edu 128.104.201.59 wisc.edu 128.104.81.186 wisc.edu 144.92.93.172 wisc.edu 128.104.201.106 wisc.edu 128.104.81.92 wisc.edu 144.92.93.172 wisc.edu 144.92.93.172 wisc.edu 128.104.111.37 wisc.edu 128.104.46.200 wisc.edu 144.92.104.126 wisc.edu 128.104.80.52 wisc.edu 144.92.138.7 wisc.edu 128.104.80.153 wisc.edu 144.92.190.47 wisc.edu 128.104.81.92 wisc.edu 144.92.190.124 wisc.edu 128.104.1.207 wisc.edu 144.92.93.172 wisc.edu 144.92.190.196 wisc.edu 144.92.9.98 wisc.edu 128.104.201.107 wisc.edu 144.92.12.152 wisc.edu 144.92.206.80 wisc.edu 144.92.235.112 wisc.edu 144.92.131.157 wisc.edu 144.92.119.50 wisc.edu 128.104.165.246 wisc.edu 144.92.38.114 wisc.edu 128.104.81.186 wisc.edu 128.104.56.33 wisc.edu 144.92.9.17 wisc.edu 128.105.7.86 wisc.edu 128.104.160.19 {:from=>nil, :to=>"opentext_wsm", :ts=>1404981951, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1418233633, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1426726470, :type=>"cms"}
{:from=>nil, :to=>"websphere_portal", :ts=>1384267915, :type=>"cm
{:from=>"wordpress", :to=>"opentext_wsm", :ts=>1405691690, :type
{:from=>nil, :to=>"opentext_wsm", :ts=>1402846500, :type=>"cms"}
{:from=>"6.22", :to=>"6.28", :ts=>1376046349, :type=>"cms_version
{:from=>"joomla", :to=>nil, :ts=>1376057232, :type=>"cms"}|{:from=
{:from=>nil, :to=>"Weebly", :ts=>1430450806, :type=>"provider"}|{:fr {:from=>"wordpress", :to=>nil, :ts=>1421531623, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1400433088, :type=>"cms"}
{:from=>nil, :to=>"sitefinity", :ts=>1380699730, :type=>"cms"}|{:from
{:from=>"wordpress", :to=>nil, :ts=>1374083299, :type=>"cms"}|{:fro
events
Appendix 4 - Acquia Report
id subdomain root wiscamp.engr.wisc.edu wiscamp.engr wisc profhorn.meteor.wisc.edu profhorn.meteor wisc epcs.education.wisc.edu epcs.education wisc my.pathology.wisc.edu my.pathology wisc tempest.aos.wisc.edu tempest.aos wisc apps.iss.wisc.edu apps.iss wisc scandinavian.wisc.edu scandinavian wisc wwwtest.biglearningevent.wisc.edu wwwtest.biglearningevent wisc inst.bact.wisc.edu inst.bact wisc remote.engr.wisc.edu remote.engr wisc nbp.wisc.edu nbp wisc environment.engr.wisc.edu environment.engr wisc msee.engr.wisc.edu msee.engr wisc batfish.bmrb.wisc.edu batfish.bmrb wisc wihivpts.wisc.edu wihivpts wisc metobs.ssec.wisc.edu metobs.ssec wisc archinte.jamanetwork.com.ezproxy.library.wis archinte.jamanetwork.com.ezproxy.li wisc marrella.meteor.wisc.edu marrella.meteor wisc rsp.wisc.edu rsp wisc pdo.son.wisc.edu pdo.son wisc scifun.chem.wisc.edu scifun.chem wisc chess2.wisc.edu chess2 wisc english.wisc.edu english wisc careers.ls.wisc.edu careers.ls wisc hosted.law.wisc.edu hosted.law wisc mail.ansci.wisc.edu mail.ansci wisc vanhise.lss.wisc.edu vanhise.lss wisc testing.exams.wisc.edu testing.exams wisc meteor.wisc.edu meteor wisc facerec.ece.wisc.edu facerec.ece wisc ieeexplore.ieee.org.ezproxy.library.wisc.edu ieeexplore.ieee.org.ezproxy.library wisc wwwtest.ecohealth.wisc.edu wwwtest.ecohealth wisc exed.wisc.edu exed wisc smph.ems.wisc.edu smph.ems wisc sbdc.wisc.edu sbdc wisc urology.wisc.edu urology wisc pogo.public.ssc.wisc.edu pogo.public.ssc wisc mquery.library.wisc.edu mquery.library wisc discovery.wisc.edu discovery wisc catalog.dcs.wisc.edu catalog.dcs wisc wisflora.herbarium.wisc.edu wisflora.herbarium wisc photos.limnology.wisc.edu photos.limnology wisc citrix.uwmf.wisc.edu citrix.uwmf wisc media.med.wisc.edu media.med wisc csportal.engr.wisc.edu csportal.engr wisc students.housing.wisc.edu students.housing wisc mars.housing.wisc.edu mars.housing wisc csd.wisc.edu csd wisc indiainitiative.wisc.edu indiainitiative wisc helios.aos.wisc.edu helios.aos wisc wifel.wisc.edu wifel wisc wwwtest.engr.wisc.edu wwwtest.engr wisc globalcultures.wisc.edu globalcultures wisc scientificteaching.wisc.edu scientificteaching wisc infosapostles.cee.wisc.edu infosapostles.cee wisc nso.wisc.edu nso wisc reda.aae.wisc.edu reda.aae wisc helpdesk.wisc.edu helpdesk wisc my.wisc.edu my wisc apr.wisc.edu apr wisc eosdb.ssec.wisc.edu eosdb.ssec wisc helpdesk.neurology.wisc.edu helpdesk.neurology wisc map.wisc.edu map wisc aiaa.slc.engr.wisc.edu aiaa.slc.engr wisc ems.smph.wisc.edu ems.smph wisc elections.wisc.edu elections wisc creativewriting.wisc.edu creativewriting wisc tutorials.ece.wisc.edu tutorials.ece wisc opennf.cs.wisc.edu opennf.cs wisc sesame.wisc.edu sesame wisc molpharm.wisc.edu molpharm wisc pats.wisc.edu pats wisc experts.wisc.edu experts wisc biopreview.wisc.edu biopreview wisc india.wisc.edu india wisc intranet.med.wisc.edu intranet.med wisc africafocus.library.wisc.edu africafocus.library wisc nboinc.chem.wisc.edu nboinc.chem wisc dairynutrient.wisc.edu dairynutrient wisc wms.ssec.wisc.edu wms.ssec wisc anthropology.wisc.edu anthropology wisc apps.parent.wisc.edu apps.parent wisc currielab.wisc.edu currielab wisc www-refworks-com.ezproxy.library.wisc.edu www-refworks-com.ezproxy.library wisc whirlwind.aos.wisc.edu whirlwind.aos wisc marrella.aos.wisc.edu marrella.aos wisc depd.wisc.edu depd wisc m.wisc.edu m wisc ecrt.wisc.edu ecrt wisc wisdm2.doit.wisc.edu wisdm2.doit wisc bmj.com.ezproxy.library.wisc.edu bmj.com.ezproxy.library wisc campbadger.engr.wisc.edu campbadger.engr wisc womenstudies.wisc.edu womenstudies wisc sdn.cs.wisc.edu sdn.cs wisc artsoutreach.wisc.edu artsoutreach wisc secfac.wisc.edu secfac wisc infosportwashington.cee.wisc.edu infosportwashington.cee wisc net.ophth.wisc.edu net.ophth wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
iis
iis iis
platform_dotnet ipv6 mobile|platform_ruby
social_embed|social_media_like platform_dotnet social_embed
html5|platform_dotnet platform_dotnet html5|platform_dotnet content_embed|platform_ruby
ipv6 mobile|platform_ruby
Appendix 4 - Page 17 of 19 html5|mobile|platform_dotnet ipv6 mobile|ipv6
mobile|platform_ruby
content_embed|platform_dotnet mobile|php_5.3|platform_php
php_5.1|platform_php mobile|php_5.3|platform_php php_5.6|platform_dotnet|platform_php mobile|platform_dotnet social_embed mobile
ipv6 content_embed|php_5.4|platform_php platform_dotnet WebsiteWehtml5|mobile platform_dotnet mobile platform_dotnet platform_dotnet
platform_ruby ipv6 platform_dotnet social_embed
ipv6 php_5.4|platform_php|social_embed|ipv6 html5|platform_dotnet mobile mobile
iis
apache
iis
iis
iis iis
iis iis
iis apache iis
iis
iis
iis
iis
platform_dotnet ipv6 platform_dotnet
apache
platform_dotnet
mobile php_5.4|platform_php|ipv6 html5|mobile html5|mobile
iis iis
iis iis iis
apache
iis
iis
platform_dotnet
php_5.2|platform_php platform_dotnet
iis iis
websrv
mobile|platform_dotnet
features php_5.4|platform_php|ipv6
platform_dotnet platform_dotnet php_5.5|platform_php CloudFlare cloudflare
cms_veprovider
title
redirect
dns_provid ip wisc.edu 128.104.201.59 wisc.edu 144.92.131.143 careers.education.wisc.edu wisc.edu 144.92.146.188 wisc.edu 144.92.28.60 wisc.edu 144.92.131.211 wisc.edu 128.104.81.186 1985-09-30 00:00:00 -0400 welcome, | d wisc.edu 144.92.9.17 wisc.edu 128.104.81.99 wisc.edu 144.92.239.46 wisc.edu 144.92.12.46 wisc.edu 144.92.9.200 wisc.edu 144.92.225.235 distancedegrees.engr.wisc.edu wisc.edu 144.92.225.235 wisc.edu 144.92.217.24 wisc.edu 128.104.80.225 wisc.edu 128.104.108.105 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 144.92.130.140 wisc.edu 128.104.147.237 wisc.edu 144.92.223.20 wisc.edu 128.104.70.177 wisc.edu 128.104.190.65 1985-09-30 00:00:00 -0400 wisc.edu 128.104.80.49 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 wisc.edu 128.104.94.99 wisc.edu 144.92.75.13 wisc.edu 144.92.115.213 128.104.149.177 wisc.edu 144.92.131.146 wisc.edu 128.104.201.100 1985-09-30 00:00:00 -0400 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 144.92.239.164 bus.wisc.edu wisc.edu 144.92.212.43 wisc.edu 144.92.104.126 bus.wisc.edu wisc.edu 144.92.212.43 wisc.edu 128.104.84.90 wisc.edu 144.92.158.8 wisc.edu 128.104.46.222 wisc.edu 23.96.32.128 wisc.edu 128.104.80.163 wisc.edu 144.92.166.198 wisc.edu 198.41.209.116 ag.uwmf.wisc.edu wisc.edu 144.92.250.64 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 wisc.edu 128.104.201.96 www.housing.wisc.edu wisc.edu 128.104.81.174 www.housing.wisc.edu wisc.edu 128.104.81.174 wisc.edu 128.104.80.37 wisc.edu 128.104.23.170 wisc.edu 144.92.130.157 144.92.249.231 1985-09-30 00:00:00 -0400 wisc.edu 128.104.201.59 wisc.edu 128.104.23.170 wisc.edu 144.92.111.199 wisc.edu 128.104.201.61 wisc.edu 128.104.201.71 wisc.edu 144.92.122.14 kb.wisc.edu wisc.edu 128.104.22.180 login.wisc.edu wisc.edu 128.104.1.207 1985-09-30 00:00:00 -0400 wisc.edu 144.92.9.17 eosweb.ssec.wisc.edu wisc.edu 128.104.108.112 1985-09-30 00:00:00 -0400 department o wisc.edu 128.104.205.139 wisc.edu 144.92.9.186 wisc.edu 128.104.201.107 smph.ems.wisc.edu wisc.edu 144.92.104.126 wisc.edu 144.92.158.36 wisc.edu 128.104.80.71 wisc.edu 128.104.201.100 wisc.edu 128.105.7.144 wisc.edu 144.92.4.138 wisc.edu 192.185.90.3 wisc.edu 144.92.122.14 login.wisc.edu wisc.edu 128.104.1.207 1985-09-30 00:00:00 -0400 biosciences wisc.edu 144.92.238.12 wisc.edu 128.104.23.170 wisc.edu 144.92.154.151 uwdc.library.wisc.edu wisc.edu 128.104.1.195 wisc.edu 128.104.71.14 wisc.edu 144.92.193.241 realearth.ssec.wisc.edu wisc.edu 128.104.111.3 wisc.edu 144.92.190.194 wisc.edu 128.104.80.148 wisc.edu 144.92.49.118 wisc.edu 128.104.46.200 wisc.edu 144.92.131.212 wisc.edu 144.92.130.140 continuingstudies.wisc.edu wisc.edu 128.104.155.42 wisc.edu 144.92.9.137 wayf.wisconsin.edu wisc.edu 144.92.197.201 wayf.wisconsin.edu wisc.edu 144.92.197.201 patron.library.wisc.edu wisc.edu 128.104.46.219 wisc.edu 144.92.225.235 wisc.edu 128.104.81.18 wisc.edu 128.105.7.111 wisc.edu 144.92.146.16 wisc.edu 128.104.81.186 wisc.edu 128.104.201.61 login.ophth.wisc.edu wisc.edu 128.104.254.110
domain_created
{:from=>nil, :to=>"wordpress", :ts=>1430500608, :type=>"cms"}|{:fro
{:from=>nil, :to=>"oraclewebcenter", :ts=>1382042776, :type=>"cms
{:from=>"6.18", :to=>nil, :ts=>1391250759, :type=>"cms_version"}|{:
{:from=>nil, :to=>"WebsiteWelcome.com", :ts=>1418777994, :type=
{:from=>nil, :to=>"drupal", :ts=>1420099517, :type=>"cms"}|{:from=>
{:from=>nil, :to=>"opentext_wsm", :ts=>1401051166, :type=>"cms"}
{:from=>"opentext_websolutions", :to=>nil, :ts=>1375976142, :type=
{:from=>nil, :to=>"opentext_wsm", :ts=>1400740929, :type=>"cms"}
{:from=>nil, :to=>"CloudFlare Inc", :ts=>1410419212, :type=>"provid
{:from=>nil, :to=>"wordpress", :ts=>1409810232, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048760, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1400293936, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1407599907, :type=>"cms"}|{:fro
{:from=>"6.28", :to=>nil, :ts=>1413397685, :type=>"cms_version"}|{: {:from=>"wordpress", :to=>nil, :ts=>1376100844, :type=>"cms"}|{:fro
{:from=>nil, :to=>"oraclewebcenter", :ts=>1428199112, :type=>"cms
events
Appendix 4 - Acquia Report
id jtr.rso.wisc.edu chpra.wisc.edu trc.wisc.edu grbweb.icecube.wisc.edu flu.wisc.edu lakeshorepreserve.wisc.edu obgyn.wisc.edu ordertranscript.wisc.edu chtc.cs.wisc.edu apl.wisc.edu cimss.ssec.wisc.edu libtext.library.wisc.edu aptlii.global.wisc.edu apalsa.rso.wisc.edu libtext-dev.library.wisc.edu insights.engr.wisc.edu phillips-lab.biochem.wisc.edu wisconsinwelcome.wisc.edu wieyemd.ophth.wisc.edu ccrweb.aos.wisc.edu lakefutures.wisc.edu federated.kb.wisc.edu scor.chem.wisc.edu hydroecology.cee.wisc.edu wisconsinreflections.wisc.edu powerofnursing.wisc.edu faculty.nelson.wisc.edu cnerg.engr.wisc.edu apip.global.wisc.edu business2.ems.wisc.edu blogs.ls.wisc.edu code.icecube.wisc.edu software.icecube.wisc.edu csp.polisci.wisc.edu galenet.com.ezproxy.library.wisc.edu wisstat.wisc.edu login.ophth.wisc.edu projectgrow.rso.wisc.edu nanospin.chem.wisc.edu admin.studyabroad.wisc.edu teachingwithtech.lss.wisc.edu atlas.wail.wisc.edu tuna.net.wisc.edu stratus.ssec.wisc.edu dept.polisci.wisc.edu host.cals.wisc.edu womenst.library.wisc.edu ctri.wisc.edu workspace.wcer.wisc.edu guts.studentorg.wisc.edu icecube.wisc.edu grads.polisci.wisc.edu www2.biochem.wisc.edu landscape.forest.wisc.edu wiscadproject.wisc.edu ortho.lic.wisc.edu silo.ece.wisc.edu mail.ophth.wisc.edu laptop.library.wisc.edu pdm.medicine.wisc.edu apa.wisc.edu provost.wisc.edu admissions.bus.wisc.edu comm-org.wisc.edu aqua.wisc.edu docushare.icecube.wisc.edu juno.wisc.edu madison.apl.wisc.edu botany.wisc.edu nelson.wisc.edu blc.wisc.edu irb.wisc.edu statefair.wisc.edu library.ssec.wisc.edu posseprogram.wisc.edu emu.engr.wisc.edu hazy.cs.wisc.edu son.wisc.edu portfolios.education.wisc.edu clipsheet.uc.wisc.edu wisconsincareers.wisc.edu skyking.microscopy.wisc.edu engr.ems.wisc.edu my.cae.wisc.edu wiscinfo.wisc.edu cbe.wisc.edu testing.wisc.edu ice.chem.wisc.edu neuroanatomy.wisc.edu sfs.doit.wisc.edu videos.med.wisc.edu topslab.wisc.edu protected.lss.wisc.edu webmail.physiology.wisc.edu getfacts.wisc.edu ress.hslc.wisc.edu mstp.med.wisc.edu stats.net.wisc.edu
subdomain jtr.rso chpra trc grbweb.icecube flu lakeshorepreserve obgyn ordertranscript chtc.cs apl cimss.ssec libtext.library aptlii.global apalsa.rso libtext-dev.library insights.engr phillips-lab.biochem wisconsinwelcome wieyemd.ophth ccrweb.aos lakefutures federated.kb scor.chem hydroecology.cee wisconsinreflections powerofnursing faculty.nelson cnerg.engr apip.global business2.ems blogs.ls code.icecube software.icecube csp.polisci galenet.com.ezproxy.library wisstat login.ophth projectgrow.rso nanospin.chem admin.studyabroad teachingwithtech.lss atlas.wail tuna.net stratus.ssec dept.polisci host.cals womenst.library ctri workspace.wcer guts.studentorg icecube grads.polisci www2.biochem landscape.forest wiscadproject ortho.lic silo.ece mail.ophth laptop.library pdm.medicine apa provost admissions.bus comm-org aqua docushare.icecube juno madison.apl botany nelson blc irb statefair library.ssec posseprogram emu.engr hazy.cs son portfolios.education clipsheet.uc wisconsincareers skyking.microscopy engr.ems my.cae wiscinfo cbe testing ice.chem neuroanatomy sfs.doit videos.med topslab protected.lss webmail.physiology getfacts ress.hslc mstp.med stats.net
root wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
Weebly
Fastly
cms_veprovider
iis apache
platform_dotnet
Appendix 4 - Page 18 of 19 iis
php_5.3|platform_dotnet|platform_php ipv6 mobile|php_5.3|platform_php|social_embed
platform_java content_embed|mobile|php_5.3|platform_php php_5.4|platform_php|social_embed|ipv6 mobile platform_dotnet php_5.3|platform_dotnet|platform_php php_5.5|platform_php mobile|platform_java ipv6
platform_dotnet php_5.4|platform_php|ipv6 php_5.3|platform_php
mobile|php_5.3|platform_php platform_dotnet
iis iis apache apache apache
apache apache
apache apache apache apache apache
iis
iis
iis
php_5.3|platform_php php_5.4|platform_php|ipv6 content_embed|platform_dotnet iis ipv6 content_embed|php_5.1|platform_php|social_embed|soc
iis
iis apache apache iis apache apache iis apache apache iis
iis
iis nginx apache apache iis apache coyote apache apache iis
iis iis apache apache lighttpd iis
mobile|platform_dotnet
platform_dotnet
mobile|php_5.4|platform_php|ipv6 platform_dotnet
php_5.3|platform_php php_5.3|platform_dotnet|platform_php
platform_dotnet social_embed|social_media_like html5|mobile platform_dotnet
platform_dotnet mobile|php_5.3|platform_php
platform_java html5
php_5.3|platform_php|social_media_like platform_dotnet
platform_dotnet mobile php_5.3|platform_dotnet|platform_php mobile|ipv6
fastly|varnish|ipv6 platform_dotnet platform_dotnet
mobile platform_php
apache apache iis apache apache nginx apache apache apache apache apache apache
apache
mobile ipv6
platform_dotnet mobile platform_php
iis
mobile|platform_dotnet
websrv apache iis
features ipv6 platform_dotnet php_5.3|platform_php
title
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 comm-org: t
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
domain_created
classrooms.hslc.wisc.edu www.med.wisc.edu
login.wisc.edu
i.stanford.edu
blcprogram.weebly.com
ecs.library.wisc.edu
www.polisci.wisc.edu
www.polisci.wisc.edu
internetatlas.org
cnerg.github.io aptlii.global.wisc.edu
uwdc.library.wisc.edu
redirect
dns_provid ip 144.92.74.126 wisc.edu 128.104.201.94 wisc.edu 128.104.81.186 wisc.edu 128.104.255.62 wisc.edu 144.92.9.200 wisc.edu 144.92.239.223 wisc.edu 144.92.66.150 wisc.edu 128.104.81.220 wisc.edu 128.105.7.141 wisc.edu 144.92.122.45 wisc.edu 128.104.108.105 wisc.edu 128.104.1.195 wisc.edu 128.104.23.170 144.92.74.0 wisc.edu 144.92.161.55 128.104.201.96 wisc.edu 128.104.116.80 wisc.edu 128.104.81.33 128.104.254.70 144.92.130.91 wisc.edu 162.144.12.28 wisc.edu 128.104.22.19 wisc.edu 128.104.71.70 wisc.edu 128.104.201.61 wisc.edu 144.92.9.53 wisc.edu 144.92.223.16 wisc.edu 144.92.235.94 wisc.edu 199.27.75.133 wisc.edu 128.104.23.170 wisc.edu 144.92.104.126 wisc.edu 128.104.88.40 wisc.edu 128.8.164.186 wisc.edu 128.8.164.165 wisc.edu 128.104.89.251 wisc.edu 128.104.46.200 wisc.edu 144.92.122.50 wisc.edu 128.104.254.110 144.92.74.126 wisc.edu 128.104.71.108 wisc.edu 128.104.23.170 wisc.edu 144.92.239.246 wisc.edu 198.133.224.233 wisc.edu 146.151.144.42 wisc.edu 128.104.108.120 wisc.edu 128.104.81.186 wisc.edu 144.92.93.173 wisc.edu 128.104.1.195 wisc.edu 144.92.76.69 wisc.edu 144.92.160.55 wisc.edu 70.39.232.40 wisc.edu 128.104.255.62 wisc.edu 128.104.81.186 wisc.edu 128.104.116.80 wisc.edu 144.92.199.125 wisc.edu 128.104.89.251 wisc.edu 144.92.119.123 wisc.edu 128.104.201.100 wisc.edu 128.104.204.248 wisc.edu 128.104.81.76 128.104.208.20 128.104.81.21 wisc.edu 128.104.81.67 wisc.edu 144.92.201.147 wisc.edu 144.92.122.77 wisc.edu 144.92.44.210 wisc.edu 128.104.5.102 wisc.edu 128.104.109.84 wisc.edu 144.92.122.50 wisc.edu 128.104.26.71 wisc.edu 144.92.235.112 wisc.edu 199.34.228.54 wisc.edu 144.92.9.17 wisc.edu 144.92.9.53 wisc.edu 128.104.108.105 wisc.edu 128.104.81.186 wisc.edu 128.104.201.96 wisc.edu 171.64.75.45 wisc.edu 144.92.223.16 wisc.edu 144.92.146.189 wisc.edu 144.92.9.53 wisc.edu 144.92.160.80 wisc.edu 144.92.48.158 wisc.edu 144.92.104.126 wisc.edu 128.104.201.49 wisc.edu 144.92.9.223 128.104.81.112 wisc.edu 144.92.239.226 wisc.edu 128.104.71.241 wisc.edu 144.92.50.135 wisc.edu 144.92.69.153 wisc.edu 144.92.50.106 wisc.edu 128.104.201.71 wisc.edu 128.104.1.207 wisc.edu 128.104.21.151 wisc.edu 144.92.122.50 wisc.edu 144.92.50.139 wisc.edu 144.92.154.150 wisc.edu 146.151.144.47 {:from=>nil, :to=>"wordpress", :ts=>1381731726, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401045405, :type=>"cms"}
{:from=>nil, :to=>"Weebly", :ts=>1404188996, :type=>"provider"} {:from=>nil, :to=>"opentext_wsm", :ts=>1401401900, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401046565, :type=>"cms"}
{:from=>"7.21", :to=>"7.26", :ts=>1391223168, :type=>"cms_version
{:from=>nil, :to=>"opentext_wsm", :ts=>1405994707, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1381768574, :type=>"cms"}|{:fro
{:from=>"wordpress", :to=>nil, :ts=>1389197548, :type=>"cms"}
{:from=>"theplanet", :to=>"SoftLayer", :ts=>1376010691, :type=>"pr
{:from=>nil, :to=>"opentext_wsm", :ts=>1403071647, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1416557698, :type=>"cms"}
events
Appendix 4 - Acquia Report
id subdomain root moodle.law.wisc.edu moodle.law wisc ersl.wisc.edu ersl wisc polygon.slc.engr.wisc.edu polygon.slc.engr wisc bse.wisc.edu bse wisc dsc.journalism.wisc.edu dsc.journalism wisc sedation.pediatrics.wisc.edu sedation.pediatrics wisc studyabroad.wisc.edu studyabroad wisc tic.engr.wisc.edu tic.engr wisc lists.cs.wisc.edu lists.cs wisc essentialevidenceplus.com.ezproxy.library.wisessentialevidenceplus.com.ezproxy.l wisc coops.wisc.edu coops wisc davidson-cs.wisc.edu davidson-www.cs wisc charge.wisc.edu charge wisc fti.neep.wisc.edu fti.neep wisc gstp.wisc.edu gstp wisc foodeng.wisc.edu foodeng wisc cntp.wisc.edu cntp wisc ticket.library.wisc.edu ticket.library wisc peacecorps.wisc.edu peacecorps wisc studentservices.engr.wisc.edu studentservices.engr wisc sep.uwcarbone.wisc.edu sep.uwcarbone wisc uwra.wisc.edu uwra wisc corkboard.journalism.wisc.edu corkboard.journalism wisc ams.org.ezproxy.library.wisc.edu ams.org.ezproxy.library wisc sustainable.engr.wisc.edu sustainable.engr wisc perlman.medmicro.wisc.edu perlman.medmicro wisc irh.wisc.edu irh wisc go.global.wisc.edu go.global wisc histology.med.wisc.edu histology.med wisc iie.slc.engr.wisc.edu iie.slc.engr wisc dfrc.wisc.edu dfrc wisc npp.neuroscience.wisc.edu npp.neuroscience wisc itunes.wisc.edu itunes wisc researchguides.ebling.library.wisc.edu researchguides.ebling.library wisc irc.wisc.edu irc wisc mediaspace.wisc.edu mediaspace wisc mapmaker.aos.wisc.edu mapmaker.aos wisc physicalplant.wisc.edu physicalplant wisc pegasus.ep.wisc.edu pegasus.ep wisc courses.dcs.wisc.edu courses.dcs wisc nanoscience.engr.wisc.edu nanoscience.engr wisc rrc.engr.wisc.edu rrc.engr wisc intlscholars.wisc.edu intlscholars wisc tt.doit.wisc.edu tt.doit wisc learning.wisc.edu learning wisc writing.wisc.edu writing wisc science.wisc.edu science wisc mepp.engr.wisc.edu mepp.engr wisc orbs.chsra.wisc.edu orbs.chsra wisc histologyatlas.wisc.edu histologyatlas wisc reitz.me.wisc.edu reitz.me wisc wbess.slc.engr.wisc.edu wbess.slc.engr wisc surgery.wisc.edu surgery wisc dsm.psychiatryonline.org.ezproxy.library.wisc.dsm.psychiatryonline.org.ezproxy.librwisc mocha.meteor.wisc.edu mocha.meteor wisc uwell.wisc.edu uwell wisc sel.me.wisc.edu sel.me wisc ge.ssec.wisc.edu ge.ssec wisc help.hep.wisc.edu help.hep wisc sprott.physics.wisc.edu sprott.physics wisc pediatrics.wisc.edu pediatrics wisc tle.wisc.edu tle wisc commencement.wisc.edu commencement wisc newstudent.wisc.edu newstudent wisc bussvc.wisc.edu bussvc wisc admissions.wisc.edu admissions wisc calendar.wisc.edu calendar wisc preview.wiscwebcms.wisc.edu preview.wiscwebcms wisc visualcultures.wisc.edu visualcultures wisc mmcd.nmrfam.wisc.edu mmcd.nmrfam wisc repairs.housing.wisc.edu repairs.housing wisc pitau.slc.engr.wisc.edu pitau.slc.engr wisc engr.wisc.edu engr wisc electionadmin.wisc.edu electionadmin wisc admin.ocpd.wisc.edu admin.ocpd wisc fbc.wisc.edu fbc wisc wihiv.wisc.edu wihiv wisc nbo6.chem.wisc.edu nbo6.chem wisc wail.cs.wisc.edu wail.cs wisc wisc.edu www wisc dev.dairymanagement.wisc.edu dev.dairymanagement wisc urs.ls.wisc.edu urs.ls wisc saa.ls.wisc.edu saa.ls wisc ils.wisc.edu ils wisc bscw.wcer.wisc.edu bscw.wcer wisc whatworksforhealth.wisc.edu whatworksforhealth wisc webmail.cae.wisc.edu webmail.cae wisc mipncontroldatabase.wisc.edu mipncontroldatabase wisc visitbucky.wisc.edu visitbucky wisc faculty.polisci.wisc.edu faculty.polisci wisc tools.flycrispr.molbio.wisc.edu tools.flycrispr.molbio wisc cme.wisc.edu cme wisc wiscsoftware.wisc.edu wiscsoftware wisc
tld edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu edu
cms
cms_veprovider
Appendix 4 - Page 19 of 19 iis
platform_dotnet|social_embed
iis iis
iis
iis iis iis iis
iis
iis
apache apache apache iis apache apache apache iis apache apache apache apache apache iis apache apache apache apache iis iis iis
iis apache apache apache apache
iis apache iis apache apache apache apache
websrv apache apache apache apache apache apache iis apache apache
php_5.2|platform_dotnet|platform_php mobile|ipv6 platform_dotnet mobile platform_dotnet
html5
php_5.3|platform_php
html5|mobile html5|ipv6 ipv6 platform_dotnet platform_dotnet html5|platform_dotnet platform_dotnet
mobile ipv6 php_5.1|platform_php mobile social_embed platform_dotnet mobile mobile
ipv6
platform_dotnet mobile|platform_ruby ipv6 php_5.4|platform_php|ipv6 platform_ruby mobile|platform_ruby
social_embed
platform_dotnet ipv6 html5|mobile ipv6 ipv6 platform_dotnet mobile|platform_dotnet platform_dotnet
php_5.5|platform_php php_5.4|platform_php|ipv6 mobile
platform_dotnet
content_embed|php_5.3|platform_php platform_dotnet|social_embed mobile|platform_ruby php_5.4|platform_php|ipv6
mobile
ipv6 mobile platform_dotnet ipv6
platform_dotnet mobile
mobile platform_dotnet
platform_dotnet
features php_5.3|platform_php ipv6 content_embed|ipv6
title
patron.library.wisc.edu
management.engr.wisc.edu
ebling.library.wisc.edu
sse.engr.wisc.edu
login.wisc.edu
www.pediatrics.wisc.edu
www.engr.wisc.edu
redirect
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
www.admissions.wisc.edu www.polisci.wisc.edu
login.wisc.edu
bus.wisc.edu
www.housing.wisc.edu
1985-09-30 00:00:00 -0400 home | cente
www.doit.wisc.edu
1985-09-30 00:00:00 -0400 teaching and
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400
1985-09-30 00:00:00 -0400 1985-09-30 00:00:00 -0400
domain_created
dns_provid ip wisc.edu 128.104.94.37 wisc.edu 128.104.201.94 wisc.edu 128.104.201.59 wisc.edu 144.92.93.172 wisc.edu 144.92.22.140 wisc.edu 144.92.221.86 wisc.edu 144.92.201.180 wisc.edu 144.92.225.235 wisc.edu 128.105.6.16 wisc.edu 128.104.46.200 wisc.edu 144.92.122.14 wisc.edu 128.105.17.45 wisc.edu 128.104.81.49 wisc.edu 128.104.184.130 wisc.edu 144.92.52.156 wisc.edu 144.92.93.172 wisc.edu 128.104.201.71 wisc.edu 128.104.1.207 wisc.edu 128.104.23.170 wisc.edu 128.104.201.96 wisc.edu 128.104.208.69 wisc.edu 128.104.147.234 wisc.edu 144.92.22.140 wisc.edu 128.104.46.200 wisc.edu 144.92.225.235 wisc.edu 144.92.72.99 wisc.edu 144.92.115.213 wisc.edu 128.104.23.170 wisc.edu 144.92.50.134 wisc.edu 128.104.201.70 wisc.edu 144.92.64.138 128.104.9.200 wisc.edu 144.92.9.53 wisc.edu 144.92.50.151 wisc.edu 144.92.13.93 wisc.edu 38.81.32.36 wisc.edu 144.92.131.141 wisc.edu 144.92.175.162 wisc.edu 128.104.201.64 wisc.edu 128.104.80.67 wisc.edu 128.104.201.96 wisc.edu 128.104.201.59 wisc.edu 128.104.23.170 wisc.edu 128.104.81.186 wisc.edu 128.104.81.186 wisc.edu 128.104.81.10 wisc.edu 144.92.9.17 wisc.edu 144.92.225.235 wisc.edu 144.92.156.39 wisc.edu 144.92.50.134 wisc.edu 128.104.201.104 wisc.edu 128.104.201.70 wisc.edu 128.104.84.90 wisc.edu 128.104.46.219 wisc.edu 144.92.130.175 wisc.edu 144.92.9.17 wisc.edu 128.104.201.67 wisc.edu 128.104.108.131 wisc.edu 128.104.28.49 wisc.edu 128.104.165.254 wisc.edu 144.92.221.86 wisc.edu 144.92.9.230 wisc.edu 144.92.9.53 wisc.edu 128.104.80.43 wisc.edu 128.104.73.77 wisc.edu 128.104.80.118 wisc.edu 128.104.80.153 wisc.edu 144.92.9.17 wisc.edu 144.92.9.17 wisc.edu 144.92.4.116 wisc.edu 128.104.81.174 wisc.edu 128.104.201.107 wisc.edu 128.104.201.59 wisc.edu 128.104.89.251 wisc.edu 128.104.81.68 wisc.edu 144.92.212.43 wisc.edu 128.104.81.186 wisc.edu 128.104.70.5 wisc.edu 128.105.7.22 wisc.edu wisc.edu 144.92.193.148 wisc.edu 128.104.88.40 wisc.edu 144.92.9.17 wisc.edu 128.104.88.40 wisc.edu 144.92.160.49 wisc.edu 144.92.156.45 wisc.edu 128.104.1.207 wisc.edu 128.104.81.186 wisc.edu 128.104.80.118 wisc.edu 128.104.81.186 wisc.edu 144.92.238.20 wisc.edu 128.104.80.101 wisc.edu 128.104.80.235 {:from=>nil, :to=>"opentext_wsm", :ts=>1409266029, :type=>"cms"}
{:from=>nil, :to=>"opentext_wsm", :ts=>1401048758, :type=>"cms"}
{:from=>"6.24", :to=>"6.28", :ts=>1381211622, :type=>"cms_version
{:from=>"6.25", :to=>nil, :ts=>1428032996, :type=>"cms_version"}|{:
{:from=>nil, :to=>"opentext_wsm", :ts=>1403731066, :type=>"cms"}
{:from=>nil, :to=>"wordpress", :ts=>1416191593, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1401027345, :type=>"cms"}
{:from=>"wordpress", :to=>nil, :ts=>1376109820, :type=>"cms"}|{:fro
{:from=>nil, :to=>"opentext_wsm", :ts=>1403851789, :type=>"cms"} {:from=>nil, :to=>"opentext_wsm", :ts=>1401048027, :type=>"cms"}
events
Appendix 4 - Acquia Report
CMS Assessment Committee – Phase I Report Appendix 5 Gartner Report – Drupal vs. WordPress – October 2014
Printed 11/17/2015
This research note is restricted to the personal use of
[email protected] G00268425
Drupal Versus WordPress and How to Best Use Them to Provide Enterprise WCM Services Published: 14 October 2014
Analyst(s): Larry Cannell
As the two most popular Web content management systems in use on the Internet, Drupal and WordPress offer compelling and safe enterprise choices because of their enormous communities. This document compares Drupal and WordPress and provides guidance on how IT organizations can best use them.
Key Findings ■
Drupal and WordPress are among the safest Web content management (WCM) choices because their usage is greater than any other enterprise WCM solution; they count their websites and users in terms of millions.
■
Drupal's core constituencies are content administrators and site builders who value utility and reuse over visual aesthetics.
■
WordPress' core constituencies are operators of basic websites as well as Web developers looking for minimal content services to help build custom websites.
■
Drupal and WordPress commoditize traditional WCM functions, similar to how Linux commoditized OSs. A new form of WCM hosting environment is emerging that builds on application virtualization and exploits these commoditized capabilities.
Recommendations ■
Use Drupal for large sites where unified content management is essential. Use WordPress for basic websites or as the basis for highly customized, high-value websites.
■
Provide an enterprise WCM service that meets the needs of potentially hundreds of websites.
■
Consider supporting both Drupal and WordPress — together, they can meet most enterprise WCM needs. Drupal is too complex for some sites, and WordPress is too simple for others.
■
Think long term, and plan for product upgrades from the start. Stay vigilant for proprietary traps that limit future choices.
This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
■
Establish a governance process, or leverage an existing governance process, that creates buyin for people, policy and organizational processes in order to succeed.
Table of Contents Comparison........................................................................................................................................... 3 Summary of Differences................................................................................................................... 3 Summary of Similarities.................................................................................................................... 5 Analysis.................................................................................................................................................. 5 Detailed Differences Between Drupal and WordPress....................................................................... 6 Page Assembly Architectures..................................................................................................... 7 Core Content Management Features and Add-On Interoperability.............................................. 8 Upgrade Philosophies.................................................................................................................9 Commercial Leadership Focus................................................................................................. 12 Why Are Drupal and WordPress Unlike Other WCM Products?...................................................... 13 Participants in These Communities Compete on Services, Not Software.................................. 13 Parallels Among Drupal, WordPress and Linux......................................................................... 15 What About Joomla?................................................................................................................ 16 Guidance..............................................................................................................................................17 Assess the Use Cases....................................................................................................................17 Think in Terms of Hundreds of Websites, Not Just One.................................................................. 17 Consider Supporting Both Drupal and WordPress.......................................................................... 18 Plan for the Long Term................................................................................................................... 19 Establish WCM Governance........................................................................................................... 20 Gartner Recommended Reading.......................................................................................................... 20 Notes................................................................................................................................................... 20
List of Tables Table 1. Major Differences Between Drupal and WordPress................................................................... 4
List of Figures Figure 1. Drupal's Content Architecture Encourages Interoperability Among Add-Ons............................9 Figure 2. Drupal and WordPress Release Frequency, Labeling and Support Policy...............................11 Figure 3. The Drupal and WordPress Communities Compete on Services, Not Software......................14
Page 2 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Figure 4. Similarities Between the Commoditization of OSs and WCM..................................................16
Comparison This document compares Drupal and WordPress, highlights their main differences, identifies important similarities and offers guidance on how IT organizations can best leverage them. After years of investing in website deployments based on expensive enterprise WCM systems, IT professionals are reconsidering their options. As the two most popular WCM systems in use on the Internet, Drupal and WordPress offer compelling low-cost alternatives. In addition, both products are safe enterprise choices because they are secure and interoperable and have enormous communities behind them.
Summary of Differences Although similar in many ways, Drupal and WordPress differ in significant ways. IT professionals must understand these differences to determine the best fit for their specific situation.
Page 3 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Table 1. Major Differences Between Drupal and WordPress Drupal
WordPress
Overall
Drupal is a feature-rich content management framework. Strengths: Drupal has strong native content capabilities that encourage add-on interoperability. Weaknesses: The system is difficult to design for and can feel too structured for some developers.
WordPress is a simple website manager that has extensible content services that developers can unlock. Strengths: It is easier to configure a basic site with WordPress. WordPress is also more designer-friendly. Weaknesses: The system requires a developer to build and maintain complex sites.
Page assembly architecture
Drupal pages are assembled via a complex combination of system configuration and template files. Result: A steeper learning curve exists for designers. However, administrators have more control over page appearance.
WordPress templates are significantly easier to understand. Result: It is easier for website designers to create a WordPress template.
Content management features and add-on interoperability
Drupal natively provides features to manage flexible content types. Add-on modules leverage and extend these core content management functions. Result: Drupal modules tend to build on this core and each other.
WordPress has functions for implementing custom post types but has only a few features directly exposed through the administrative interface for managing them. Result: Although plug-ins can interact, WordPress plug-ins tend to be independent rather than built upon each other.
Upgrade philosophy
Major Drupal versions are released about every three years: ■ Major versions require site
WordPress regularly releases a new version every four to six months: ■ Each version includes new features
conversion and involve API and data changes. Result: Major version upgrades require a dedicated project. However, major versions of Drupal have been supported with minor updates for up to six years.
and bug fixes (whatever is ready). WordPress encourages upgrading to the latest version and has no published policy for how long a particular version will be supported with minor updates. Result: WordPress releases are more frequent and cause less disruption. However, long-term support of older WordPress releases is indeterminate.
Commercial leadership focus
Acquia: This company provides enterprisefocused products and services. Acquia has invested heavily in marketing and in building awareness of Drupal within enterprises.
Automattic: This company has mostly consumer- and small or midsize business (SMB)-focused products and services. However, Automattic has many notable enterprise customers.
Advocate personality
Drupal advocates are often content administrators looking for a system with rich content management features and has addon interoperability.
WordPress advocates are often website developers looking for a server to provide minimal content services. WordPress is also more designer-friendly.
Source: Gartner (October 2014)
Page 4 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Summary of Similarities Drupal and WordPress are also similar in many ways. These include: ■
Popularity: Drupal and WordPress are the two most popular WCM products. BuiltWith says that WordPress runs over 48% of the top 10,000 websites running a WCM. Drupal, although a distant second, runs over 13%; this is still over twice the number of sites of the next most popular WCM. Usage of these products is measured in millions of websites and users.
■
Robust communities: Both Drupal and WordPress have large and passionate communities consisting of thousands of developers, designers and service providers. All these community participants have a shared interest in maintaining, securing and growing their particular product. Commercial entities (run by the projects' original founders) anchor the communities and provide a base level of investment, as well as deliver services built for and on the product.
■
Developed openly on the Internet: Both communities' websites are based on their own product and have become valuable product knowledge bases through years of community participants sharing problems and answering questions. Another benefit is that these products are secure by necessity, interoperate with popular Internet services and represent a form of Web-scale "dogfooding" (the use of one's own product).
■
Open-source license: Both products use version 2 of the open-source GNU General Public License (GPL v.2). Often criticized for its viral nature, the application of GPL v.2 in these communities promotes competition around services rather than software. This has resulted in the development of better software and more service choices.
■
Software environment: Both products run on the Linux OS, the Apache Web server, the MySQL database and the PHP language (that is, LAMP). Therefore, an IT department that can support one of the products can also support the other.
■
Multiple delivery models: Numerous hosting options are available, including self-hosting, managed hosting and the emergence of SaaS offerings based on either of these products.
Analysis The size of Drupal's and WordPress' ecosystems is stunning. WordPress is, by any measure, the most popular WCM in use on the Internet. Drupal is a distant second, yet its use still dwarfs that of all other enterprise WCM vendors. Both products have tens of thousands of community-created and -supported add-ons (called plug-ins within WordPress and modules within Drupal). Given their popularity, interoperability and enormous community, chances are that both Drupal and WordPress will still be available and running millions of websites 20 years from now. How many enterprise WCM vendors can say the same? Enterprises should consider replacing their current WCM solution with Drupal or WordPress when they are frustrated with the solution's cost or functionality or are concerned about its long-term viability. The most notable reason for this is that the goals of the open-source communities behind Drupal and WordPress align with traditional IT goals. They strive to provide low-cost, highly
Page 5 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
functional, yet commoditized software that lays the foundation for continued innovation. Software commoditization is the path that Linux took within the OS market many years ago. Although commercial vendors warned enterprises that the OS was too valuable to be based on open-source software, Linux proved more than capable and subsequently accelerated the emergence of innovations such as virtualization and cloud computing. In other words, software commoditization enables IT to focus on higher-value opportunities. However, Drupal and WordPress differ in significant ways. IT strategists need to understand each product's strengths to ensure success. In short, Drupal is generally appropriate for large sites managing a diverse, but unified, set of content. WordPress is a better fit for basic websites or stand-alone, high-value websites where development and upkeep are well-funded.
Detailed Differences Between Drupal and WordPress All popular open-source projects have vocal advocates; Drupal and WordPress are no different. Given that both products are based on similar software environments (Linux, Apache, MySQL and PHP), advocates of either of the products have often experimented with the other. Although the perspective of each product's advocates may be biased, those perspectives can be instructive because they are usually well-informed: ■
What the WordPress advocate says about Drupal: "Drupal is for top-down, controlling administrators."
■
What the Drupal advocate says about WordPress: "WordPress is a freewheeling and undisciplined system."
Both statements are true — to some extent. Another way to compare Drupal and WordPress is to view them as knives. Most people only need a simple dinner knife on a daily basis. The dinner knife is analogous to WordPress in its simplest form. A WordPress site that contains a few pages (and perhaps a blog) is easy to set up and run. You can test-drive a basic WordPress website on WordPress.com, a hugely popular and inexpensive SaaS 1
offering that runs the WordPress software. On the other hand, Drupal is the Swiss Army knife of website tools. Drupal can be configured to address many website needs, including simple websites containing only a few pages, but requires someone with a more technical background to operate. Sometimes neither a Swiss Army knife nor a dinner knife is sufficient. Instead, you need a hunting knife, or a website focused on delivering one particular function well. For example, a marketing department needs an attractive and interactive website to promote a particular product or to support an advertising campaign. However, customized websites require development to add specific features, as well as design expertise to provide a finely tuned experience. To extend the metaphor, hunting knives are sold based on their appearance as much as their utility. Both Drupal and WordPress can be tailored to meet the needs of customized websites. Drupal is a more complex and feature-rich WCM product than WordPress. Its strength is in content organization and facilitating community-contributed module interoperability. The core product has a powerful set of content management capabilities. However, this comes with the cost of an imposed
Page 6 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
structure. This structure can result in a steep learning curve, particularly for Web designers, but also for developers. WordPress has a "Clean, Lean and Mean" philosophy that not only delivers basic capabilities and a simple administrative experience, but also provides low-level content capabilities that enable developers to extend WordPress to meet specific needs. WordPress designers and developers like the product because it imposes almost no structure whatsoever. However, this comes with the cost of having only minimal content management capabilities available to content administrators.
Page Assembly Architectures Nowhere are the architectural differences between the two products more obvious than in the complexity of page assembly. The appearance of a Drupal page is the result of a complex combination of templates, configuration and add-on modules. In contrast, a single template is capable of driving the appearance of a WordPress page. Drupal Builds Pages by Assembling Subcomponents When Drupal receives a request for a page, the system's configuration drives how Drupal assembles the page. Modules and subtemplates are dispatched as Drupal builds the page one subcomponent at a time and inserts content in appropriate locations. Designers who are inexperienced with Drupal can find the complexity of Drupal's page assembly extremely frustrating and will often resort to a form of reverse engineering by examining the resulting page to determine which modules and template files contribute which snippets of HTML. Drupal also offers a feature called "Views" to query and consolidate the list of content to be displayed. An administrator creates and configures views. For example, a content administrator managing a real estate website that lists properties for sale can use the flexibility enabled by views to add or remove pieces of information that are shown alongside each property. However, a downside to this approach is that designers must work with a content administrator to understand what views have been created in order to create a template that tailors the appearance of a page. For example, a real estate website may use different views for commercial property listings versus residential property listings. WordPress Pages Are Built More Directly From a Template In WordPress, page assembly is significantly simpler. Templates are the primary drivers of page assembly. As a result, it is generally easier for a Web designer to translate wireframe designs into a WordPress template. Although a single template can format the appearance of a page, in practice, WordPress templates involve a hierarchy of files and a set of rules. However, these are significantly more straightforward for the designer to understand than Drupal. WordPress has no equivalent to Drupal's views. Instead, designers use a PHP class called WP_Query in their template to find matching content. The template then retrieves the content in "The Loop." This enables less flexibility for content administrators and may require a designer to change a template in order to add or remove what is shown on the page (instead of just changing a
Page 7 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
view in Drupal). However, a benefit to this template-driven approach is that the configuration of what is included in a page is captured entirely in template files. Therefore, a developer is able to version-control these configurations because they are not stored in a database (like a Drupal view).
Core Content Management Features and Add-On Interoperability WordPress developers view their preferred system as a toolkit. Drupal content administrators view their preferred system as a framework. This philosophical difference is visible when contrasting the two products' approaches for enabling new types of content. Both products are able to create and manage custom types of content. For example, a retailer wants to publish a list of store locations on its website to help customers find locations that provide the services they need. Therefore, instead of just managing Web page content, the site must also manage information about store locations. Each location becomes a piece of content, just like a Web page, except that locations have a different set of metadata, such as a street address or telephone number. Taxonomies based on characteristics such as services that are offered or whether a store has an automated teller machine help the website visitor to navigate and find a location. The following three sections explain how Drupal and WordPress handle new types of content, as well as the impact that these approaches have on their communities. Drupal Content Administrators Create and Manage Content Types Drupal provides administrative capabilities to create, manage and extend new types of content. One of Drupal's philosophies is that content administrators should be able to add new types of content and extend them with any number of fields (such as an address or telephone number), entirely through the administrative interface. Developers creating add-on modules that support new types of content are encouraged to build on these core capabilities. For example, the "audio.js" module provides a "field formatter" for content types that have file attachments. In short, this module enables a Drupal website to play audio files within a Web page. Obviously, this module enables the creation of Drupal sites that manage and play libraries of audio files. However, this same module could also apply to our retail example and add audio testimonies from customers for each location. WordPress Developers Create and Manage Custom Post Types WordPress can enable similar features via custom post types. These new types of WordPress content also have metadata and taxonomies associated with them. However, WordPress developers use PHP functions to create and extend custom post types. WordPress has minimal administrative capabilities in its core product to manage these new types of content. To fill this gap, various plug-ins, such as Custom Post Type UI or Advanced Custom Fields, provide administrative capabilities. Alternatively, a more narrowly focused plug-in can enable a specific type of content. For example, the JetPack plug-in (provided by Automattic) includes support for a Portfolio custom post type. Portfolios enable WordPress sites to publish a list (or portfolio) of projects. The Impact of These Approaches on Their Respective Communities In general, Drupal's community-developed add-on modules tend to build on Drupal's core features and on each other. For example, as of October 2014, drupal.org's Download & Extend page reports
Page 8 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
that there are 742 add-on modules that support custom fields for use in custom content types in Drupal 7. The availability of Drupal's core content management capabilities also sets the tone for the Drupal developer community. Drupal comes with a content architecture and provides the associated administrative features. Therefore, the community builds on that foundation. On the other hand, community-contributed plug-ins in WordPress generally do not build on each other. This is likely due to the lack of centrally provided content management features. Figure 1. Drupal's Content Architecture Encourages Interoperability Among Add-Ons
Drupal Custom Content Types
Views
Module
Module
WordPress
Module
Module
Module
Custom Post Types
Plug-In
Plug-In
Plug-In
Plug-In
Module
Module
Source: Gartner (October 2014)
This dissimilar community behavior reflects the products' different philosophies and their core audiences. Drupal's centralized architectural approach encourages interoperability among modules, but it comes at the expense of additional structure and complexity. Module developers and Web designers have to work within Drupal's structure. WordPress' minimalist approach comes at the expense of architectural fragmentation among plug-ins, but it comes with less structure and arguably more flexibility within specific deployments.
Upgrade Philosophies Drupal and WordPress have significant differences regarding version labeling, release frequency and backward compatibility.
Page 9 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Release Frequency and Version Labels Drupal uses a "major.minor" labeling scheme, which is a traditional enterprise view of version labels. Major versions of Drupal are usually released once every three years. For example, Drupal 6 came out in 2008 and Drupal 7 in 2011. Drupal 8 is expected by the end of 2014. WordPress uses an awkward "major.major.minor" labeling scheme. WordPress labels new versions with two numbers separated by a decimal point. However, the first number only increments after the second number reaches nine, so it has virtually no significance. For example, version 4.0 was simply the next sequential release after 3.9, as was version 3.0 the next sequential release after version 2.9. To make this simpler, mentally remove the decimal point (for example, version 40 comes after version 39). New WordPress versions are regularly released every four to six months (for example, in 2013, WordPress released versions 3.6, 3.7 and 3.8, with plans to release versions 3.9, 4.0 and 4.1 in 2014). The project labels these releases as "major" (although this use of the word "major" to describe them is different from how most vendors use the word). These releases include significant functional changes as well as bug and security fixes. The needs of WordPress.com, a popular consumer- and SMB-focused WCM SaaS offering, probably influence this cadence of continual updates. Both products add and increment a number at the end of their version label for minor updates that address significant time-sensitive bugs or security vulnerabilities. For example, Drupal 7.2 was the second update to Drupal 7. WordPress 3.8.1 was the first update to WordPress 3.8.
Page 10 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Figure 2. Drupal and WordPress Release Frequency, Labeling and Support Policy
Drupal 6
3 Years
6.1
6.2
Drupal 7
...
6.22
...
6.26
7.2
...
7.13
7.1
Drupal WordPress
4 to 6 Months
WordPress 3.8
WordPress 3.9
3.8.1
3.9.1
3.8.2
3.9.2
WordPress 4.0
Source: Gartner (October 2014)
Backward Compatibility and Support of Older Versions The two products also have philosophical differences regarding backward compatibility, and they have different approaches for supporting older versions. There are benefits and costs with either of the choices that the product teams have made. The WordPress project prides itself on providing backward compatibility between versions. In a June 2013 presentation, Andrew Nacin, the lead developer for WordPress, explained the project's commitment to backward compatibility this way, "Code that works on WordPress now should always work on WordPress." Unfortunately, as of September 2014, WordPress has no published policy for how long older versions will continue to be supported with minor updates that provide bug and security fixes. Automattic (the primary commercial entity behind WordPress; see the Commercial Leadership Focus section for more information) has informed Gartner that WordPress developers have no plans to end support for WordPress 3.7 (released October 2013) and subsequent releases. An examination of the WordPress versions page shows this to be the case.
Page 11 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
However, the WordPress release archive page also warns, "None of these are safe to use, except the latest in the 4.0 series, which is actively maintained." Automatic updates were introduced in WordPress 3.7 to assist site owners in keeping their software up-to-date. This enables the WordPress software to check for and install new versions automatically. By default, only minor updates (for example, 3.8.1 is a minor update to version 3.8) are automatically installed. Drupal purposefully does not provide backward compatibility between major releases but supports the last two major versions with minor updates to provide bug and security fixes. Add-on modules and templates that were developed for an earlier major Drupal release are incompatible with the latest major release. For example, Drupal 7 modules and templates are incompatible with Drupal 8. New major Drupal versions come with significant changes to APIs, callback hooks, data schemas and templates. Drupal provides a utility to assist with converting a site's database to the new version, as do most popular add-on modules. Nevertheless, expect significant manual intervention to be required when upgrading to a new major Drupal version. The last two major Drupal versions are supported with minor updates containing bug and security fixes. This means that Drupal 6 will be officially supported until shortly after Drupal 8 is released, which would give it a supported life span of close to seven years.
Commercial Leadership Focus Both of the founders of Drupal and WordPress formed commercial entities that provide services based on their product. Dries Buytaert started the Drupal open-source project in 2001 and later cofounded Acquia (in 2007). Matt Mullenweg started the WordPress open-source project in 2003 and later founded Automattic (in 2005). Both founders continue to play active roles in their companies and within their associated open-source communities. In addition, the companies they created — Acquia and Automattic — are leading contributors to and supporters of their open-source communities. Acquia is squarely focused on serving the enterprise market. The company actively markets Drupal for enterprise use, and most of Acquia's revenue comes from cloud services that host, support or enhance Drupal sites. In addition, Acquia markets a SaaS-based contextualization and personalization service, called Acquia Lift, that provides Web analytics and targeted content delivery for Drupal sites. Acquia also provides professional services in support of large Drupal projects. The company had a brief foray into the consumer website market when it launched Drupal Gardens in 2011. However, this has not remained part of Acquia's core focus. WordPress has no equivalent to Acquia in terms of the extent it has gone to promote enterprise use. Automattic primarily caters to the consumer and SMB markets using WordPress.com, a popular SaaS offering built on the open-source software available on WordPress.org. Although Automattic no longer publicizes how many blogs it hosts, based on the distribution of previous numbers and the recent claim that over 60 million sites run WordPress blogs, WordPress.com probably serves between 20 and 40 million blogs. Automattic's enterprise offering is WordPress.com VIP, which provides a subscription support service for WordPress developers and a WordPress hosting service that leverages the WordPress.com infrastructure. Even though the number of customers is Page 12 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
infinitesimal when compared with WordPress.com, WordPress.com VIP serves many notable sites, such as ESPN Grantland, Time.com and TechCrunch.com.
Why Are Drupal and WordPress Unlike Other WCM Products? Simply put, Drupal and WordPress are among the safest WCM product choices. Usage of these products is on a different scale from commercial products. The lone exception is Adobe Experience Manager, which BuiltWith says runs on over 5% of the top 10,000 sites running a WCM. However, this is still far below WordPress' 48% and less than half of Drupal's 13%. Most enterprise WCM vendors will proudly point to hundreds of installations with thousands of users. WordPress and Drupal count their websites and users in the millions. Each product also has huge communities that have produced tens of thousands of add-ons to extend their capabilities. Given the number of sites using these products and the size of their communities, the software is likely to remain viable for a long time. Security holes will be patched quickly, and community interest will push the products to continually evolve.
Participants in These Communities Compete on Services, Not Software A product's open-source license profoundly shapes the type of community that forms around it. Permissible licenses, such as the Apache or BSD licenses, allow open-source software to be incorporated into commercial software. As a result, community participants are able to compete through the sale of software, and enterprises indirectly benefit (perhaps through less expensive software). Both Drupal and WordPress use the GPL v.2 license, which is considered a hereditary open-source license because it includes the controversial "copyleft" condition, which compels developers who tightly integrate code with either product to license the resulting software under GPL v.2. The business models of most commercial software vendors are incompatible with the GPL v.2 license because of its viral nature. In the case of Drupal and WordPress, the GPL v.2 license has been critical in the formation of their communities and has effectively removed the ability for companies (including Acquia and Automattic) to compete based on the sale of commercial software that incorporates code from either product. In essence, the Drupal and WordPress communities collectively own the product and any add-on software. Instead, participants in these communities compete on outsourced services (such as hosting or software development) or SaaS-based services (such as Web analytics or e-commerce). This may be bad news for commercial developers, but it is terrific news for IT organizations because they are in the business of deploying services based on software.
Page 13 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Figure 3. The Drupal and WordPress Communities Compete on Services, Not Software
Competing With Commercial Software Products
Users
...
Competing With Services Based on Open-Software Software
IT's Goal: Provide Services
Services
Users
... Commercial Services Compete Here
Closed
Software
Open
Commercial Software Competes Here
Vendor
Community
Source: Gartner (October 2014)
In addition to co-developing and co-owning the software, community participants also collaborate within their community's online forums (which, of course, run on either Drupal or WordPress). Furthermore, they have built valuable knowledge bases of information about the product that allow new service providers — or IT organizations — to quickly become proficient in their product. These communities are essential to the long-term viability and evolution of their products. Without their communities, Drupal and WordPress would be interesting historical footnotes. Their potential Achilles' heel is anything that threatens the cohesiveness of the open-source community. This could be unwanted leadership change, major disagreements or any other type of schism. GPL-based communities and the products they produce are still new territory for business management. Only a few companies have been successful with them, the most notable being Red Hat. Oracle's seeming mismanagement of the MySQL community shows that, once established, a product may still survive significant missteps. It is probably no coincidence that Drupal's and WordPress' founders are still actively leading their communities. The success of their communities and, hence, their products depends on continued strong leadership to provide direction.
Page 14 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Parallels Among Drupal, WordPress and Linux Drupal and WordPress commoditize traditional WCM functions, similar to how Linux commoditized OSs. The effects of WCM commoditization are starting to become apparent. Nearly all enterprises have websites they need to manage, that are accessed from desktop or mobile devices, and whose content must be organized and associated processes facilitated. Websites with complex needs may require more advanced capabilities (although these often require dedicated applications), but by now, the basic capabilities most websites need are well-understood. For most enterprises, Drupal and WordPress can meet all these basic needs. Vendors of commercially developed WCM systems will say that there is no revenue from Drupal or WordPress — therefore innovation will stagnate. This may be true from their perspective because the opportunities to earn a profit in these communities are quite different from the sale of traditional software. Vendors selling proprietary OSs 15 years ago made these same arguments when Linux first emerged. Nevertheless, the commoditization of OSs, brought about by Linux, enabled a new set of vendors and innovators to focus on solving a new generation of problems. For example, Linux was a critical factor in the acceleration and broad acceptance of virtualization and cloud computing, such as infrastructure as a service (IaaS), platform as a service (PaaS) and SaaS offerings. Similarly, we are seeing the emergence of a new form of WCM hosting environment that leverages advances in virtualization based on Linux containers. Pantheon, for example, provides an innovative website platform that runs Drupal or WordPress websites. The platform manages the entire life cycle of these websites and facilitates processes that approve and then migrate custom changes (which include template modifications, new software components or other types of customizations) that are created in a development environment into a test and, subsequently, a production environment. Based on Linux containers (which also provide the foundation for the application virtualization solution Docker), Pantheon's cloud service virtualizes all the software, configuration, templates and other components that are required for a Drupal or WordPress website. As a result, developers, designers or administrators customizing a website in a development environment operate within the same virtualized environment as the production website. Pantheon also provides services that Drupal and WordPress websites need in order to scale, such as Varnish-based cache services as well as Redis and Solr integration. Although enterprise WCM has not traditionally been suitable for SaaS offerings due to the need for customization (for example, drag-and-drop platforms such as Wix or Squarespace have limited appeal for enterprises), Pantheon bridges this gap by providing a controlled, yet customizable, website IaaS platform that is based on Drupal or WordPress.
Page 15 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Figure 4. Similarities Between the Commoditization of OSs and WCM
Operating Systems
Yesterday
Today
Tomorrow
Competing Operating Systems
Commoditized OS (Linux)
Cloud Services (IaaS, Paas and SaaS)
High-Cost Software, Suitable for a Few HighValue Applications
Web Content Management
Competing WCM Systems
High-Cost Software, Suitable for a Few HighValue Websites
Low-Cost Software Provides Immediate Cost Savings
Next Generation of Services, With New Types of Platforms and Solutions
Commoditized WCM (Drupal and WordPress)
Website Infrastructure as a Service
Low-Cost Software Provides Immediate Cost Savings
Next Generation of Services Enables New Types of Sites and Scales to Thousands
Source: Gartner (October 2014)
Gartner expects existing and new hosting providers to leverage advances in Linux containers and follow Pantheon's lead by providing these flexible, yet controlled, website IaaS platforms. As was the case with Linux and the acceleration of cloud services, the business models of these new types of hosting providers hinge on the availability of popular and robust open-source software, such as Drupal and WordPress. In short, the commoditization of WCM spurs innovative approaches to address a new generation of problems.
What About Joomla? Joomla is often included in comparisons of Drupal and WordPress. Joomla is based on the same software requirements (that is, LAMP), is also licensed under the open-source GPL v.2 license, has a robust community and is identified by BuiltWith as one of the more popular WCM products (although it is most popular among websites outside the top 10,000). However, Joomla is not included in this Gartner analysis because there is no equivalent commercial entity actively leading the Joomla community, such as Drupal's Acquia or WordPress' Automattic. Consequently, there is no consistent level of investment or a vendor of last resort for commercial support. Joomla's popularity attests to its capabilities and may be included in future analysis.
Page 16 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Guidance Enterprises that are frustrated with the cost or functionality of their current WCM solution or that are concerned about the product's long-term viability should consider replacing it with Drupal or WordPress, whichever is most appropriate. However, as with most content management initiatives, governance and business alignment are the most overlooked, and often the most difficult, challenges to overcome. Companies that have been successful with a particular WCM and are happy with its capabilities should be cautious of changing technologies and affecting these business relationship dynamics. In addition, Drupal and WordPress can become the basis of a highly scalable WCM service and provide a foundation for supporting multiple types of enterprise websites, many of which may previously have been unaffordable. IT strategists need to understand the use cases that each product is capable of supporting and be mindful of strategies for scaling a WCM service.
Assess the Use Cases Use Drupal for large sites where unified content management is essential. Use WordPress for basic websites or as the basis for highly customized, high-value websites. Drupal is strongest when managing a diverse, but unified, set of content. For example, intranetpublishing sites are better-suited to Drupal. The native product has strong content management capabilities. However, site owners choosing Drupal must balance their need for these content capabilities with the overhead that the product imposes on designers and developers. WordPress is strongest when managing basic sites because of ease of use and its straightforward management of Web content. For stand-alone, high-value websites, which are often highly customized with specific features and possibly developed by an external agency, either product suffices. For example, a marketing organization is creating a site to support an advertising campaign. The best choice of product will depend on who is creating and who is supporting the site. Drupal is certainly capable of facilitating these sites, but designers and developers must be well-versed in the product to work within the constraints that its structure imposes. WordPress has a leaner core and imposes significantly less structure, and, because of its popularity, more agencies are likely to have sufficient skills to develop on the product. In any case, due to the custom nature, these types of sites require more attention. Fortunately, because they are high-value sites, the extra cost that is necessary to care for these customizations is likely easier to justify.
Think in Terms of Hundreds of Websites, Not Just One Provide an enterprise WCM service that meets the needs of potentially hundreds of websites. Websites are not created equally. A small minority of sites justifies most WCM investments and tends to get all the attention. These are usually owned by marketing. However, many organizations need websites, and they should not (or cannot) all be expensive. For example, manufacturing may
Page 17 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
need informational sites to publish standards or announce new initiatives to its supply chain partners. Companies only providing services to other companies need websites to publicize what they offer but do not necessarily need to make their sites as attractive as a consumer-goods company website. A university could have hundreds of departmental sites providing information for students. Lastly, no department in an enterprise should still be using HTML authoring tools for their websites, yet these types of sites still exist. Commoditization of WCM enables IT organizations to provide sites for any organization in the enterprise. Imagine providing a service that offers WCM capabilities almost to the same scale as what IT provides for desktop computers. This goal helps clarify IT's role, highlights needed competencies, and influences deployment strategies and decisions. If IT is only engaged in a debate over which WCM technologies to use for one particular website, then IT is not providing the highest level of value possible to the business.
Consider Supporting Both Drupal and WordPress Consider supporting both Drupal and WordPress — together, they can meet most enterprise WCM needs. Drupal is too complex for some sites, and WordPress is too simple for others. The biggest barrier that these products have faced within IT organizations is support for MySQL and PHP. For years, many IT organizations have insisted that any WCM product they use must align with their application development environment. Organizations developing with Java would choose a Java-based WCM product. Organizations developing with .NET would choose a .NET-based WCM product. These decisions assume that integration with the WCM would take place at the middleware level and would operate within similar hosting environments. Given the popularity of Drupal and WordPress and the opportunities they enable, it's time for enterprises to get over their hesitation around MySQL and PHP. For purely .NET environments, this represents a significant shift. However, most Java environments already run Linux servers. In addition, old open-source myths continue to fester in some quarters. In particular, because opensource products come with source code, some IT professionals assume that they must be supported as if they were custom applications. However, there is no need to support Drupal or WordPress any differently than other products. Customization is still a choice. In fact, having the source code may make them easier to support. If necessary, direct support is available through Acquia or Automattic. Both communities have numerous independent software vendors (ISVs) involved that can also provide assistance. The true challenge of IT supporting Drupal or WordPress is staffing competency around hosting the products. Any number of ISVs or hosting companies, including Acquia or Automattic, can address this. If internal hosting is preferred, then an IT professional with a nominal background in software development (and capable of, at least, reading PHP code) can understand the needs of either product. The knowledge bases built up by both communities offer valuable resources that most vendors of commercially developed products would envy. For initial installations, line-of-business organizations can buy or hire expertise in either Drupal or WordPress. For example, marketing may choose WordPress due to its designer friendliness, or Page 18 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
manufacturing may choose Drupal to organize its supplier informational pages. Over time, and as usage grows, SMB resources can be consolidated under IT.
Plan for the Long Term Think long term, and plan for product upgrades from the start. Stay vigilant for proprietary traps that limit future choices. For either Drupal or WordPress, an updated site is a secure site. Therefore, plan for upgrades from the start, and carefully examine anything that jeopardizes upgradability. Use add-ons conservatively. Assess their long-term viability separately from the core product itself. Some popular add-ons, with broad community support and a history of being kept up-to-date, may be managed as if they were part of the core product. Be cautious with less popular add-ons, and be aware how much they are used and if there are alternatives that meet the same need. Limit integrations with other systems (such as document management systems or single sign-on) to popular add-ons, preferably based on standards (such as Content Management Interoperability Services [CMIS] or Lightweight Directory Access Protocol [LDAP]). Within five years, expect a major upgrade that requires content migration and a reassessment of other components (such as template modification) to be necessary for both products. Drupal's policy is to release a major version every three years but still support the last two major versions with bug and security fixes. WordPress does not release new versions that require this much effort. Nevertheless, do not be surprised if WordPress releases a significant upgrade on this scale at some point in the future. This may be disguised as a new product announcement, where development of the older product eventually ends. For more details, see the Upgrade Philosophies section. WordPress' normal upgrades are released every four to six months; although they are not as significant as Drupal's major upgrade, do not consider these as minor updates. WordPress upgrades include significant new features that go well beyond simple bug and security fixes and introduce new opportunities for something to fail. Particularly for WordPress sites that use plug-ins, have sufficient staffing to test all upgrades in a development environment first. Moreover, be wary of proprietary services that go beyond Drupal or WordPress. These can include services from hosting providers that offer code migration between development, test and production environments or marketing services that extend the website's capabilities, such as Web analytics or customer targeting. These may be valuable services, but their long-term implications must be understood before committing to them. For example, will these services slow the pace at which the software can be upgraded, or do they lock you into a particular hosting provider?
Page 19 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
Establish WCM Governance Establish or leverage an existing governance process that creates buy-in for people, policy and organizational processes in order to succeed. Simply focusing on WCM technology alone is insufficient. WCM should be treated as a program that provides technologies that are driven by business needs, as well as aligns with organizational structures. Left unchecked, the proliferation of websites can lead to a confusing mess where it is difficult for customers, partners or employees to find information. WCM programs that are supported by governance structures have a much higher chance of success. Website governance may take on multiple flavors, based on where the technologies are applied. The needs and organizational dynamics of websites serving customers will be different from websites that support an intranet or those that support a B2B exchange of information. Additional information about website governance is available in "Eight Governance Patterns for SharePoint, Intranets and Portals That Can Jump-Start Governance Efforts." The advice provided in that document applies to all types of websites.
Notes 1
There are two versions of WordPress. The freely available WordPress open-source software is often referred to as "WordPress.org" because WordPress.org is the location of the community that produces the product. WordPress.com is a popular SaaS offering that runs on the software developed by the community.
Gartner Recommended Reading Some documents may not be available as part of your current Gartner subscription. "Eight Governance Patterns for SharePoint, Intranets and Portals That Can Jump-Start Governance Efforts" "Web Content Management Systems: Managing Web Presence in a Post-2.0 World" "Magic Quadrant for Web Content Management"
Page 20 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
This research note is restricted to the personal use of
[email protected]
GARTNER HEADQUARTERS Corporate Headquarters 56 Top Gallant Road Stamford, CT 06902-7700 USA +1 203 964 0096 Regional Headquarters AUSTRALIA BRAZIL JAPAN UNITED KINGDOM
For a complete list of worldwide locations, visit http://www.gartner.com/technology/about.jsp
© 2014 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. If you are authorized to access this publication, your use of it is subject to the Usage Guidelines for Gartner Services posted on gartner.com. The information contained in this publication has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This publication consists of the opinions of Gartner’s research organization and should not be construed as statements of fact. The opinions expressed herein are subject to change without notice. Although Gartner research may include a discussion of related legal issues, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner is a public company, and its shareholders may include firms and funds that have financial interests in entities covered in Gartner research. Gartner’s Board of Directors may include senior managers of these firms or funds. Gartner research is produced independently by its research organization without input or influence from these firms, funds or their managers. For further information on the independence and integrity of Gartner research, see “Guiding Principles on Independence and Objectivity.”
Page 21 of 21
Gartner, Inc. | G00268425 This research note is restricted to the personal use of
[email protected]
CMS Assessment Committee – Phase I Report Appendix 6 w3techs.com – Usage of Content Management Systems – September 2014
Printed 11/17/2015
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
provided by Q-Success
Home
1 of 8
Technologies
Reports
Sites
Quality
Users
Blog
Forum
FAQ
Search
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
Technologies Content Management Server-side Languages Client-side Languages JavaScript Libraries Markup Languages Character Encodings Image File Formats Site Elements SSL Certificate Authorities Social Widgets Web Servers Operating Systems Content Delivery Traffic Analysis Tools Advertising Networks Tag Managers Top Level Domains Content Languages
http://w3techs.com/technologies/overview/content_management/all
Technologies > Content Management
This diagram shows the percentages of websites using various content management systems. See technologies overview for explanations on the methodologies used in the surveys. Our reports are updated daily.
Usage Trend Market Share Trend
Market
Learn more
How to read the diagram: 58.4% of the websites use none of the content management systems that we monitor. WordPress is used by 24.4% of all the websites, that is a content management system market share of 58.8%.
Content management systems are web-based applications for creating and managing the content of a website. We include all such systems in this category, also systems that are often classified as wikis, blog engines or discussion boards.
Featured Products and Services
58.4% 24.4%
WordPress
58.8%
Joomla
2.8% 6.7%
Drupal
2.1% 5.0%
Secure Premium Wordpress Hosting WP Engine
Top Site Usage Market Position
Magento
1.2% 2.9%
Blogger
1.2% 2.8%
Breakdown
TYPO3
0.6% 1.6%
TemplateMonster
Ranking Server-side Languages Client-side Languages JavaScript Libraries Markup Languages Character Encodings Image File Formats Site Elements SSL Certificate Authorities Social Widgets Web Servers Operating Systems Content Delivery Traffic Analysis Tools Advertising Networks Tag Managers Top Level Domains Content Languages
Adobe Dreamweaver
0.6% 1.5%
PrestaShop
0.5% 1.2%
Premium website templates, including themes for WordPress, Joomla, Drupal, Magento, Prestashop, and more.
Bitrix
0.5% 1.2%
FrontPage
0.5% 1.1%
OpenCart
0.4% 0.9%
see FAQ for explanations on advanced reports
2 of 8
Content Management Systems
Request an extensive market report of specific content management systems.
None
Trends
Technology Brief
Usage of content management systems for websites
Shopify
Present your product or service here
0.4% 0.9%
vBulletin
0.4% 0.9%
DataLife Engine
0.3% 0.8%
Squarespace
0.3% 0.8%
DotNetNuke
0.2% 0.6%
ExpressionEngine
0.2% 0.6%
phpBB
0.2% 0.5%
Discuz!
0.2% 0.5%
osCommerce
0.2% 0.4%
Bigcommerce
0.2% 0.4%
Latest related posting read all
Web technology fact of the day 3 September 2015 XenForo has increased its usage by 54% in the last year. » more
Latest related forum entry read all
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
SharePoint
0.2% 0.4%
Wix
0.2% 0.4%
Weebly
3 of 8
Technology proposal: Craft CMS 28 August 2015 » more
0.1% 0.4%
uCoz
0.1% 0.3%
Zen Cart
0.1% 0.3%
GitHub Pages
0.1% 0.3%
XenForo
0.1% 0.3%
Tumblr
0.1% 0.3%
Simple Machines Forum
0.1% 0.2%
Volusion
0.1% 0.2%
Concrete5
0.1% 0.2%
Telerik Sitefinity
0.1% 0.2%
Contao
0.1% 0.2%
Duda
http://w3techs.com/technologies/overview/content_management/all
0.1% 0.2%
IP.Board
0.1% 0.2%
SPIP
0.1% 0.2%
CMS Made Simple
0.1% 0.2%
Kentico
0.1% 0.2%
Liferay
0.1% 0.2%
PHP Link Directory
0.1% 0.2%
CS-Cart
0.1% 0.2%
Jimdo
0.1% 0.2%
Webs
0.1% 0.2%
eZ Publish
0.1% 0.2%
xt:Commerce
0.1% 0.2%
Yahoo! Small Business
0.1% 0.1%
Pligg
0.1% 0.1%
MediaWiki
0.1% 0.1%
Movable Type
0.1% 0.1%
SilverStripe
less than 0.1% 0.1%
MyBB
less than 0.1% 0.1%
Our Book Recommendation
Integrative Document and Content Management: Strategies for Exploiting Enterprise Knowledge Michael Middleton et al. Price: $73.86 List Price: $79.95 More Content Management Systems Books
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
HubSpot CMS
less than 0.1% 0.1%
Umbraco
less than 0.1% 0.1%
Shopware
less than 0.1% 0.1%
nopCommerce
less than 0.1% 0.1%
XOOPS
less than 0.1% 0.1%
Plone
less than 0.1% 0.1%
Ektron
less than 0.1% 0.1%
3dcart
less than 0.1% 0.1%
Adobe Experience Manager
less than 0.1% 0.1%
UMI.CMS
less than 0.1% 0.1%
Ning
less than 0.1% 0.1%
NetObjects
less than 0.1% 0.1%
NetCat
less than 0.1% 0.1%
WebSite X5
less than 0.1% 0.1%
Livedoor Blog
less than 0.1% 0.1%
Google Sites
less than 0.1% 0.1%
XpressEngine
less than 0.1% 0.1%
HostCMS
less than 0.1% 0.1%
RapidWeaver
less than 0.1% 0.1%
Open Text
less than 0.1% 0.1%
InstantCMS
less than 0.1% 0.1%
EPiServer CMS
less than 0.1% 0.1%
Demandware
less than 0.1% 0.1%
GoDaddy Website Builder
less than 0.1% 0.1% W3Techs.com, 16 September 2015
absolute usage percentage
market share
Percentages of websites using various content management systems
The following content management systems have a market share of less than 0.1% Orchard eSyndiCat Homestead BLOX CMS Moodle WebsiteBaker CMS Xara PyroCMS
4 of 8
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
Web Page Maker Ghost PHP-Fusion PHP-Nuke ekmPowershop LiveStreet CMS Pimcore OpenCms SEOshop Sitecore CMS Contenido e107 Webnode OverBlog Dynamicweb CMS Amiro.CMS Mura CMS Vivvo NukeViet mojoPortal Visualsoft NationBuilder DokuWiki PHPShop Squiz Matrix Intershop ATG Web Commerce Strikingly Chevereto MODx Weblication MaxSite CMS Textalk Webshop Nucleus Magnolia Setup.ru GetSimple Telligent phpwcms a-blog cms UBB.threads YaBB Vanilla Forums Serendipity WebGUI LightCMS Danneo CubeCart Mambo CMSimple Hybris SupeSite Convio CommonSpot Indexhibit Quick.Cms Imperia Lauyan TOWeb Textpattern BlueVoda TypePad Websale Discourse Tiki Wiki CMS Groupware Fork CMS Infopark CMS Fiona KimsQ LocomotiveCMS Kooboo October CMS ImpressPages CMS
5 of 8
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
Percussion Odoo b2evolution ContentXXL Alterian iAPPS Dotclear AxCMS.net SiteSpinner Government Site Builder Phorum Contrexx DocPad NQcontent TomatoCart ProcessWire PivotX PHPFox fCMS Contensis SiteGrinder Geeklog Trac CanalBlog Powerfront Agility CMS Subrion CMS Xanario BrowserCMS Anchor CMS ZMS Cotonti Tangora Web CMS gpEasy Exponent CMS Dragonfly CMS redFACT InterRed Jekyll Literatum Straightsell MoinMoin Blogg.se cms3 Enonic CMS Seamless CMS CoreMedia Hotaru CMS Jahia MidCOM Opennemas Lepton NodeBB Thelia Jadu CMS OneWeb CMS WebSite Tonight FluxBB SimpleSite Fo.ru Stacey Cmsbox ImpressCMS N2 CMS XMB YAF.NET Marqui CMS SageFrame XWiki Flatpress Komodo
6 of 8
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
Onion.net Twilight CMS Decibel CMS OpenACS CMS TWiki Amaxus Hugo Monstra i-SITE Mango Blog Quick 'n Easy Rainbow Foswiki Graffiti HTMLy Chyrp SiteW Taberna Level9 CMS ocPortal Jieqi CMS WikkaWiki Papaya CMS Pikock VIO.Matrix Bitweaver Grav Zotonic OmCore Sense/Net Zinnia Koobi Shop miniBB WebAPP Artiphp Bigace Silva CMS Tajan Portaj AdVantShop Bricolage InfoGlue webEdition WebHare CMS JSPWiki Microweber Webydo Accessible Portal Crowd Fusion Daisy Melody Pier CPS CMS elcomCMS Lightmon Engine PmWiki Apache Lenya Blackmonk Django CMS Navigate CMS phpCOIN TinyCMS WheelCMS
Is there a technology missing? Registered users can make a proposal to add a technology.
Do you want to stay informed about this survey? Use our monthly technology survey RSS Feed. Registered users can also subscribe to a monthly
7 of 8
9/16/15, 5:21 PM
Usage Statistics and Market Share of Content Management System...
http://w3techs.com/technologies/overview/content_management/all
technology survey email.
Share this page
About Us
Disclaimer
W3Techs on
Terms of Use Twitter
Privacy Policy
LinkedIn
Google+
Advertising
Feedback
Facebook
Copyright © 2009-2015 Q-Success
Advertise Here
8 of 8
9/16/15, 5:21 PM
CMS Assessment Committee – Phase I Report Appendix 7 w3techs.com – Comparison of the Usage of WordPress vs. Drupal vs. OpenText – September 2014
Printed 11/17/2015
WordPress vs. Drupal vs. Open Text usage statistics
http://w3techs.com/technologies/comparison/cm-opentext,cm-wor...
provided by Q-Success
Home Technologies Content Management Server-side Languages Client-side Languages JavaScript Libraries Markup Languages Character Encodings Image File Formats Site Elements SSL Certificate Authorities Social Widgets Web Servers Operating Systems Content Delivery Traffic Analysis Tools Advertising Networks Tag Managers Top Level Domains Content Languages
Technologies
Reports
Sites
Quality
Users
Blog
Forum
FAQ
Technologies > Content Management > Technology usage comparison
Comparison of the usage of WordPress vs. Drupal vs. Open Text for websites This report shows the usage statistics of WordPress vs. Drupal vs. Open Text as content management system on the web. See technologies overview for explanations on the methodologies used in the surveys. Our reports are updated daily.
Learn more
This diagram shows the percentages of websites using the selected technologies. How to read the diagram: WordPress is used by 24.4% of all the websites, that is a content management system market share of 58.8%.
Open Text X
Compare with other
58.8% 2.1% 5.0% less than 0.1% 0.1% W3Techs.com, 16 September 2015
absolute usage percentage
Secure Premium Wordpress Hosting WP Engine
TemplateMonster
24.4%
WordPress X Drupal X
Featured Products and Services
Request an extensive market report of specific content management systems.
Usage and market share
Comparison
Search
Premium website templates, including themes for WordPress, Joomla, Drupal, Magento, Prestashop, and more.
market share
Percentages of websites using various content management systems
Present your product or service here
Usage broken down by ranking This diagram shows the percentages of websites using the selected technologies broken down by ranking. How to read the diagram: WordPress is used by 58.8% of all the websites whose content management system we know. WordPress is used by 55.3% of all the websites whose content management system we know and that rank in the top 1,000,000. 58.8% 55.3% 51.4% 46.5%
WordPress 29.9%
Drupal
Open Text
5.0% 6.9% 10.7% 17.7% 19.5% 0.1% 0.1% 0.4% 1.0% 1.3% W3Techs.com, 16 September 2015
Overall
top 1,000,000
top 100,000
top 10,000
top 1,000
Percentages of websites using the selected content management systems broken down by ranking
Historical trend This diagram shows the historical trend in the percentage of websites using the selected technologies.
1 of 3
9/16/15, 5:21 PM
WordPress vs. Drupal vs. Open Text usage statistics
http://w3techs.com/technologies/comparison/cm-opentext,cm-wor...
Our dedicated trend survey shows more content management usage and market share trends.
Market position This diagram shows the market position of the selected technologies in terms of popularity and traffic compared to the most popular content management systems. Our dedicated market survey shows more content management market data.
More details
2 of 3
9/16/15, 5:21 PM
WordPress vs. Drupal vs. Open Text usage statistics
http://w3techs.com/technologies/comparison/cm-opentext,cm-wor...
You can find complete breakdown reports of content management systems in our content management systems market reports.
Share this page
About Us
Disclaimer
W3Techs on
Terms of Use Twitter
Privacy Policy
LinkedIn
Google+
Advertising
Feedback
Facebook
Copyright © 2009-2015 Q-Success
Advertise Here
3 of 3
9/16/15, 5:21 PM
