--- /dev/null
+targetname usmarc
+targetref USmarc
+
+map localControlNumber /(3,001)/(3,@)
+map dateLastModified /(3,005)/(3,@)
+
+map subject /(3,653)/(3,a)
+map title /(3,245)/(3,a)
+map author /(3,700)/(3,a)
+map publisher /(3,260)/(3,b)
+map otheragent /(3,710)/(3,a)
+map date /(3,260)/(3,c)
+map identifier /(3,024)/(3,a)
+# objectType skipped for now
+map form /(3,538)/(3,a)
+map relation /(3,787)/(3,a) # complexity here
+map language /(3,041)/(3,a)
+map source /(3,786)/(3,a)
+# coverage skipped for now
+
+map abstract /(3,520)/(3,a)
--- /dev/null
+#
+# This is a simple profile based on the Dublin Core of metadata elements.
+# Tags are pulled from tagsetG when
+
+name meta
+attset bib1.att
+tagset meta.tag
+varset var1.var
+
+esetname F @
+esetname B meta-b.est
+
+maptab meta-usmarc.map
+
+elm (1,10) rank -
+elm (1,12) url -
+elm (1,14) localControlNumber Local-number
+elm (1,16) dateOfLastModification Date/time-last-modified
+elm (4,1) subject Subject-heading
+elm (2,1) title Title
+elm (2,2) author Author
+elm (2,3) publisher Publisher
+elm (4,2) otherAgent -
+elm (2,4) date Date
+elm (4,3) objectType Content-type
+elm (4,4) form Material-type
+elm (4,5) identifier -
+elm (4,6) relation -
+elm (4,7) source -
+elm (4,8) language Code-language
+elm (4,9) coverage -
+
+# Sorry - I can't bear the thought of not having an abstract.
+
+elm (2,6) abstract Abstract