We are looking for ideas for presentations (and presenters!), tutorials, discussions, etc. to include in the March 14 user group mtg which is immediately after the SPARC mtg. Some of the current ideas are:

- update on 1.8 and beyond

- innovative projects from the community

- tutorial on Discovery (faceted search and browse) or Mirage

- structured networking (this is always really well rec'd by attendess) - use a conversation starter, like: What are your current challenges with your repository/DSpace? Or what is your most pressing issue/s with your repository?   

Please include your ideas/suggestions here or send me an email.

  • No labels

7 Comments

  1. Some ideas/suggestions: at OAI 7 DUGM we had a Repository Manager Session - we were working in five groups discussing best practices in the following areas of repository management:

    1. Budget: Managing the repository budget and responding to user needs in line with resources;
    2. Strategic planning: Developing a strategy and costing for the future development of the repository;
    3. Fundraising: Sourcing funding opportunities for repository projects;
    4. Workflows: Developing workflows to manage the capture, description and preservation etc. of repository outputs;
    5. Personnel: Coordinating and managing activities of repository personnel and coordinating repository development with associated departments. 
  2. Best practices of repository management is a great idea--it's certainly something I would want to talk about.

    What about a features brainstorming session?  I imagine there are any number of people out there who aren't confident enough to create a JIRA ticket with an idea for an improvement they'd like to see. 

    1. Amy, what types of best practices particularly appealed to you from Iryna's list? What are the most common challenges you face and would like to hear how others have addressed them? 

      1. I'd really love to hear what others are doing with budget and strategic planning.  Repositories, for so many of us, are a 'side' project fit in where we can find the staff time and the money.  How have those who have a full-time repository staff/operation, how are they budgeting for the people and equipment?  Where do they see their services going in the future, and what are they planning to give up (if anything) to get there?

        At Missouri. we're a small, part-time staff with disparate skills.  We in Columbia work with three of our four sister campuses for broad planning purposes, but each campus is responsible for it's own 'territory' when it comes to adding material.  There are many directions in which we could move, and there is some thought on the part of administration as to where that is, but I'm not sure that we've a cogent plan at this point to do all that we could do.  It'd be nice to hear how others got to where they are so we have some ideas about paths to taek.

  3. No other suggestions from me.  All that has been suggested would be welcome!  I would though also like to expand on Amy;s comment that a new features brainstorming would be welcome but it would be good to also include improvements to what already exists (the bug bears if you like) within DSpace

  4. I received a suggestion last night that a discussion about integrating other frameworks with DSpace would be welcome at this session.  The suggestion stems from a discussion on Dspace-tech yesterday on the topic: http://sourceforge.net/mailarchive/message.php?msg_id=28749459.

  5. For some, a repository and DSpace will always be about publication data.  For others though, publication data was just the first hurdle.  Publication data is a large part of the research paradigm, but it is only one part.  There are many other facets which integrate with publications; such as people, projects, funders, grants, organizations (depts & research teams), patents, equipment, etc.  These other facets also need describing in controlled metadata.  Dublin Core has little to offer here.

    My understanding of the European CRIS movement is that it is mainly for decision support of research managers.  Exposing data in CRIS for discovery is an afterthought, or not provided at all.  However, the Library's perspective, and one now many times fired with Knowledge Transfer/Exchange/Translation, is that discovery is foremost.  Having all research facets on one platform and integrated one with the other, enhances discovery and SEO.  I believe there is a role here for repositories to play, and not one that simply plays nicely with other on-campus silos, all separate but equal.

    Can DSpace move into this area and provide discovery & integration with these other facets?  Should it?  Can the VIVO ontology or CERIF format be used to scale up DSpace for inclusion & integration of these other facets?  If so, that would answer the paucity of DC (cf. "MARC's vile progeny").

    Many people report that OA IRs are not compelling to their faculties.  Can DSpace IRs move to a place that would be compelling to faculties?  And thus attract higher rates of publication deposit?