Institutional Repositories


  • General Discussion (discussion led by Sunny Yoon, Digital Resources Coordinator at the City University of New York)
    • Palmer School has IMLS grant to place interns in CUNY special collections to work on digital projects, goal is to encourage institutions to put the information on the web and find new ways to present it. Still in the planning stages for technology and methodology.
  • Content
    • Records are not immutable, they change more often than expected.
    • Guidelines, standards, and best practices are needed. No one standards body to turn to for this. (Cornell guidelines).
    • Variety in how institutions (large vs. small) store existing digital data, availability of backups, standard formats.
  • Institutional buy in
    • Cultural issues - someone needs to be responsible for the repository.
    • No consensus on the definition of "institutional repository"
    • Slow uptake
  • Tech. Infrastructure
    • File formats and migration
      • Handling digital video and other multimedia formats.
      • Versioning may be useful
      • Technical standards/open formats
    • DSpace
      • Messy, hard to work with, requires specialized.
      • Still widely used.
    • Fedora
      • Many evaluating this option
    • Custom software
      • oracle -> xml -> lucene
  • Presenting to the public
    • Goes hand in hand with intellectual property, when to open up content.
  • Metadata
    • Challenges in converting complex metadata (NVPL, VRA, other schemas) to other standards like DublinCore, MODS
    • Interoperability is hard.
  • Exposing, harvesting OAI
  • Intellectual property issues
    • Authenticating and protecting content.
    • Theft of grant ideas in medical field.
    • Copyright legislation
**
* Folksonomies
    • Searching vs. browsing user behavior for finding content.
    • Text mining as a future application for linking content together.
    • "Authoritative metadata" is expensive and time consuming, is crowd sourcing an alternative?
  • Resources