We’ve been busy at Northern Lights over the past year in some new areas that I think you might find interesting and perhaps relevant to your library’s strategies and/or operations. With this posting, I’m focusing on a project that involved a research library archives department whose staff members were charged with creating a Digital Archives for enterprise-wide born-digital administrative content management.
Please feel free to contact me if you wish to receive any of the NLI documents described later in this posting.
Our responsibilities focused primarily on assisting Archives staff members in getting up to speed on the emerging XML family of services, SOA, Web Services, the difference between XML and XML native capabilities, taxonomies, thesauri, Ontologies and so forth.
Our Northern Lights activities and contributions included:
1. A one-day workshop related to “Current Trends in IT and what they mean to Information Managers”.
This included not only Archives staff members, but the Archives Director also invited the metadata librarian, campus ITS staff members, and the IT staff member from the College of Arts and Sciences. Shared discussion among the attendees set the stage for what was currently possible, when new relevant ITS implementations might occur, the interrelationship of the Library’s Repository and the Administrative Digital Content Management System as well as how the attendees might be working together in the future.
2. A series of Content Management Documents that Archives staff members used as beginning points for discussing and understanding together the emerging Content Management capabilities. The document series included:
a. Content Methods -- a detailed overview of the logical segments of CMS and available types of systems designed to manage content (structured information) in distributed, digital environments.
b. CM Types – an overview of various types of CMS, the difference in designs, specific differences in component-based, composition-based and schema-based types and how the latter relates to analyzing a body of content.
c. CM Type Detail – a detailed exploration of the three main types of CMS, including details of their design as well as how and when to implement them.
d. CM Access Structures – a detailed overview of access structures and the organizing tools used to work with a body of content. These value-added structures support the basic CMS functionality, enable the rapid, precise discovery of relevant content facilitate contributions, enable repurposing and reuse and, in general, allow the content to be managed to maximize investments.
e. CM Repository – an overview of the heart of the CMS, the repository, the place where content is stored and managed, The document looks at the repository, its characteristics, its components, its critical role in storing the structures that make up the explicit content model and the various storage options available.
f. CMS Relational Databases versus OO-XMLDG – an overview, comparison and contrast of the repository component of the Management Module of CMS, specifically the different approaches to data handling found in relational databases and XML/OO databases when the latter act as repositories for content management systems.
g. Readiness – a detailed overview of skills and knowledge the staff members need to create a new version of archives in a digital age, to change the way they work, to transfer their skills into components of systems and to help users organize and structure their own information in a way that enables the users to manage their own content, enables Archives staff members to fulfill their mission in a new, active way and that enables the enterprise to leverage every dollar it spends on the application of information management skills. In essence, the document is about how to prepare for changing the way that staff members and users work.
3. Readings – we also provided a list of other relevant sources designed to provide a further context for current discussions of Content Management Systems relevant to the emerging XML native environment.
4. Wiki – we made two site visits to get the process going and then provided a Wiki for Archives staff members to share and discuss what they were learning as well as resolving problems they discovered during the project. We also participated in the Wiki discussions in responding to questions, guiding discussions, suggesting approaches and so forth. This proved not only to be cost effective, but also to provide a rich learning and application-testing environment.
5. Testing Applications – Archives staff members also undertook testing of Open Source content management systems like Greenstone to gain hand-on experience in the use of relevant Open Source software in terms of the further design and development of the “Digital Archives” enterprise-wide administrative content model.
As our NLI participation in the Project ended, Archives staff members began the design the next phase of their work – i.e., participation with the College of Arts and Sciences to respond to the CAS Dean’s desire to create a new way for College members to work together – named at that time the “Paperless Office” – in a born digital working environment.
Recent Comments