You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

 ITEMMENTIONSTIMEFRAMECOMMENTS
AConsolidate platforms / Samvera decision / exit bepress / migrate legacy collections / sunset systems111, 3 
BService management / role clarity / appropriate staffing level71, 3See also I, below
CComplete and public-facing policies (possibly including collection), contact information51, 3Some suggest consistency across repositories (see also I, below)
DDevelop/define CUL-wide repository strategy; clear purpose for each repo; clarify place of repositories in CUL priorities51, 3Don't base on CU/CUL org structure
EEnsure preservation of repository content31, 3 
FParticipate in selected open sources communities23Presumes some consolidation of platforms
GImprove discovery (and interoperability to support it)23 
HEvaluate / explore existing and potential external partnerships and shared repos (e.g. BHL, Internet Archive, other)21, 3 
IAdopt / implement repository principles document across CUL21See also B, C above

 

SINGLE MENTIONS

  • RepoExec should meet less frequently
  • Support for large (>3GB) datasets in eCommons (i.e. Globus)
  • Greater transparency on part of RepoExec, especially for liaisons
  • Complete documentation for all repositories
  • Define "metadata of record," in particular to support movement of content from one repo to another
  • Clarify repository landscape (support staff understanding of it)
  • Clarify whether collection and deposit of Cornell faculty papers is a priority (and if it is, staff appropriately)
  • Better communication among repository staff to share ideas, challenges, goals, etc.
  • PR / marketing support for repositories to improve visibility
  • Improve or modernize feature set in repositories; better support for customization

 

PRIORITIZING

  • Day to day work experience / pain points
  • Previous RepoExec discussions
  • Issues of technical debt, need to consolidate platforms
  • 1-year: things that can be done with current knowledge and resources
  • Funders' public access requirements (for data)
  • Lifecycle and longer-term thinking
  • Desire to break down siloes

OTHER COMMENTS

  • RepoExec underutilized / out of the loop on discussions, decision-making
  • Convening service managers to establish more uniform practices could be useful
  • Lack of authority means RepoExec can't do much; demoralizing
  • Suggestion that membership skews too much towards "top level," should include more functional experts
  • Need to hear CUL/UL commitment regarding repositories

HOW RESPONSES WERE TABULATED

  • Repetition of the same idea within a single survey response was only counted once
  • Where multiple/similar ideas were combined into a single item in the table above, if the response included two or more different elements of the consolidated item, each element was counted
  • No labels