creator: creator
In cboettig/build.eml: Build Ecological Metadata Language Files

creator

creator(individualName = NULL, organizationName = NULL,
  positionName = NULL, address = NULL, phone = NULL,
  electronicMailAddress = NULL, onlineUrl = NULL, userId = NULL,
  references = NULL, id = NULL, system = NULL, scope = NULL)

`individualName`	The full name of the person being described See `individualName()`
`organizationName`	The full name of the organization being described See `organizationName()`
`positionName`	The name of the title or position associated with the resource. See `positionName()`
`address`	The full address information for a given responsible party entry. See `address()`
`phone`	Information about the contact's telephone See `phone()`
`electronicMailAddress`	The email address of the contact. See `electronicMailAddress()`
`onlineUrl`	A link to associated online information, usually a web site. See `onlineUrl()`
`userId`	An identifier that links this party to a directory of individuals See `userId()`
`references`	The id of another element in this EML document to be used to here in this context. See `references()`
`id`	A unique identifier for this additional metadata that can be used to reference it elsewhere. This is a formal field in that it is an error to provide a value for the id attribute that is not unique within the document's set of id attributes. This is designed to allow other portions of the metadata to reference this section formally.
`system`	The data management system within which an identifier is in scope and therefore unique. This is typically a URL (Uniform Resource Locator) that indicates a data management system. All identifiers that share a system must be unique. In other words, if the same identifier is used in two locations with identical systems, then by definition the objects at which they point are in fact the same object.
`scope`	The scope of the identifier. Scope is generally set to either "system", meaning that it is scoped according to the "system" attribute, or "document" if it is only to be in scope within this single document instance. In this particular use of scope, it is FIXED to be "system" because the packageId is required and always has the scope of the required "system".