Your SlideShare is downloading. ×
0
Where Are We “AT”? A Status Report on the Archivists Toolkit Presenters: Brad Westbrook  Kate Bowers Jody Lloyd Thompson  ...
Project Update Bradley Westbrook AT Project Manager UC, San Diego
Overview <ul><li>Project Update </li></ul><ul><ul><li>Application Overview </li></ul></ul><ul><ul><li>Phase 1 Summary </li...
Application Overview <ul><li>Open source, relational database application to support archival processing and production of...
Phase 1 Summary <ul><li>Started June 15, 2004 & concluded 31 January 2007 </li></ul><ul><li>Key objectives targeted were: ...
Beta Testing <ul><li>Application thoroughly tested by AT specification team from April to July 2006 </li></ul><ul><li>Prog...
1.0 Release & Uptake <ul><li>Version 1.0 of the AT was released on December 17, 2006 </li></ul><ul><li>1,130 unique downlo...
Implementation <ul><li>36 respondents to a survey conducted Feb. 19-March 9, 2007 among ATUG-l members </li></ul><ul><li>6...
Support Services <ul><li>ATUG-l (Archivists’ Toolkit User Group) </li></ul><ul><ul><li>Nearly 500 members at mid-August </...
Phase 2 <ul><li>Began February 1, 2007 </li></ul><ul><li>Objectives </li></ul><ul><ul><li>Refine performance of version 1....
1.1 Release & Features <ul><li>Enhanced Records </li></ul><ul><ul><li>Accession </li></ul></ul><ul><ul><li>Repository </li...
AT Project:  www.archiviststoolkit.org Staff Email address:  [email_address]   AT Sandboxes:  http:// www.archiviststoolki...
Society of American Archivists Annual Meeting, August 30, 2007 Jody Lloyd Thompson Implementing the AT: Working with Staff...
Overview <ul><li>Brief look at AT </li></ul><ul><li>Working with staff and student assistants </li></ul><ul><li>Working wi...
Brief look at AT <ul><li>Accessions module </li></ul><ul><li>Resource module </li></ul><ul><li>Other features </li></ul>
Working with staff & student assistants <ul><li>Manage staff & student access </li></ul><ul><li>Create user manuals for st...
Manage staff & student access <ul><li>Access classes: </li></ul><ul><ul><li>Superuser (5) </li></ul></ul><ul><ul><li>Appli...
 
 
Working with staff & student assistants <ul><li>Manage staff & student access </li></ul><ul><li>Create user manuals for st...
 
 
 
 
 
 
Impact on staff <ul><li>Improved functions in the Archives </li></ul><ul><ul><li>Reference services  </li></ul></ul><ul><u...
 
 
 
Impact on staff <ul><li>Improved functions in the Archives: </li></ul><ul><ul><li>Reference services  </li></ul></ul><ul><...
 
 
 
Impact on staff <ul><li>Improved functions in the Archives: </li></ul><ul><ul><li>Reference services  </li></ul></ul><ul><...
Working with IT <ul><li>Establish good communication with IT </li></ul><ul><ul><li>Create a Wiki </li></ul></ul><ul><li>Cr...
 
