Hi,
To create a mapping you'll need to create "units" for each field or group of fields (Eg. forename, surname, middlename for an entity) you want to map. Each unit contains one or more mappings between CA bundles (aka fields) and targets in the output format – OAI_DC in this case.
The CollectiveAccess side of the mappings need to have bundle specifiers in the form described here: http://docs.collectiveaccess.org/wiki/API:Getting_Data#Bundle_specifiers
The OAI_DC side of the mappings needs a simple tag path, in the form /dc:title for title.
The base values for each side were intended as shortcut prefixes that are simply prepended onto the mapped values to create the full CA bundle specifiers and tag paths.
If you set the base for the CA side to ca_objects and the mapping to preferred_labels.name, then the bundle specifier ca_objects.preferred_labels.name is what will be used. Similarly, if the prefix for the OAI_DC tag path is "/" and the mapped tag is dc:title, then /dc:title will be used in the mapping.
If this all sounds confusing and rather ill-conceived that's because, well, it is. We've been working on designs for a replacement UI that is visual and drag-and-drop. It is something we want to do soon, but there's still a lot of work to do.
Please give the current UI a try and if it proves unworkable (quite likely) perhaps we can rig up a way for you to specify the mapping in a configuration file, as a bridge until the new UI is available.
seth