The metadata should enable other people to use the data. What merely passes mp is not necessarily of sufficient quality or usability for end users. A good metadata review involves examination of the data, and our goal is to improve the integrity and quality of the research results produced by USGS for the Nation.
Good metadata is good scientific writing, lively and engaging. It should never be stilted or overly complex.
Here is an annotated list of elements that reviewers should pay special attention to, because they are used by software that carries out further processing of the metadata, or because they are sometimes entered incorrectly or awkwardly.
The Title must never be a file name or a UUID.
Assume links are case sensitive--get the letter case right. Windows systems are not case sensitive, Web servers usually are.
Be on the lookout for links that are not complete, that are awaiting information such as a publication number or data release identifier.
Larger_Work_Citation sections can be nested ad infinitum. There should be a really good reason if you see more than two levels of Citation_Information within the Citation.
Don't let the abstract begin with the mission statement of the project, program, science center, or the USGS as a whole.
The purpose of these data should be more specific than the mission statement of the project, program, science center, or the USGS as a whole.
No projected coordinates--must be latitude and longitude as decimal degrees.
This should be about more than geometrical topology.
Be alert for statements that don't say anything useful.
Entity_and_Attribute_Detail_Citation is a good place for a URL to a methods report.
This should not be the same as the Attribute_Label. It should be possible to make a clearer statement.
Some software writes "Downloadable data". That is incorrect.
Be alert for text that demands more of our users than is permissible.
We are working to provide controlled vocabulary for this field, but our work is not yet complete.
Test the links to make sure they work. Be alert to incomplete URLs awaiting information.
Remember that in CSDGM all dates are written YYYYMMDD, like 20160811. No dashes, no slashes.