MO-Space»Minutes 20080520

Minutes 20080520

MO Space meeting

Minutes - DRAFT

May 20, 2008

Attendees: Ann Riley, Mary Aycock, Diane Oerly, Anselm Huelsbergen, David Crain, Adrienne Arden, Wayne Sanders , Hardy Pottinger, Felicity Dykas, Amy Lana, Rhonda Whithaus, Judy Maseles

1) Meeting with Office of Sponsored Projects and the Provost’s Office

A group of people, including Ann Riley, met with the Office of Sponsored Projects and the Provost’s Office. The meeting went well. While the focus of the meeting was NIH projects and compliance, the institutional repository was discussed and there was much support for an MU institutional repository.

The first project in MO Space will focus in NIH projects. These projects involve multiple schools and departments.

Follow-up:

  • Kate and Diane are following up on information to faculty.
  • Ann is working with Lisa on a template regarding copyright legalities. In looking at other repositories, it looks like we need to make sure publishers have agreed to posting in MO Space. See Oregon as an example. We need to develop a form for that, too.

2) Server

Hardy reported that initially MO Space will be on LSO servers. We will look for more space as needed. The new mainline and backup storage are in place. Hardy is setting up DSpace version 1.5 and he reports it has some nice features for setting up and running DSpace. DoIT has a deadline of a week from Friday to gets its work done. Ryan Woodsmall is working on it. His supervisor is Brian Dourty. MORENet did some of the programming for the pilot.

The goal is for authentication to be via Shibboleth.

Ann mentioned that Tim Donohue is a programmer at the DSpace installation at the University of Illinois at Urbana-Champaign and is willing to help us. [His wiki: http://wiki.dspace.org/index.php/User:TimDonohue]

3) MO Space mission

See sheet. We will need to make this less introductory when we post it on our MO Space website. Ann will work on that.

4) Workflow Planning

Adrienne reported that the MU Libraries Acquisitions Department is looking forward to training and instruction. Amy reported that they envision a process similar to what is done with monographic acquisitions for the library. She figures they can quickly move digital information into DSpace. They may have a role in contacting faculty for NIH compliance.

5) Collection policy

A subgroup was formed to develop this. The group includes Anselm, Ann, and Judy. Ann will speak to Diane about serving as an HSL representative. The collection policy will detail what will be accepted and what will not be accepted. [Library?] directors will need to agree with the policy.

6) Basic structure proposal

The group agreed with a hierarchical structure for the communities feature. This will follow the university structure. Example: MU / School / Dept / Center

Interdisciplinary works will be listed under all relevant departments. It isn’t clear what we will do with a work published by an author which is not related to the author’s department affiliation. Ann suggested that we will need to form a small group that will handle decisions such as this.

The structure will be useful for authentication functions. We agreed to establish entries as needed, rather than build the whole structure at once. We are aware that departments and their affiliations sometimes change.

Felicity will determine an authoritative source of information for department names will be.

7) Workflow

Questions to consider: Should we review before posting? Should we allow authors to self-post?

Hardy noted that DSpace has built in features for workflow that can be customized.

8) Content

It was agreed that it will be useful to get resources into MO Space before marketing begins in the fall.

Possibilities other than NIH works:

  • Agricultural Experiment Station publications. Maybe. They sell some of their publications.
  • Review web crawl that Judy did.
  • University of Missouri Press publications.
  • Query IT pros and find out what is at risk.
  • Look at Bengal. Departments have been asked to move stuff off of Bengal and onto department sites. Some of this might be appropriate for MO Space.
  • Look at MERLIN to identify online MU and UM publications.
  • Librarians should use their connections to identify publications.
  • Librarians should model behavior and post their works.
  • Undergraduate research projects.
  • Student literary magazines and journals.
  • Mizzou weekly.
  • College of Ed has portfolios. These are not permanent and are not always scholarly.
  • Pictures of the year.
  • Active symposia held at MU.
  • Review inventory created by an IR working group in 2003.

7) Other campuses

Ann reported that UMKC is interested in participating next year. UMSL expressed interest for their Mercantile collection.

8) Miscellaneous

Hardy noted that MO Space will be able to talk to OAI and Google Scholar. We will submit works to PubMed on behalf of authors. If we follow the model used at the University of Illinois, we will send an ID back to the author and they will be able to review the entry before it is posted by PubMed.

Exploring DSpace and practicing: Interested persons should request back end permission to the pilot installation from Hardy. We can consider the pilot a sandbox. Keep in mind that the information is publicly available.

Do we expect a mandate at MU that MU-supported research and scholarly output will have to be included in MO Space? No.

Having permanent URLs will be a plus for authors.

Diane asked that we use a wiki to collect and keep information. Judy and/or Hardy will set up a MO Space wiki. Ann will send initial content.

9) Next meeting – tentatively scheduled for June 19

  • We should look at the new DSpace before the meeting.
  • Report on copyright matters.
  • Report on the collection policy.
  • Look at workflow options.
  • Consider department structure and form of names that will be used.
  • Workflow group report.
  • NIH group: look at list of works to be included. Consider best way to get resources into a DSpace workflow.

PmWiki can't process your request

Cannot acquire lockfile

We are sorry for any inconvenience.