#hypothes.is

/

      • badon joined the channel
      • realzies has quit
      • realz joined the channel
      • floryst___ joined the channel
      • linuxconformer has quit
      • waloo has quit
      • waloo joined the channel
      • floryst___ has quit
      • realzies joined the channel
      • realz has quit
      • m1yag1 joined the channel
      • robla[m] has quit
      • robla[m] joined the channel
      • hslack
        <james.paradiso> I am in a very similar scenario as @steelwagstaff and appreciate him articulating these concerns so clearly. I’m also thankful to @judell and @robertknight for the excellent summary (above). Third party accounts seem to make good sense here (imo), especially if it means a more immediate/practical timeline for development to launch. The search limitations would be slightly displeasing, but my intended
      • conversation) is centralized to Pressbooks (with no external annotations to filter in), so it might be worth it to gain the SSO functionality. Lack of private group creation (at least for now) shouldn’t pose much of an issue either, as faculty could direct their use of the annotation pane to host multimedia and text/notes that supplement the students’ reading experience. (I’d like to open it up for a wider use cas
      • efficiently search annotations, it would be quite challenging.) *Question:* If we already have a Canvas LTI that enables SSO into Pressbooks, could a properly configured Pressbooks+Hypothesis plugin do the trick to link users “anonymously” to all three products? If so, what would it take to make that happen? *Scenario* (Course 1): --The Hypothesis+Canvas LTI app becomes publicly available (is designed to use “th
      • into Canvas Course 1. --Pressbooks+Canvas LTI is configured in Canvas Course 1 which also enables SSO (separately) into a Pressbooks instance with Hypothesis installed/network activated. ---What is the likelihood that the credentials/user information stored/exchanged during the Hypothesis+Canvas LTI sign-on will carry over to the Hypothesis annotation pane “log in” in Pressbooks when launched from the same Canvas cou
      • quite new to the scene, so my terminology and phrasing may be a bit incorrect or unclear. I appreciate your patience.
      • jeremydean has quit
      • jeremydean joined the channel
      • realzies has quit
      • realzies joined the channel
      • anavarre joined the channel
      • linuxconformer joined the channel
      • anavarre has left the channel
      • m1yag1 joined the channel
      • <steelwagstaff> Hi Jim--I’m thinking along very similar lines. My plan would be to see 1) whether we can configure the hypothesis plugin for WordPress to implement a ‘third-party account’ using the reference implementation at https://github.com/hypothesis/publisher-account.... If we’re successful with this, then we could allow us to create Hypothesis accounts when new Pressbooks accounts are created. 2) S
      • Shibboleth plugin. This means that users would use their ‘NetID’ to create a Pressbooks user account. If step 1 were properly configured, they’d also generate a third-party hypothesis account at the same time, I’m hoping.
      • realz joined the channel
      • realzies has quit
      • realzies joined the channel
      • linuxconformer has quit
      • realz has quit
      • _6a68 has quit
      • _6a68 joined the channel
      • m1yag1 joined the channel
      • <james.paradiso> I think the plan is great, Steel, and I’d love to see it come to fruition sooner rather than later. Is this a venture that the Hypothesis dev team would also support or would we be going solo (with our individual and/or our dev teams respective expertise)? How do you work plan to work through the student data privacy piece in all this? The one repeated comment I get from my dev and LMS admin teams ar
      • out by the third party vendor (in this case Hypothesis and/or Pressbooks) and then send them through the Information Security Office at my university (a long process), or configure whichever LTI to “anonymous” in the privacy setting (which allows for a random number to be assigned each user, but I’m not sure how trackable that is, as there is no name, email address, et al. associated with the user). I know privacy
      • considering we are both from rather large public universities, I thought you may have had a similar experience. (My university, for example, is VERY conservative when it comes to student data, so I’m confronted with this concern at every turn.)
      • tilgovi joined the channel
      • PaulCapestany joined the channel
      • realzies has quit
      • realzies joined the channel
      • badon has quit
      • chjh has quit
      • ylc1432[m] has quit
      • M-rongladney has quit
      • M-steko has quit
      • M-almereyda has quit
      • opeanuts[m] has quit
      • M-sraja has quit
      • Matthew[m] has quit
      • robla[m] has quit
      • VientesiesDeJuli has quit
      • tk[m] has quit
      • stoneridge has quit
      • M-dizzi90 has quit
      • akaibu[m] has quit
      • M-Giom has quit
      • M-HirmeS has quit
      • chjh joined the channel
      • book` joined the channel
      • luizirber joined the channel
      • book` joined the channel
      • <steelwagstaff> Pressbooks won’t matter with user accounts/data because we’re self-hosting. All that data is on Unizin servers as is our LTI tool. So it’s as though it were a ‘home-grown’ LTI tool (provided you think of Unizin as ‘home.’ Hypothesis does store annotations on their servers, but if that’s an issue, they can help you/us set up our own self-hosted clients and h server and do it all ourselves.
      • might be better in your case, Jim?
      • rektide joined the channel
      • <james.paradiso> Thanks for the follow up, Steel. The admins have been adamant about me keeping all data anonymous, but I will touch base with them again to see how they ultimately view Unizin’s ‘home’ space (in so far as security). This is the first I’ve heard of setting up self-hosted clients and an h server. How might one pursue that route? I’m DEFINITELY interested! In the meantime, I’ll touch base
      • think. Thanks!