Skip to end of metadata
Go to start of metadata

Following Kate Ellis' question (through the mailing list) from Dec. 21, 2007:

Who is the audience for this collection?

Kate Ellis: I assume the answer is many different people: T&L consultants and support folks, faculty and perhaps designers & developers. From my admittedly limited point of view, I was imagining this collection as being something I would access and share with the instructors that I work with. How are other people envisioning this?

Mathieu Plourde: I think the audience would be segmented. Each institution would promote what they want to promote to their faculty members, and the global repository would be a place for T&L professionals who would seek fresh ideas. As someone who has to support faculty members on a daily basis, I need job aids, examples, training material, promotional material, in order to show something concrete, something professors can relate to. But I would not send all my professors to an external source. I would filter what applies to our context, and put it on our support website. So, if there were some kind of flagging process, were I could decide which example coming from a repository I would like to share with my professors, that would be awesome. Have a look at my diagram to get a better sense of what I am thinking.

Mathieu Plourde (3-5-2008): I think the idea that this repository will primary be targeted at ourselves (instructional designers, IT support people, managers) has been widely accepted. It will become a tool for all of us to promote good practices at our faculty members (correct me if I'm wrong). Consider the following points:

  1. It should have a great value to us (members of the Sakai and OSP T&L Followers);
    1. We should assume the responsability to share resources from our institutions. That way, the vocabulary remain be the same.
  2. It should be open to anyone who wants to look or contribute, especially Faculty members.
  • No labels


  1. One way to achieve what Mathieu suggests¿flagging resources from a central repository for local consumption¿in the example of the community library would be to tag "flagged" resources there with a specific tag and then expose a feed from that specific tag on a local website.

    One modification to the library that would assist with this is to enable tagging separately from editing the resource record: user-based tags. We'll look into that.

    1. I think that tagging is the most useful way to classify information. If Drupal could

      1) have a tagging capability (user driven, not extracted for the text) or
      2) generate tags out of its current database,

      that would be awesome.

      In order to be efficient, we would need the community to contribute to tag definition. This confluence site would be perfect for that in my sense. Graduate students from Marist could be alerted every time something is added to review it and assure constance thoughout the database.