1. MUI Purpose
Conversion: current vocabulary-ui manager to the metadata-ui manger (MUI).
No database and is services oriented
Assigns identification numbers to controlled vocabulary terms
Metadata functionality: (use fields metadata format)
Document metadata frameworks (field name, definitions, attribution, controlled vocabulary terms, XPATH, cataloging best practices, child elements, max/min occurrences, example data, data type).
Interface functionality: (use groups metadata format)
Track user interface labels, bread crumbs, ordering and grouping layouts, definitions and attribution information to different UIs
Web services / discovery functionality:
Metadata field & MUI assigned vocab ids are used to shorten the length of query strings. Make requests to MUI using metadata format, metadata version and metadata field identification/XPATH to get the shortened stuff for the query

2. Metadata Frameworks
ADN – v for web resources; upgrading for 4th level standards and a technical issue
Annotation - v in library; v includes standards, aligns, hierarchal, rating (plus the existing description and url)
Collection – title, key, format, services, OAI, NSDL, accessioning info (v1.0.00)
News-Opps – news and events (v1.0.00)
Fields – cataloging best practices & vocab deftns
OPML (base) – subscription feeds (v2.0)
OPML (groups for MUI) – UI labeling, grouping and ordering of metadata content (v1.0)
OPML (tree menus) – e.g. metadata menu (v1.0)

3. Crosswalks (using XSLT)
ADN
ADN to NSDL_DC 1.02
ADN to Oai_DC
Annotation
Anno to Anno
Anno to Oai_DC
News
News-Opps to Oai_DC
Collection
Collection to Oai_Dc
Collection builders
Numerous crosswalks from native metadata to ADN or News
Fields
Fields to groups OPML for MUI
Web services are used extensively!!!