must move towards a model with comprehensive mobile access to online services
101More
Mobile Strategy | National Library of Australia - 0 views
- ...98 more annotations...
-
the Library may look to harness the potential of these technologies to break away from the traditional broadcast-only website presence and move towards two-way conversations between the Library and its users, or conversations between the users themselves
-
the key objectives stated in the Information Technology Strategic Plan 2012-2015 include Online Presence and supporting “the needs of our users for easy discovery of, access to, and engagement with our services, collections and other information resources in the digital environment”
-
Putting Library resources into the hands of users in their lounge rooms reflects a deeper understanding of the need to move beyond the desire to follow our users and instead reach out to them to “take them some place new
-
building both infrastructure and a culture of engagement will pave the way to more efficiently and effectively meeting that need in the future
-
Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
-
Equip staff to champion and drive the development of mobile services to improve access and productivity.
-
Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
-
Adopt standards and best practices for interoperable mobile content and cross-platform data management.
-
Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
-
Information Technology Division to examine ongoing resourcing of development work, administrative models, and potential for partial cost-recovery
-
Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes. Identify
-
Collections Management Division to keep a watching brief on any developments pertaining to the extension of Legal Deposit to include digital (and mobile) content
-
developing a statement of collecting intentions for the various categories of ebook titles within the context of revising the collecting policy for Australian electronic publications in general
-
Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
-
Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
-
Equip staff to champion and drive the development of mobile services to improve access and productivity.
-
Equip staff to champion and drive the development of mobile services to improve access and productivity.
-
Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
-
Equip staff to champion and drive the development of mobile services to improve access and productivity.
-
Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
-
Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
-
Adopt standards and best practices for interoperable mobile content and cross-platform data management.
-
Adopt standards and best practices for interoperable mobile content and cross-platform data management.
-
Adopt standards and best practices for interoperable mobile content and cross-platform data management.
-
Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
-
Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
-
Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes
-
Investigate infrastructure and resourcing requirements for digital recording and distribution to ensure the long-term sustainability of online broadcast activity
-
Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
-
Collections Management Division to keep a watching brief on any developments pertaining to the extension of Legal Deposit to include digital (and mobile) conten
-
developing a statement of collecting intentions for the various categories of ebook titles within the context of revising the collecting policy for Australian electronic publications
-
Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes
18More
The Code4Lib Journal - How Hard Can It Be? : Developing in Open Source - 0 views
-
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.
-
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.
-
ensure the software writers did not miss any key points in their fundamental understanding of the way libraries work.
-
The programming we commissioned cost us about 40% of the purchase price of an average turn-key solution.
-
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.
-
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
Home - Introduction to LibGuides CMS (formerly CampusGuides) - Springshare Help at Spri... - 0 views
21More
shared by Joanne S on 10 Sep 12
-
Cached
The Strongest Link: Libraries and Linked Data - 0 views
www.dlib.org/...11byrne.html
IMT122 Reading List Supplementary Reading Week 03 Linked Data Topic 03 IMT122
![](/images/link.gif)
![](/images/uploaded-cache.png)
-
By marking up information in standardized, highly structured formats like Resource Description Framework (RDF), we can allow computers to better "understand" the meaning of content
- ...17 more annotations...
-
For most librarians this concept is fairly easy to understand. We have been creating highly structured machine-readable metadata for many years
-
By linking our data to shared ontologies that describe the properties and relationships of objects, we begin to allow computers not just to "understand" content, but also to derive new knowledge by "reasoning" about that content.
-
the term "Semantic Web" to refer to a full suite of W3C standards including RDF, SPARQL query language, and OWL web ontology language.
-
This article will outline some of the benefits that linked data could have for libraries, will discuss some of the non-technical obstacles that we face in moving forward, and will finally offer suggestions for practical ways in which libraries can participate in the development of the semantic web.
-
Having a common format for all data would be a huge boon for interoperability and the integration of all kinds of systems.
-
The linking hub would expose a network of tightly linked information from publishers, aggregators, book and journal vendors, subject authorities, name authorities, and other libraries.
-
semantic search could take us far beyond the current string-matching capabilities of search engines like Google.
-
Until there is enough linking between collections and imaginative uses of data collections there is a danger librarians will see linked data as simply another metadata standard, rather than the powerful discovery tool it will underpin.
-
Rights management poses potential problems for linked data in libraries. Libraries no longer own much of the content they provide to users; rather it is subscribed to from a variety of vendors.
-
Byrne, G., & Goddard, L. (2010). The Strongest Link: Libraries and Linked Data. D-Lib Magazine, 16(11/12). doi:10.1045/november2010-byrne Retrieved from http://www.dlib.org/dlib/november10/byrne/11byrne.html