Tag Archives: Core Team

Notes: March 14, 2017

1. WordPress review

Recap recent history of review prep. MIIS has its own instance of WordPress separate from Midd. College. WordPress has grown quite a bit — 1000s of websites in our instance. WordPress has been difficult to keep up-to-date at times in the past; is WordPress sustainable going forward, or should we be looking at other ways to keep it functional? We’ve had the idea that MiddCreate should be part of the solution. MIIS has not been invited into subsequent meetings, but Bob has seen the charter. One thing they’ll be discussing will be creating one instance including MIIS, will MiddCreate be part of that environment? Last time we were talking about WordPress, a lot of time has been spent on supporting WordPress. Is there a way to re-think WordPress/MiddCreate as a blogging/website creation environment?

Some schools have taken the use of WordPress and separated it by use: individual and academic instances. Some have departmental WordPress sites to support projects, and there are some boutique sites with custom programming/theme. These have separate needs, can we separate them out?

It becomes a different conversation if we’re all going to be brought under the same instance. You could bundle functions/use cases in MiddCreate as well. Communications may want to rein in some of these admin uses.

If we’re paying attention to what other schools are doing, why are we not paying attention to how other schools are using domain of one’s own? Not just for personal use, it’s more nimble than that.

In past conversations, we didn’t have domain of one’s own, so it may become part of the conversation going forward.

ITS has not touched MiddCreate; they helped with authentication, security review and contract negotiations, but they haven’t been involved since then, don’t know how they’re supporting it, if they are at all.

2. Canvas Assessment

This was brought up by FLAC (Faculty Library Advisory Committee), they want to know what’s being done with assessing Canvas, looking at differences with Moodle, etc. Looking at any difference to help desk, tickets to Instructure, etc. Two most common questions have to do with assignments (unpublished); and enrollment, which has more to do with Add/Drop process than with Canvas itself. Other than that, not sure what else to assess Canvas on at this point. For undergrad Canvas is supplemental only, so uses of Canvas are varied; without standards, we don’t have anything to assess Canvas on other than tickets and increase in adoption. Canvas is being adopted at a faster rate than Moodle across Fall and Spring terms. It might also be a little early to ask the question. Feedback has been positive, acknowledging that some adjustments have been necessary. Instructure has also been undergoing some changes as they grow as a company.

3. Hypothes.is

Jeremy is going to be on campus in a couple of weeks for a possible workshop.

4. Future meeting agenda items

Joe will put a call out on Slack for future meeting agenda items.

Notes: Moodle Archving