Working with IT <ul><li>Establish good communication with IT </li></ul><ul><ul><li>Create a Wiki </li></ul></ul><ul><li>Cr...
Working with IT <ul><li>Install AT </li></ul><ul><li>Import legacy accession records </li></ul><ul><ul><li>Completed at Ge...
Thank you <ul><li>Jody Lloyd Thompson </li></ul><ul><li>Georgia Institute of Technology </li></ul><ul><li>[email_address] ...
Big Scale, Little Scale: Consortium vs Multiple Implementations of the AT at Harvard Kate Bowers Harvard University Archiv...
Big Scale, Little Scale: Consortium vs Multiple Implementations of the AT at Harvard al Kate Bowers Harvard University Arc...
Scalability <ul><li>Part-timers / 1 collection </li></ul><ul><li>25+ FTE / thousands </li></ul><ul><li>100,000+ feet overa...
AT Working Group <ul><li>with library IT, to test installation and scalability of AT </li></ul><ul><li>further investigate...
AT Working Group <ul><li>investigate issues of importing legacy data (collection management as well as descriptive data) <...
Using the latest information technology... [Grace Hopper working on the development of the MARC I computer, 8/4/1944]  (UA...
AT Working Group <ul><li>with library IT, to test installation and scalability of AT </li></ul><ul><ul><li>Oracle installa...
Working closely with colleagues... “ Some new data on the weight of a crowd of people” (HUK 363p (Fig. 8))  Original photo...
AT Working Group <ul><li>further investigate AT functionality and develop recommendations for Harvard-specific development...
Central / distributed administration and security levels ... Plan showing Position of Reading Room [central portion of blu...
AT Working Group <ul><li>recommend administrative rights (security) and functionality to be centrally controlled </li></ul...
Pull in legacy data... [Tug of War Team, photograph, 1888] (HUPSF Tug o' War (6))  The ’88 worn by all of them probably me...
AT Working Group <ul><li>investigate issues of ingesting legacy data (collection management as well as descriptive data) <...
Investigate the diversity of workflows ... Harvard College Library Department of Classification and Cataloging [flow chart...
AT Working Group <ul><li>investigate the diversity of workflows,  processes, & procedures in Harvard archival repositories...
AT Working Group <ul><li>Report the cost of central support </li></ul><ul><li>Identify the benefits, particularly cost sav...
Division of labor (not final!) <ul><li>Consortium Responsibilities : Central </li></ul><ul><li>Create and manage the datab...
Division of labor (not final!) <ul><li>Consortium Responsibilities : Central </li></ul><ul><li>Identify and train liaison ...
Division of labor (not final!) <ul><li>Consortium Responsibilities   : Central </li></ul><ul><li>At Harvard, but maybe not...
Division of labor (not final!) <ul><li>Consortium Responsibilities: Distributed </li></ul><ul><li>Liaison in repository cr...
Division of labor (not final!) <ul><li>Dual responsibilities </li></ul><ul><li>(needs central support, but will also requi...
Conclusions? <ul><li>Wide-scale end-user testing September-October 2007 </li></ul><ul><li>Mid-term project report late Sep...
The end <ul><li>http:// isites.harvard.edu/icb/icb.do?keyword =k15469 </li></ul><ul><ul><ul><li>Bugs </li></ul></ul></ul><...
Can you get AT without IT? Implementing the Toolkit at a small college repository Katherine Stefko Edmund S. Muskie Archiv...
Archives Overview <ul><li>3 FTE </li></ul><ul><li>100+ mss. collections, 1,500 l.f. of College records, 14,000 rare books ...
Technical Underbelly <ul><li>Installed v. 1 and 1.1 (beta) as networked app for testing and implementation </li></ul><ul><...
Accessions Module <ul><li>Fully implemented </li></ul><ul><li>Tracking new accessions </li></ul><ul><li>Adding legacy pape...
 
Importing Legacy Accessions <ul><li>Tab delimited text (or XML) </li></ul><ul><li>Low barrier ingest process </li></ul><ul...
Description Module <ul><li>Implementation on hold </li></ul><ul><li>Tested adding new records </li></ul><ul><li>Consolidat...
Decision Factors <ul><li>Legacy data and AT divergences </li></ul><ul><li>Bugs </li></ul><ul><li>Application limitations <...
IT Needs <ul><li>Installation and upgrades of application </li></ul><ul><li>Clean up of legacy descriptive data </li></ul>...
It’s not just a database… It’s a work style <ul><li>Encourages/enforces compliance to professional standards and best prac...
It’s not just a project, It’s a process.. <ul><li>Active user community that is contributing to the application’s developm...
 
Get Involved <ul><li>Join the community </li></ul><ul><li>Contribute feedback and helper apps </li></ul>
Upcoming SlideShare
Loading in...5
×

Here Is View Using The Search Query Function To Find All Collections That Deal With Textile

687

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
687
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Transcript of "Here Is View Using The Search Query Function To Find All Collections That Deal With Textile"

    1. 1. Where Are We “AT”? A Status Report on the Archivists Toolkit Presenters: Brad Westbrook Kate Bowers Jody Lloyd Thompson Katherine Stefko SAA Annual Meeting, 2007
    2. 2. Project Update Bradley Westbrook AT Project Manager UC, San Diego
    3. 3. Overview <ul><li>Project Update </li></ul><ul><ul><li>Application Overview </li></ul></ul><ul><ul><li>Phase 1 Summary </li></ul></ul><ul><ul><ul><li>Product Uptake </li></ul></ul></ul><ul><ul><ul><ul><li>Downloads </li></ul></ul></ul></ul><ul><ul><ul><ul><li>User survey </li></ul></ul></ul></ul><ul><ul><ul><li>Support Services </li></ul></ul></ul><ul><ul><li>Phase 2 Objectives </li></ul></ul><ul><ul><li>Release 1.1 & Features </li></ul></ul>8/30/2007 AT for SAA Annual Meeting
    4. 4. Application Overview <ul><li>Open source, relational database application to support archival processing and production of access instruments </li></ul><ul><li>Promote data standardization </li></ul><ul><ul><li>Based on DACS, ISARR (CPF) </li></ul></ul><ul><ul><li>Exports EAD, MARCXML, METS (containing MODS or DC) </li></ul></ul><ul><li>Promote efficiency </li></ul><ul><ul><li>Integrate range of archival functions </li></ul></ul><ul><ul><li>Repurpose data—multiple outputs from data recorded </li></ul></ul><ul><ul><li>Automate encoding and reporting </li></ul></ul><ul><li>Lower training costs </li></ul>8/30/2007 AT for SAA Annual Meeting
    5. 5. Phase 1 Summary <ul><li>Started June 15, 2004 & concluded 31 January 2007 </li></ul><ul><li>Key objectives targeted were: </li></ul><ul><ul><li>Recording accession, description, and location information for resources, as well as name and subject authorities, and </li></ul></ul><ul><ul><li>Exporting EAD 2002, MARCXML, METS (MODS / DC), and 30 different administrative and descriptive reports, such as acquisition statistics, accession records, shelf lists, subject guides, etc.; </li></ul></ul><ul><ul><li>With support for importing legacy data in EAD, MARCXML, and, for accessions, tab-delimited formats; customizing the interface; managing a broad range of user types; and </li></ul></ul><ul><ul><li>implementation as a stand-alone or networked application. </li></ul></ul>8/30/2007 AT for SAA Annual Meeting
    6. 6. Beta Testing <ul><li>Application thoroughly tested by AT specification team from April to July 2006 </li></ul><ul><li>Programmatically tested by 60 testers at 21 institutions over 14 week period in fall of 2006 </li></ul><ul><li>Institutions included: Arizona State, Bundesarchiv, Georgia Tech, Getty Research Institute, Harvard, Nationaal Archief, NYU, Princeton, Michigan, UCSD, U Mass, U Texas (complete list and report at: http://archiviststoolkit.org/AT1Testing/betaTest/index.html) </li></ul>8/30/2007 AT for SAA Annual Meeting
    7. 7. 1.0 Release & Uptake <ul><li>Version 1.0 of the AT was released on December 17, 2006 </li></ul><ul><li>1,130 unique downloads in 72 countries and territories as of July 25 </li></ul><ul><ul><li>United States 752 </li></ul></ul><ul><ul><li>Spain 48 </li></ul></ul><ul><ul><li>Canada 43 </li></ul></ul><ul><ul><li>United Kingdom 34 </li></ul></ul><ul><ul><li>France 15 </li></ul></ul><ul><ul><li>Italy 15 </li></ul></ul><ul><ul><li>Brazil 14 </li></ul></ul><ul><ul><li>Portugal 13 </li></ul></ul><ul><ul><li>Mexico 12 </li></ul></ul><ul><ul><li>Germany 9 </li></ul></ul><ul><ul><li>Australia 8 </li></ul></ul><ul><li>No attempt made to count downloads of AT 1.1 beta </li></ul>8/30/2007 AT for SAA Annual Meeting
    8. 8. Implementation <ul><li>36 respondents to a survey conducted Feb. 19-March 9, 2007 among ATUG-l members </li></ul><ul><li>60% installed AT as a network app, while 48% installed as a stand alone </li></ul><ul><li>80% installed the AT as a test app, while 35% installed as production app </li></ul><ul><li>32 respondents reported using MySQL as a backend, while one brave soul reported using MS SQLServer </li></ul><ul><li>94 % installed the client on a Windows machine, 14% on a Linux machine, and 11% on a MAC machine </li></ul><ul><li>For network installations, 60% installed on a Windows server, 30% on a Linux server, 5% on a MAC server, a small percentage on other servers. </li></ul>8/30/2007 AT for SAA Annual Meeting
    9. 9. Support Services <ul><li>ATUG-l (Archivists’ Toolkit User Group) </li></ul><ul><ul><li>Nearly 500 members at mid-August </li></ul></ul><ul><ul><li>Subscribe: http://mailman.ucsd.edu/mailman/listinfo/atug-l </li></ul></ul><ul><ul><li>Archives: http://mailman.ucsd.edu/pipermail/atug-l/ </li></ul></ul><ul><li>Software Issues / Bug Management </li></ul><ul><ul><li>Over 1000 bugs, feature requests, documentation issues reported by mid-August </li></ul></ul><ul><ul><li>Internal Reporting Device </li></ul></ul><ul><ul><li>Issue list: https://jira.nyu.edu:8443/jira/secure/Dashboard.jspa </li></ul></ul><ul><li>Both ATUG-l messages and issue reports contributed to design revision </li></ul>8/30/2007 AT for SAA Annual Meeting
    10. 10. Phase 2 <ul><li>Began February 1, 2007 </li></ul><ul><li>Objectives </li></ul><ul><ul><li>Refine performance of version 1.0 by identifying and removing bugs, enriching records and functionality, and supporting batch import and export processes </li></ul></ul><ul><ul><li>Introduce new functionality to support user registration / use tracking, rights management, appraisal, and interoperability of the AT with digital repository systems </li></ul></ul><ul><ul><li>Develop business plan with consultant for nurturing and sustaining the application beyond the phase 2 grant period </li></ul></ul><ul><li>Staffing </li></ul>8/30/2007 AT for SAA Annual Meeting
    11. 11. 1.1 Release & Features <ul><li>Enhanced Records </li></ul><ul><ul><li>Accession </li></ul></ul><ul><ul><li>Repository </li></ul></ul><ul><li>New Processes </li></ul><ul><ul><li>Import of XML encoded accession data </li></ul></ul><ul><ul><li>Batch import for EADs </li></ul></ul><ul><ul><li>Batch export for EADS and MARCXML </li></ul></ul><ul><ul><li>EAD import / export based on EAD schema </li></ul></ul><ul><li>Support for MS SQLServer and Oracle backends </li></ul><ul><li>Bug fixes </li></ul>8/30/2007 AT for SAA Annual Meeting
    12. 12. AT Project: www.archiviststoolkit.org Staff Email address: [email_address] AT Sandboxes: http:// www.archiviststoolkit.org/sandbox.html http:// archiviststoolkit.org/publicBeta/index.html Archivists’ Toolkit User Group: Subscription: http://mailman.ucsd.edu/mailman/listinfo/atug-l Archives: http://mailman.ucsd.edu/pipermail/atug-l /
    13. 13. Society of American Archivists Annual Meeting, August 30, 2007 Jody Lloyd Thompson Implementing the AT: Working with Staff, Students, and IT
    14. 14. Overview <ul><li>Brief look at AT </li></ul><ul><li>Working with staff and student assistants </li></ul><ul><li>Working with IT </li></ul>
    15. 15. Brief look at AT <ul><li>Accessions module </li></ul><ul><li>Resource module </li></ul><ul><li>Other features </li></ul>
    16. 16. Working with staff & student assistants <ul><li>Manage staff & student access </li></ul><ul><li>Create user manuals for staff and students </li></ul><ul><li>Improve training for staff & students </li></ul>
    17. 17. Manage staff & student access <ul><li>Access classes: </li></ul><ul><ul><li>Superuser (5) </li></ul></ul><ul><ul><li>Application manager (4) </li></ul></ul><ul><ul><li>Project manager (3) </li></ul></ul><ul><ul><li>Advanced data entry staff (2) </li></ul></ul><ul><ul><li>Beginning data entry staff (1) </li></ul></ul><ul><ul><li>Reference staff (0) </li></ul></ul>
    18. 20. Working with staff & student assistants <ul><li>Manage staff & student access </li></ul><ul><li>Create user manuals for staff and students </li></ul><ul><li>Improve training for staff & students </li></ul>
    19. 27. Impact on staff <ul><li>Improved functions in the Archives </li></ul><ul><ul><li>Reference services </li></ul></ul><ul><ul><li>Donor tracking </li></ul></ul><ul><ul><li>Workflow </li></ul></ul>
    20. 31. Impact on staff <ul><li>Improved functions in the Archives: </li></ul><ul><ul><li>Reference services </li></ul></ul><ul><ul><li>Donor tracking </li></ul></ul><ul><ul><li>Workflow </li></ul></ul>
    21. 35. Impact on staff <ul><li>Improved functions in the Archives: </li></ul><ul><ul><li>Reference services </li></ul></ul><ul><ul><li>Donor tracking </li></ul></ul><ul><ul><li>Workflow </li></ul></ul>
    22. 36. Working with IT <ul><li>Establish good communication with IT </li></ul><ul><ul><li>Create a Wiki </li></ul></ul><ul><li>Create production and test instances </li></ul>
    23. 38. Working with IT <ul><li>Establish good communication with IT </li></ul><ul><ul><li>Create a Wiki </li></ul></ul><ul><li>Create production and test instances </li></ul>
    24. 39. Working with IT <ul><li>Install AT </li></ul><ul><li>Import legacy accession records </li></ul><ul><ul><li>Completed at Georgia Tech </li></ul></ul><ul><li>Import/export EAD-encoded finding aids </li></ul><ul><ul><li>On-hold at Georgia Tech until data import function has been refined. </li></ul></ul>
    25. 40. Thank you <ul><li>Jody Lloyd Thompson </li></ul><ul><li>Georgia Institute of Technology </li></ul><ul><li>[email_address] </li></ul><ul><li>404-894-9626 </li></ul>
    26. 41. Big Scale, Little Scale: Consortium vs Multiple Implementations of the AT at Harvard Kate Bowers Harvard University Archives SAA Conference, August 2007 Copyright 2007
    27. 42. Big Scale, Little Scale: Consortium vs Multiple Implementations of the AT at Harvard al Kate Bowers Harvard University Archives SAA Conference, August 2007
    28. 43. Scalability <ul><li>Part-timers / 1 collection </li></ul><ul><li>25+ FTE / thousands </li></ul><ul><li>100,000+ feet overall? </li></ul>
    29. 44. AT Working Group <ul><li>with library IT, to test installation and scalability of AT </li></ul><ul><li>further investigate AT functionality and develop recommendations for Harvard-specific development </li></ul><ul><li>recommend administrative rights (security) and functionality to be centrally controlled </li></ul>
    30. 45. AT Working Group <ul><li>investigate issues of importing legacy data (collection management as well as descriptive data) </li></ul><ul><li>investigate the diversity of workflows, processes, and procedures in Harvard archival repositories and determine how well the AT accommodates them </li></ul>
    31. 46. Using the latest information technology... [Grace Hopper working on the development of the MARC I computer, 8/4/1944] (UAV 605.270.1.2p (U-822))
    32. 47. AT Working Group <ul><li>with library IT, to test installation and scalability of AT </li></ul><ul><ul><li>Oracle installation up and running </li></ul></ul><ul><ul><li>12 repositories / 25-ish total at Harvard </li></ul></ul><ul><ul><li>75 user accounts, about 40 people </li></ul></ul><ul><ul><li>Want to ingest about 75-100K MARC records and 2000+ EAD finding aids </li></ul></ul>
    33. 48. Working closely with colleagues... “ Some new data on the weight of a crowd of people” (HUK 363p (Fig. 8)) Original photo, used as illustration in the Harvard Engineering Journal (vol. 4, 1905-1906).
    34. 49. AT Working Group <ul><li>further investigate AT functionality and develop recommendations for Harvard-specific development </li></ul><ul><ul><li>Interface with Harvard library catalogs (ILS, archival inventories, images) </li></ul></ul><ul><ul><li>Add functionality for ease-of-use (to be fully identified in wide-scale testing) </li></ul></ul>
    35. 50. Central / distributed administration and security levels ... Plan showing Position of Reading Room [central portion of blueprint, ca. 1895] (UAIII 50.28.95.5 (1)) Plan for library addition that was never built.
    36. 51. AT Working Group <ul><li>recommend administrative rights (security) and functionality to be centrally controlled </li></ul><ul><ul><li>Central AT administration will be level 5 </li></ul></ul><ul><ul><li>Each repository will have a level 4 liaison </li></ul></ul><ul><ul><li>Below that, details to be worked out in wide-scale end-user testing </li></ul></ul><ul><ul><li>Are the remaining 4 levels enough? </li></ul></ul>
    37. 52. Pull in legacy data... [Tug of War Team, photograph, 1888] (HUPSF Tug o' War (6)) The ’88 worn by all of them probably means that they are a class team.
    38. 53. AT Working Group <ul><li>investigate issues of ingesting legacy data (collection management as well as descriptive data) </li></ul><ul><ul><li>Have not successfully sent a finding aid on a round-trip from, and back to, our local system </li></ul></ul><ul><ul><li>We know we will want central support for ingest of accession data </li></ul></ul>
    39. 54. Investigate the diversity of workflows ... Harvard College Library Department of Classification and Cataloging [flow chart, May 1936] (UAIII 50.20.36.15) 1936 backlog: 160,000 monographs
    40. 55. AT Working Group <ul><li>investigate the diversity of workflows, processes, & procedures in Harvard archival repositories and determine how well the AT accommodates them </li></ul><ul><ul><li>Needs wide-scale end-user testing </li></ul></ul><ul><ul><li>Working Group members have already identified some issues in their own repositories </li></ul></ul>
    41. 56. AT Working Group <ul><li>Report the cost of central support </li></ul><ul><li>Identify the benefits, particularly cost savings </li></ul>
    42. 57. Division of labor (not final!) <ul><li>Consortium Responsibilities : Central </li></ul><ul><li>Create and manage the database (.25 FTE “IT” guy) </li></ul><ul><li>Create central &quot;Super user&quot; with highest security level </li></ul><ul><li>Create “stub” records for repositories </li></ul>
    43. 58. Division of labor (not final!) <ul><li>Consortium Responsibilities : Central </li></ul><ul><li>Identify and train liaison for each repository </li></ul><ul><li>Create user accounts for these liaisons: second-highest security level </li></ul><ul><li>Create a “pseudo user” for each repository, thus central administration can act as if it were a staffer in the repository </li></ul>
    44. 59. Division of labor (not final!) <ul><li>Consortium Responsibilities : Central </li></ul><ul><li>At Harvard, but maybe not everywhere: </li></ul><ul><li>Batch import EAD instances </li></ul><ul><li>Batch import MARC records </li></ul>
    45. 60. Division of labor (not final!) <ul><li>Consortium Responsibilities: Distributed </li></ul><ul><li>Liaison in repository creates all other users with security levels 0-3 </li></ul><ul><li>Any configuring that is possible for repositories, rather than centrally </li></ul>
    46. 61. Division of labor (not final!) <ul><li>Dual responsibilities </li></ul><ul><li>(needs central support, but will also requires input from repository personnel) </li></ul><ul><li>Ingest/mapping of legacy accession data </li></ul><ul><li>Ingest/mapping of holdings data (boxes & locations) </li></ul><ul><li>Ingest/mapping of patron data </li></ul><ul><li>Configuring the application centrally (consensus) </li></ul><ul><li>Centralized training end-users? </li></ul>
    47. 62. Conclusions? <ul><li>Wide-scale end-user testing September-October 2007 </li></ul><ul><li>Mid-term project report late September </li></ul><ul><li>Final report to senior administration November-ish </li></ul>
    48. 63. The end <ul><li>http:// isites.harvard.edu/icb/icb.do?keyword =k15469 </li></ul><ul><ul><ul><li>Bugs </li></ul></ul></ul><ul><ul><ul><li>Wish lists </li></ul></ul></ul><ul><ul><ul><li>Conclusions </li></ul></ul></ul><ul><ul><ul><li>Continuing questions </li></ul></ul></ul>
    49. 64. Can you get AT without IT? Implementing the Toolkit at a small college repository Katherine Stefko Edmund S. Muskie Archives and Special Collections Library Bates College
    50. 65. Archives Overview <ul><li>3 FTE </li></ul><ul><li>100+ mss. collections, 1,500 l.f. of College records, 14,000 rare books </li></ul><ul><li>Papers of Edmund S. Muskie, ca. 3000 l.f. </li></ul><ul><li>Est. 2000 with merger of two departments </li></ul><ul><li>No dedicated IT staff or support </li></ul>
    51. 66. Technical Underbelly <ul><li>Installed v. 1 and 1.1 (beta) as networked app for testing and implementation </li></ul><ul><li>MYSQL backend on a Windows server </li></ul><ul><li>Moving to Linux backend to support secure connection </li></ul>
    52. 67. Accessions Module <ul><li>Fully implemented </li></ul><ul><li>Tracking new accessions </li></ul><ul><li>Adding legacy paper accession records as time permits </li></ul><ul><li>Imported all electronic legacy accession data </li></ul>
    53. 69. Importing Legacy Accessions <ul><li>Tab delimited text (or XML) </li></ul><ul><li>Low barrier ingest process </li></ul><ul><li>Import can be slowed by: </li></ul><ul><ul><li>Incomplete legacy data </li></ul></ul><ul><ul><li>Out-of-date documentation </li></ul></ul>
    54. 70. Description Module <ul><li>Implementation on hold </li></ul><ul><li>Tested adding new records </li></ul><ul><li>Consolidated legacy data and started data clean up </li></ul><ul><li>Developed and tested migration strategy </li></ul><ul><li>Wrote script to extract EAD </li></ul>
    55. 71. Decision Factors <ul><li>Legacy data and AT divergences </li></ul><ul><li>Bugs </li></ul><ul><li>Application limitations </li></ul><ul><ul><li>Multiple user access to collections </li></ul></ul><ul><ul><li>No global search and replace </li></ul></ul>
    56. 72. IT Needs <ul><li>Installation and upgrades of application </li></ul><ul><li>Clean up of legacy descriptive data </li></ul><ul><li>Extracting EAD from current database </li></ul><ul><li>Formulating and testing descriptive data migration strategy </li></ul><ul><li>Potential customizations? </li></ul><ul><li>Developing style sheets and XML database for online delivering our EAD finding aids </li></ul>
    57. 73. It’s not just a database… It’s a work style <ul><li>Encourages/enforces compliance to professional standards and best practices </li></ul><ul><li>Changes to policies and procedures </li></ul><ul><li>Workflow--more time on input, less on reporting and retrieval </li></ul><ul><li>Flexibility vs. functionality </li></ul>
    58. 74. It’s not just a project, It’s a process.. <ul><li>Active user community that is contributing to the application’s development </li></ul><ul><li>Major improvements between v. 1 and v. 1.1 </li></ul>
    59. 76. Get Involved <ul><li>Join the community </li></ul><ul><li>Contribute feedback and helper apps </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×