Wherever sources, processing, or projection information vary among items in a data set, consider describing the components using separate metadata records. Don't document ArcInfo attributes Some data attributes exist as a consequence of the GIS or other software used to create the data. Where these have not been infused with scientific information, they can safely be left undocumented because their meanings and their values can be readily inferred from the knowledge of the software used. This rule of thumb simplifies the presentation of metadata to the end-user as well as their creation and maintenance. Errors are not equally important While it is a useful tool for checking the structure and format of metadata, it is not good to put too much faith in mp.
Human review is the thing that really matters.
Too many of some element Missing elements Empty elements Improper element values Warnings and upgrades 7. Leave some specific elements out if they cause trouble Some metadata elements are difficult to fill out and are so inconsistently understood in the community at large that it does not make sense to agonize over their values. This form of metadata can be used to facilitate the human review of metadata, especially by people who are not conversant with the metadata standard itself. Such keywords can be discovered by web search engines and are able to provide better conceptual associations among related data and reports than non-controlled keywords. Alternative user interfaces such as those based on pick-lists, can be developed if controlled keywords are chosen.