Guest – Billy Sneed

  • We’re transitioning away from Moodle, but we’re still somewhat reliant on it, even though we’ve migrated to Canvas.
    • We can’t totally turn Moodle off. Need to think thoughtfully about what we still need access to in Moodle and for how long?
    • How do we keep from disrupting policy and practices?
  • Project request was submitted (Billy S. here to speak more to that)
  • What do we still rely on Moodle for?
    • Faculty need to offer course content evidence up to 7 years back, specifically class activity online. They are being evaluated on how they interact with students online and what students get out of the course.
    • No one in the public needs to see any Moodle content, students shouldn’t need access either.
    • Content backups (MIIS). Not student data, just faculty content.
    • We’re still in transition, migration of course sites is not complete. Faculty need to have access to all their Moodle content so they can migrate it over in the future if they need it
    • Tenure review process
    • User access management: tenure review committee and faculty would need access
    • MIIS doesn’t have tenure review, we have contract review.
    • Relatively small group of faculty get reviewed for tenure at Midd.
    • Could we use some sort of non-public archival tool?
  • There are challenges in moving content from Moodle to Canvas.
    • Process strips out user data.
    • We may not be able to do this with future versions of Moodle, either. So even if we maintain a Moodle instance, that may not solve the problem.
  • Why did we decide to have Moodle be a hosted service?
    • We have the resources for this, $ or otherwise
    • What’s the cost benefit analysis of a hosted instance or an internally maintained instance?
    • It was a political decision – maintaining an instance of Moodle for archival purposes would also be a political decision
  • We can’t just export it and keep the data because we need to be able to see how the interaction with students played out
  • Another solution: desktop virtualization system
    • Adjust authentication settings
    • One administrator account
    • If anyone needs to review anything, they can pull up the Moodle instance ONLY via that local computer
    • If there is only one machine and it’s physically located on the College campus, this wouldn’t serve Monterey
  • We need to comply with the policy and keep Moodle pages with student data available for 2 years, the need changes for years 3-7
    • December 2018 is when we’ve told the community Moodle archives will no longer be accessible
    • Beyond that point, Moodle instance does not need to be accessible to more than 2 or 3 people (Joe, Bob, Amy S). Then we can just add people when they need access for review process.
  • We like the idea of a phased approach. One plan for years 1-2 and then emergency/auxiliary access beyond that
    • Not sure, but it will be difficult at best to maintain a piece of software like this on a virtual machine for this extended amount of time
    • Could AWS host this and handle the patches? Is there a way to fire things up in a hosted environment as needed?
  • Moodle is a PHP application
    • That’s a lot of data…
    • This is why promoting services like Panopto/Google Apps is going to be super important going forward
    • Not an obvious win, but could be doable
    • Reticent to commit to 7 years, chances are it’s going to break. The more time, the greater the fragility
    • Can it be kept up to date for 2 years? 7 years? It’s going to break, then what happens?
    • From the web applications side of things, it would be yet another application to maintain, but after initial setup, it won’t need much network. While it’s live, we’ll need to monitor for Moodle security issues that come up and apply patches in a timely manner. Not hard, more of the same, low usage. Probably easier to maintain than most of our other services. Would be a couple days work to get a new VM set up. Then monitoring the mailing list and setting up security patches.
    • How much data are we talking about, storage wise? 590GB
    • Annual maintenance as of 2015 for 1 TB was $1800 – just for storage (licensing, support, maintenance) doesn’t include staff time or other support pieces
  • Immediate needs…
    • We need to make sure we are covered for when the “no” gets vetoed.
    • How can we treat this as an education opportunity? Can we direct faculty make screencaptures of their courses? No administrator actually wants to go digging around in a Moodle page
    • Anyone can install their own Moodle instance on Middcreate
    • Faculty need to be more accountable for their data, but they have an expectation that everything will be available.
    • There needs to be some shift of ownership to faculty who will need this information, but it’s going to be a slow shift. Policy says the data will be accessible for two years, not beyond that.
  • Technology changes – we have no guarantee of what’s going to happen/Canvas’ longevity
  • How do we change the culture? Use these two years (until Dec 2018) to work with faculty to move their Moodle data where they need it to go
    • About 35-50 faculty at Midd
    • To change the culture, we have to constantly keep to policy
    • Ties into the growing need for education around how people interact with and take ownership of their data (digital literacies)
    • A lot of the time, we don’t take threats seriously until we have to
    • Set clear expectations and timeline
    • Communicate with list of relevant faculty
    • We would need to look at faculty over the past 5 years who are going through the tenure process
  • Would still advocate for paying remote learner to host the service through Dec 2018
  • Service availability is what makes things complicated – just downloading and storing static data would not be a problem.
    • Maybe that’s what we do after 2 years? We’ll export and keep the data, but faculty won’t be able to interact with it via a live service
    • In those 2 years, there needs to be good and repetitive communication with faculty about what they might to do to maintain access to the course interaction beyond those 2 years (Moodle hosted on Middcreate, screencapture of course pages, etc)
  • Time frame for moving content out of remote learner to wherever it will go?
    • Our RL contract is up in August – we’d need to have the new location up and ready to go in August – that’s our deadline
    • How long does web team need to make this happen?
      • Theoretically, it would take 1 person 1 week to get things up and running. But, web team is going to be short-staffed and has a substantive project pipeline. Other projects and staffing could make things take much longer.
    • Push for us to reach a decision by April 1 – this is not a joke (Joe)
    • Joe commits to getting the numbers to the group by the end of this week or next week. Joe will work with Billy on the numbers.

 

Notes for Core Team Meeting: Hypothes.is

February 28, 2017

Guests: Jeremy Dean and Nate Angell

