Home > ACErep, Workshop > Priorities from workshop

Priorities from workshop

Thanks to everyone for coming to the workshop this morning.  In August.   The academic dead zone!

Just to quickly post here our priorities that Peter presented at the end of the morning.  I’ve tried to reorganise them into the implicit activities and deliverables that were felt to be essential and the more explicit deliverables that we collaborated on throughout the morning.

(Here is the original document)

Please feel free to comment if you think we’ve missed anything crucial or anything new has occurred to you.

Implicit

  • Dissemination (user engagement emphasised as crucial)
  • Language  (no technical jargon!)
  • Usability / simplicity (e.g. RLO-CETL)
  • Supporting the community of users (will comprise at least 2 distinct groups – those that simply use resources they find and those that use AND (re)deposit.)
  • No authentication barrier for discovery (Open Access)
  • Authentication required for depositing

Explicit priorities

  1. Resources presented in the context of specific learning/assessment outcomes (will guide discovery)
  2. Discovery / use from VLE (resources need to be easy to embed in VLE[s])
  3. User commenting (optional authentication would allow practitioners to comment on resources potentially providing a mechanism to link theory and practice)
  4. Use of existing authentication mechanism (LDAP)
  5. Deposit from the VLE (not seen as a priority at this time and outside scope of current project)
  6. Social networking integration (low priority – likely to be driven by community at later date)

Revisiting this list, it occurs to me that we’ve sort of skirted round the deposit question…is a simplified deposit tool (or tools) into the respective repositories an implicit or explicit deliverable do we think (technical issues not withstanding)?

Advertisements
  1. ljshipley
    August 6, 2010 at 9:59 am

    Implicit, I think, even if – given the short timescale we’re dealing with – all that is is a simple, user-tested-to-infinity web form that forwards deposits and accompanying information to the relevant repository manager.

    Thanks for the workshop, also. I found it very useful to define the nature of the projct – even though I did commit the sin of geekery a bit too much 🙂

    • Nick
      August 6, 2010 at 10:11 am

      Thanks Lauren. I agree it is probably implicit given the discussion yesterday and, as you suggest, we can certainly develop a web-form for mediated deposit tailored to user-requirements before worrying about the technical side of automating deposit into the respective repositories.

      However, as we discussed in our mini geek-off, it would be a great outcome both for YSJ and for the project if we could develop a SWORD client to achieve this, depending on PTFS developing SWORD functionality for Archivalware of course

      • ljshipley
        August 6, 2010 at 10:13 am

        Yep – that’s definitely something to aim for, perhaps with the simpler version as a stop-gap measure.

        I like the term geek-out very much…

  2. Jakki Sheridan-Ross
    August 6, 2010 at 10:07 am

    yes, I agree its implicit. Many of the OER project workshops over the last year have highighted this requirement and also the need for less metadata (I know, that’ll be controversial! but that was definitely the trend!)

    • Nick
      August 6, 2010 at 10:19 am

      Yes – ukoer guidelines were certainly towards lightweight metadata – see this post on Lorna’s JISC CETIS blog(this post at ukoer outset but comments link to discussion throughout the programme.)

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: