OLE Project Regional Workshop, Utah - Blue Sky brainstorming discussion

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    OLE Project Regional Workshop, Utah - Blue Sky brainstorming discussion - Presentation Transcript

    1. “Blue Sky” Brainstorming Results – Utah Workshop OLE would allow us to create and curate new digital content. Built in digital content management tools like OCR full text, zoom of images, etc. In other words, incorporate Content DM and IR stuff When entering an order – automatically checks for existing holding and alerts ACQ staff. Serial holding services that drive open URL links, etc. Would talk directly to the system (SFX style) but be maintained remotely – real time updates. Order/receipt of new edition automatically generates not to consider withdrawal of older edition Ability for faculty and other authorized people to contribute content like their articles, etc. (IR-like items) So OLE would contain all materials (IR, print, dig library etc) Robust help system with contextual aid at all levels Processing materials: alerts for where material is and the next step in the process. Tag records with who worked on them. Ability to access LC/NACO authority file directly rather than need to have local authority records No hardcoding of features but instead can be turned on or off Failed title searches go to a report for consideration for library purchase All special collections resources would be indexed with enough “granularity” to lead researches directly to needed materials (both reducing research time and unnecessary handling of primary resources) Anytime a patron requests an item from ILL automatically checks for price and auto rush orders item if under a certain price Have one central database for bibs and have the whole world work in that environment (network level service) OLE should work seamlessly with endnote, zotero etc. OLE will allow quality federated searching Simple reports- user driven Fast search results i.e. robust searching with fast searching time Able to utilize all the great data in MARC records that current ILS’s ignore System would send alerts to patrons on new material added New journal issues (print, e-journals) o New acquisition in variety of formats o By sub, author, what else?? o Incorporate the best of FRBR principles. Implement FRBR concepts to improve display and access. Utilize a FRBR hierarchical model to allow content identification separate from format (video, cd, book, etc) and link purchasing at the format/edition level OLE Project BPM Workshop – Utah – January 14-15, 2009 Page 1
    2. Incorporate all print/e-holdings in one easy to read format Require few “clicks” to view search results OLE should display results in an easy to read format OLE records should be easy to read Authority records should be simplified and demystified – no cataloger-arcane codes and language. Mouse over 510 tag would show explanation of what was in that tag. Would have the template into which you could type in a name of source used to verify form of name so don’t need to attend NACO training to create or understand. Maybe have a catalog record templates so more staff could contribute catalog records without having to know AACR2/RDA+LCSH rules by heart. Have context sensitive and immediate help and/or links to rules or examples. Accept multiple authentication methods ILS integrated with ILL systemAuomated generation of formatted bibliography for a given list of books of articles (APA, MLA, etc)(citations) The new OLE should link out to all free scholarly resources available on the web. Linking should be seamless, not embedded. System crawls and automatically adds bib records for peer reviewed open access journals and books. Store, search, index and display vernacular data. Unicode. It should be easy to upgrade individual parts of the ILS when needed. Should not have to wait for major system upgrade if only a single or a few areas need upgrade. Assure that new version implementation do not negate working processes. (same for migrations to different systems) Split budget allocation on an invoice by amount not percentage Links to security – doors, gates, etc.. RFID checks out as person leaves through any door Have a process for e-books. From acquisitions to cataloging and maintenance. Take into account vendor deletions Open website for book vendors (or publishers), put chosen items in “cart”, create the order with purchase card information, linked to (purchase instrument order) that tracks the item. Have the system automatically “ping”/test for access to e-content that we own – negate the need for us to manually check and eliminates patron frustration when content is down Provide deeply integrated e-resource management including acq. Info – renewal price, date of expire, vendor or consortial source, with key use stats, DRM and package contents Allow users to post reviews of books and extract reviews from students at other libraries across the world Automatic spell check of all ACQ and CAT records Ability to import usage stats and run cost-per-use type analysis (better – system talks to e-resource admin modules to automatically pull reports) OLE Project BPM Workshop – Utah – January 14-15, 2009 Page 2
    3. Allow patrons to add content/metadata to records (tagging, reviews, links between materials) Incorporation of more search criteria – relevance ranking, fuzzy search- but still have precision search. Browsing available tool. OLE should “point” patrons to additional relevant resources. “If you like this…you might like this…” Digital collections/IR content incorporated in ILS Instantaneous indexing. 24/7 availability – no downtime for indexing Maintain circulation history of patrons for special collections materials Developed for high functionality on mobile devices, a mobile version of OPAC Ability to create or supply persistent URLs for digital objects (articles, text, images) that are contained in or described in OLE Not dependent on operating system Ability for patrons to link to or pull out records from out system to create their own content (like deli.cio.us collections of weblinks) Interact with patrons using social networking. Mash-ups. If patrons can’t find item at our library they can easily see who might have it at another state library. Automate ILS requests – no new login or form to fill out. “Cited by” option for any bib entry Flexible and easy for staff to get stats, reports or create ad hoc reports Streamline selection, acquisition and access to electronic books A simplified way for students to search across all our systems easily. A meta-search (catalog, article databases, etc) that is easy to customize, and turn on and off depending on patron needs. A single search/discovery interface for all library resources with simple starting point and options for more sophisticated searching Improve ability to make batch changes to data in ILS (e.g. bib record, item records, vendor records) Editing and translating abilities within ILS (or connected via SOA) currently available in MARC edit. Robust architecture able to handle large files (importing, deleting) quickly without problem. “MyLibrary” customization would suggest resources, reserves, databases, subj pathfinder, based on major, class registrations, personal customiztion. User can create profiles and customize list of databases to be searched. System would generate and populate e-journal and database lists (from MARC record?) bu subject, publisher, alphabetically Provide enhaced authority records (for special collection materials)(managed outside of local ILS system). Incorporate authority work in all searches. (keyword too) Incorporate Web 2.0 ( annotations, RSS, rankings etc) and developing Web 3.0 technologies (include semantically accessible data in authority record – coordinates etc.) Get beyond inventory control to access, creation, modification User interface should be pretty, fun and easy to use. A Netflix like interface for patrons to organize and save booklists, requests, etc. OLE Project BPM Workshop – Utah – January 14-15, 2009 Page 3
    4. Use open source software which vendors (materials supplier) can use and interface EDI tools for Acq, stats and other library functionality A serials record that patrons (and non-cataloging librarians) can understand…and that brings all instances of serial into one display Share vendor information (ILS vs. campus accounts payables) – linked to contact information so that changes are timely and global A discovery tool that helps users make connections between library content without overwhelming them with too much information The ability to create “instructional” collections from all kinds of library resources and integrate them into a wide range of end user systems (CMS, wikis, etc) Remotely accessible through web interface/client-server (web-client) utilizing LDAP authentication (client-server app. needs to be cross-platform – including Linux) Hold any item-specific holdings information (manifestation/expression/work records managed externally) Manage item information separately from manifestation (conservation, acquisition, restrictions, provenance, etc) Move e-reserves to CMS platform. Leave the service (i.e. scanning, copyright) to the library but work in CMS. Print reserves can just be treated as normal catalog items with their own types and locations. Automatic generation of accession numbers and call numbers for manuscript material. Provide additional data fields so that manuscript and archival material can be accessioned in the ILS. Manage processes with task assignments, notifications, and reporting/statistics. System notifies task owners when new tasks need to be completed. Customizable workflows (ability to adapt the way processes run through the ILS) Accommodate finding aids that are not MARC based and not just special collection material. ILS shouldn’t just be MARC based. Easy interoperability between MARC record information and metadata. (for example, print MARC information could be easily exported and applied as metadata to a duplicate item in a digital collection – as with a thesis, for example) Ability to cross walk between data formats such as MARC, XML, EAD. Ability to bring in wide range of formats into catalog without forcing metadata into single format/standard Use MyLibrary sign on (or MyCampus) logon to authorize all levels of access – checkout, e-journal, ILL, course reserves etc) Athentication should only take place once – both for the front end and the back end. Customizable interface for individuals to display the function they use most (reserves, e-journals, databases). Alerting feature so searches are prompted when the library adds sources, regardless of format, in subjects of interest or according to personal profile. Adding information to records is easy, e.g., notes about content, readers’ opinions and recommendations, mini reviews, tagging? Remove barriers between our users and our resources. Single authentication into all library services requiring authentication. Brings me coffee every morning! OLE Project BPM Workshop – Utah – January 14-15, 2009 Page 4

    + Beth WarnerBeth Warner, 10 months ago

    custom

    462 views, 0 favs, 1 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 462
      • 458 on SlideShare
      • 4 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 1
    Most viewed embeds
    • 4 views on http://oleproject.org

    more

    All embeds
    • 4 views on http://oleproject.org

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories