Skip to main content

Home/ BA (LCIM)/ Group items tagged activities

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Joanne S

Guideline 15 - Developing and implementing a keyword thesaurus - State Records NSW - 0 views

www.records.nsw.gov.au/...guideline-15

guideline developing keyword thesaurus state nsw records records management

shared by Joanne S on 10 May 13 - Cached
  • Thesaurus: a controlled list of terms linked together by hierarchical, associative or equivalence relationships. (AS ISO 15489.2, 4.2.3.2).
  • Keyword thesaurus: a records management thesaurus based on functions and following the principles of keyword classification.
  • develop, implement, maintain and review a keyword thesaurus for use in records management.
  • ...5 more annotations...
  • Keyword classification: involves grouping records into broad, functionally based areas represented by keywords. Records are further classified by the use of activity descriptors and optional subject descriptors.
  • Classification: systematic identification and arrangement of business activities and/or records into categories according to logically structured conventions, methods, and procedural rules represented in a classification system. (AS ISO 15489.1, 3.5).
  • A thesaurus is a tool that supports the classification and management of records, usually at the file level. It ensures that classification terms are used consistently throughout a recordkeeping system. It is a 'controlled language' tool.
  • A thesaurus may have: multiple entry points to guide users to preferred terms and correct titles cross-referencing scope notes and tips strict control of language, and alphabetical or hierarchical presentation.
  • Functional classification establishes and documents the relationships between records and the business activities they document which is essential in understanding records, and in particular understanding over time.
Joanne S

CAARA - Council of Australasian Archives and Records Authorities - 0 views

www.caara.org.au/?s=Policy+Statement+15#principle15

LIM215 Module 2.1 Introduction to Archival Principles activities

shared by Joanne S on 23 Mar 14 - No Cached
  • Joanne S on 23 Mar 14
     
    Activities (not for assessment) * What is distributed custody? A good place to start is with CAARA's (Council of Australasian Archives and Records Authorities) Policy Statement 15: Models for the distributed custody and management of government archival records. Adopted March 2006. http://www.caara.org.au/?s=Policy+Statement+15#principle15
Joanne S

Hildenbrand, S. (2000). Library feminism and library women's history: Activism and scho... - 0 views

sentra.ischool.utexas.edu/...LandC_35_1_Hildenbrand.pdf

LIS100 Topic 4: Library History Supplementary Reading library Gender equality Curtin Login Required

shared by Joanne S on 19 Mar 14 - No Cached
  • Joanne S on 19 Mar 14
     
    Hildenbrand, S. (2000). Library feminism and library women's history: Activism and scholarship, equity and culture. Libraries & culture, 35(1), 51-65. Retrieved fromhttp://sentra.ischool.utexas.edu/~lcr/archive/fulltext/LandC_35_1_Hildenbrand.pdf
Joanne S

Guideline 16 - Accountable outsourcing: Recordkeeping considerations of outsourcing NSW... - 0 views

www.records.nsw.gov.au/...guideline-16

LIM135 Week 01 Week 1 - Information governance and accountability state records

shared by Joanne S on 25 Aug 13 - No Cached
  • Joanne S on 25 Aug 13
     
    In light of the lecture on Accountability the following quote in the Guideline is important... "Public offices are accountable Outsourcing a business activity does not diminish a public office's responsibility to ensure that it is carried out properly and that all requirements for records are met".
Joanne S

The Code4Lib Journal - How Hard Can It Be? : Developing in Open Source - 0 views

journal.code4lib.org/...1638

IMT122 Essential Reading Week 06 Task 06 Koha

shared by Joanne S on 22 Nov 12 - Cached
  • We experienced freedom to explore alternate avenues, to innovate, to take risks in ways that would have been difficult under the direct control of a district council.
  • patrons made it clear that while they appreciated that computers were a necessary part of a modern library, they did not consider them the most important part.
  • Our overall objective was to source a library system which: could be installed before Y2K complications immobilised us, was economical, in terms of both initial purchase and future license and maintenance support fees, ran effectively and fast by dial-up modem on an ordinary telephone line, used up-to-the minute technologies, looked good, and was easy for both staff and public to use, took advantage of new technology to permit members to access our catalogue and their own records from home, and let us link easily to other sources of information – other databases and the Internet. If we could achieve all of these objectives, we’d be well on the way to an excellent service.
  • ...14 more annotations...
  • "How hard can it be" Katipo staff wondered, "to write a library system that uses Internet technology?" Well, not very, as it turned out.
  • Koha would thus be available to anyone who wanted to try it and had the technical expertise to implement it.
  • ensure the software writers did not miss any key points in their fundamental understanding of the way libraries work.
  • fairly confident that we already had a high level of IT competence right through the staff, a high level of understanding of what our current system did and did not do.
  • The programming we commissioned cost us about 40% of the purchase price of an average turn-key solution.
  • no requirement to purchase a maintenance contract, and no annual licence fees.
  • An open source project is never finished.
  • Open source projects only survive if a community builds up around the product to ensure its continual improvement. Koha is stronger than ever now, supported by active developers (programmers) and users (librarians)
  • There are a range of support options available for Koha, both free and paid, and this has contributed to the overall strength of the Koha project.
  • Vendors like Anant, Biblibre, ByWater, Calyx, Catalyst, inLibro, IndServe, Katipo, KohaAloha, LibLime, LibSoul, NCHC, OSSLabs, PakLAG, PTFS, Sabinet, Strategic Data, Tamil and Turo Technology take the code and sell support around the product, develop add-ons and enhancements for their clients and then contribute these back to the project under the terms of the GPL license.
  • FRBR [5] arrangement, although of course it wasn’t called that 10 years ago, it was just a logical way for us to arrange the catalogue. A single bibliographic record essentially described the intellectual content, then a bunch of group records were attached, each one representing a specific imprint or publication.
  • The release of Koha 3.0 in late 2008 brought Koha completely into the web 2.0 age and all that entails. We are reconciled to taking a small step back for now, but the FRBR logic is around and RDA should see us back where want to be in a year or so – but with all the very exciting features and opportunities that Koha 3 has now.
  • In the early days, the Koha list appeared to have been dominated by programmers but I have noticed a lot more librarians participating now
  • "Adopt technology that keeps data open and free, abandon[ing] technology that does not." The time is right for OSS.
  • Joanne S on 22 Nov 12
     
    For more information about Koha and how it was developed, see: Ransom, J., Cormack, C., & Blake, R. (2009). How Hard Can It Be? : Developing in Open Source. Code4Lib Journal, (7). Retrieved from http://journal.code4lib.org/articles/1638
1 - 5 of 5
Showing 20▼ items per page