This document discusses the current state and future plans for the CUNY DSpace repository. It notes that the repository currently lacks meaningful commitment and visibility across CUNY institutions. The plans are to promote the repository, train staff, formalize sub-community administrators, and deploy the new DSpace 1.5 features like SWORD to allow more decentralized depositing across CUNY.

1. DSpace at CUNY Kevin Reiss [email_address] City University of New York Office of Library Services NISCamp 2009 http://dspace.nitle.org/handle/10090/438 http://www.cuny.edu c

3. 1 University Center (All CUNY PHD Programs)

4. 6 Community Colleges

6. 6,100+ full-time faculty

7. 21 Libraries

9. One single CUNY community

10. 23 current sub-communities

13. 544 current objects < 486,000 plus CUNY community

15. Repository managers have little contact with CUNY Academic Communities

16. Batch ingests for existing collections must currently run through NITLE rather than repository administrator

17. Local library contacts have wildly varying levels of technical skills

18. Lack of CUNY-wide user directory (LDAP) limits authentication options

21. Grey literature from CUNY research institutes

22. CUNY-published journal content

23. Theses and dissertations

25. Behavior customization and unmediated deposit (SWORD)

26. Current Main Community View

27. Current Sub-Community View

30. Warehouse for archival materials

32. New CUNY-wide repository promotion and staff training program

33. Start a formal sub-community administrator program

34. New collection building opportunities with the SWORD repository deposit protocol

35. Rebranded Community Home

36. Rebranded Search Results

38. Public launch to University and CUNY Library community to highlight new Manakin-based user interface

39. Identify noteworthy test collections to highlight in our campaign

40. Staff DSpace toolkit with sample workflows and metadata templates

45. Find one single point of contact at each CUNY institution

46. Use new reference and training materials as a means to get one substantive collection mounted from each CUNY institution

47. New half-time staff member will be devoted to repository administration, outreach, and training

48. Regularly meet/contact with this new group

50. Batch loading via spreadsheet/zip file has been somewhat successful but clunky to assemble

51. Need a means to connect the repository with other collection-building tools used by libraries and other campus units

52. Need to find a way to integrate DSpace deposit directly into exiting staff workflows

53. Current CUNY DSpace Environment

56. http://www.swordapp.org/ Current version is 1.3

58. Update/delete existing objects

59. Works with built-in DSpace authentication and mediation rules

60. SWORD-Enabled Environment