The ACTT Core Team met with Jeremy (Director of Education) and Nate (Director of Marketing) from Hypothes.is ( https://hypothes.is ). This followed A two-week “facilitated online experience” using Hypothes.is was led by Sean and Jeremy from late January to early February, and Joe, Sean, and Jeremy had a previous conversation about Middlebury adopting Hypothes.is.

What is Hypothes.is?

  • All-purpose annotation tool.
  • Can be used for fact-checking.
  • Non-profit, open model.
  • Brings back the idea of an annotated web, dropped in early Mozilla projects.
  • Text is highlighted and links to annotations, which can be text, urls, audio, and video.
  • Uses the W3C adopted standards for online annotation.
  • Groups can be created to filter annotations. Ex. MiddAnnotate
  • Can be used as a commenting feature in a document.
  • Adding annotations requires an account.
  • Can be installed as a Chrome browser plugin.

Plugins and Integrations

  • There is a plugin for WordPress
    • Creates an experience similar to CommentPress
    • Is not theme dependent.
  • Canvas plugin
    • Can be used within Canvas, inline with pdfs.
    • Can be an assignment submission type
      • Can be assessed in the SpeedGrader.
  • Plugins are not browser-dependent.
  • Can be self-hosted, not recommended.

Challenges and Questions

  • What happens when content changes?
    • Answer released next week.
    • All annotations are saved.
    • If content changes, annotations will appear in an “orphans” tab.
    • Annotations can be loaded using Internet Archive.
      • Robot.txt files can block archiving.
  • Diigo is similar, can you import content?
    • If it uses the W3C standards
    • Annotations can be exported.
    • Currently, import and export for Hypothesis are supported via API. John Udell has an export utility that uses API: https://jonudell.info/h/facet.html
  • Browser limitations.
  • Content behind a pay-wall has limitations.
  • Some answers are available in the FAQ ( https://hypothes.is/faq/ ).

Middlebury and Hypothes.is

  • Some faculty and programs are using Hypothes.is.
    • Accounts are not tied to Middlebury authentication.
  • Course use vs. Institutional adoption
    • Agreement is currently between the faculty and student for course use.
    • Institutional adoption would involve:
      • Integrating with existing systems (Canvas, WordPress, etc.).
      • Using Middlebury authentication credentials
      • Require adherence to security and data standards.

 

Next Steps

  • Jeremy will share Education Offering documentation with team (DONE).
  • Joe will share Data Classification Policy with Jeremy (DONE).
  • Team will have a follow up meeting to discuss.
  • Jeremy will keep the Team informed on Hypothes.is development.

Notes for Core Team October 18, 2016

Moodle Archiving

  • No courses using Moodle sites after December.
  • Q: What form does the Moodle archive need to take?
    • A: Read-only
  • Q: How long do we need to keep the sites?
    • Policy says 2 years, until December 2018
  • Q: Can Segue decommissioning be used as a model?
    • Q: Can Moodle sites be exported in a usable format?
      • A: They can be exported as .mbz files, we may be able to extract files and pages from them.
    • Q: Is that enough?
      • Review process may need to see student data, this is stripped on an import into Canvas
    • A: Segue model is probably not viable
  • Q: What hosting solutions are possible?
    • Local – considerations are that it needs to be set up the same way as the R-L hosted version. Adam will follow up.
    • Keep at R-L for a reduced cost. Joe will follow up.
    • MiddCreate – concern is the Moodle instance may be too big. Sean will follow up.
  • Q: How long do we have before an archive solution needs to be in place?
    • A: August 2017
  • Other considerations
    • Leng course content. Sean will follow up.
    • Chinese Placement Exam. ODL is working with the Chinese School to use the UNC hosted version of the adaptive placement exam for the near term.
  • This is the start of the conversation, please be prepared to discuss in the future.

 

ACI (Academic Cyberinfrastructure Inventory)

  • Doreen has been adding inventory items (THANK YOU!!!). She is currently working on the items in the ITS Service Catalog.
  • Joe will present the inventory at an all-Library meeting. Please share with people you feel are interested in the inventory, we would like to know how it can be useful. We also need to update the information and make additions.
  • Most of the dependencies are in the ITS list, these will be added.
    • Q: Should dependencies be a cascading or a flat list?
      • A: TBD these are the kinds of questions and discussions we want to have.
  • Needs taxonomy definitions.
  • Extended Team will be asked to review items from their area on a 2-4 times per year. The ACTT will update based on the progress of our evaluations.
  • Inventory is available at http://go.middlebury.edu/aci or http://act.middcreate.net/aci

Values

The Team sorted values collected in Padlet, then each member summarized the values in a category. The results are below.

From https://padlet.com/bcole8/n30ltevlwnfd

Collaborative Partnerships

We engage in our work with Middlebury community partners, colleagues, and amongst ourselves with a collaborative spirit and a commitment to fostering and supporting agency, empathy, and curiosity on all sides.

Critical Thinking

We approach our work from a critical lens, taking into consideration the technical, administrative, as well as pedagogical sides of each recommendation to ensure that solutions truly address underlying needs.

Inclusivity

We strive to serve all our constituents equitably across campuses. This necessitates intentional and mindful communication internally, as well as with the parties represented/impacted by our recommendations and decisions.

Leadership

We lead and participate in complex evaluations, balancing the current needs of the institution with the need to change and innovate. We encourage exploration of what is possible, and inspire others to do the same.

Openness & Growth

We are open to new ideas, suggestions, and ways of doing things; continually inquiring and learning as individuals and a team.

Transparency

ACTT activities are accessible, discoverable and visible to the Middlebury community. Secrecy is utilized as little as necessary.

Notes for Core Team Septembr 13, 2016

Google Hangout

  • Took some time to get the meeting going, meeting was not showing up in some people’s Hangout dashboard
  • Sean showed Joe how to park a Hangout url, we will use that from now on

Canvas LTI Governance

  • Joe shared Bill K’s feedback with the rest of the ACTT
  • Requests should be submitted to ATG/DLC/ODL by faculty, requests should be shared with the ACTT
  • ATG/DLC/ODL members will evaluate the LTI
    • Test installation
    • Confirm utility with requestor
    • Check use of student data by the LTI
    • Complete the SaaS if necessary.
  • ACTT will confirm completion of the evaluation, and will evaluate for the sub-account and platform levels.
  • A flowchart of the process is available here.
  • Q: Can we create a list of LTIs and where they are in the process?
    • A: yes. Let’s start with a spreadsheet, then see if that is adequate
  • Q: Do we know what LTIs have been installed already?
    • A: yes. Canvas can export an LTI report. Joe will run the report and share it.
  • Attendance tool was disabled, it creates conflicts with the gradebook. We’ll collect requests, examine the feature, and maybe address the conflict with education for the following semester.

Web Conferencing/Adobe Connect Replacement

  • Bob, Sean and Joe met with Petar and Mack to discuss a plan for looking at 4 services in a short amount of time. The hope is we can either eliminate a few, or identify one that is noticeably better than the others.
  • In one meeting the Extended Team and other guests will spend 10-15 minutes in each services, test features, then jump to the next service.
  • The invitation will be shared on the All Things Digital Slack channel, as well
  • Interested faculty can join via invitation.
  • Plan is to do this at the Extended Team meeting on October 4th.
  • Bob, Sean, Petar, Mack and Joe will design a detailed plan on October 3rd, Joe will share out with the meeting invitation.
  • We will have an open In-progress Project meeting on October 11th to discuss the results.

Notes for Core Team May 18, 2016

Canvas

No decision yet on Canvas. LS pilot is up and going with user/group provisioning via the Course Hub.

Basic Canvas overviews will need to be added to Language School orientations.

Discussion of location for Midd-created documentation about Canvas should live. http://digitallearning.middcreate.net/ ? Library and ITS wiki?

Inventory

Joe has been trying out Palladio and Google Fusion Tables for visualizing the data. Mixed results, no tools totally satisfactory yet. Bob will put Joe in touch with META Lab who may have some suggestions around visualization.

What questions come to mind looking at the inventory data?

  • How many tools are in the life-cycle stage bucket compared to the total number of tools? Is this sustainable?
  • What criteria would trigger an evaluation? Can this be a score?
  • Agreement renewals
  • Budget
  • Utilization
  • Changes in the environment
  • New pedagogies and practices
  • New programs

 

The next large goal is to make 1/3/5 projections for items in the inventory so that the administration & community at large has some idea of where we see this inventory shifting.

Assignment for the next meeting: Look at the Classification 2D Array and pick an intersection. Come up with a set of questions that will help us make projections for 1, 3, 5 years out.