Thursday, May 06, 2010

MADS Implementation Registry

LC wants to start a MADS implementation registry, like the one they have for MODS

If you are using MADS in your institution or project, please submit an entry.

You can either send the information as detailed below to the MODS list, which is what we are using for MADS discussions (mods@loc.gov) or send to ndmso@loc.gov (our office email).

Please include:

  1. The MADS project name
  2. Name of the institution or organization implementing MADS
  3. A short description of the project
  4. A URL to the project web site (if available)
  5. Any web site notes
  6. Projected dates of implementation
  7. A URL to any available documentation or specifications developed for the MADS project
  8. Any notes about documentation
  9. A list of any MADS tools developed and or used as part of the project
  10. Contact name and e-mail address
  11. Any additional contact information.

Additions to the MARC Code List for Relators

The codes listed below have been recently approved. The codes will be added to the MARC Code List for Relators.

The codes should not be used in exchange records until 60 days after the date of this notice to provide implementers time to include newly-defined codes in any validation tables.

Additions:

blw
Blurb writer
clr
Colorist
con
Conservator
db
Distribution place
evp
Event place
mrb
Marbler
pup
Publication place
uvp
University place
Design Patterns: Faceted Navigation by Peter Morville, Jeffery Callender an excerpt from Chapter 4 of Search Patterns (O’Reilly, 2010) is available on A List Apart (the other ALA).
Faceted navigation is a master pattern. Its deployment impacts all other search patterns and the information architecture as a whole. To oversimplify, there’s the Google model and the faceted navigation model. Choosing between these two is a major strategic decision. Determining whether or not faceted navigation is sensible and feasible is among the earliest steps in design. The infrastructure for faceted navigation can enable a tighter relationship between search and browse. It can shape the structure and navigation of the entire site or application. It also changes how we think about autocomplete and best first. It offers a familiar framework for managing the sources of federated search. Plus, its discriminatory power to clarify intent and refine results may offset the need for personalization and advanced search. That said, faceted navigation won’t work everywhere. For starters, it’s an expensive proposition. The demands on search software and servers are substantial. Also, the metadata infrastructure involves both initial investment and ongoing expense. For these reasons and more, a simpler search model is sometimes better, but it must often be supplemented by advanced search.