{"action":"created","issue":{"url":"https://api.github.com/repos/ropensci/EML/issues/135","repository_url":"https://api.github.com/repos/ropensci/EML","labels_url":"https://api.github.com/repos/ropensci/EML/issues/135/labels{/name}","comments_url":"https://api.github.com/repos/ropensci/EML/issues/135/comments","events_url":"https://api.github.com/repos/ropensci/EML/issues/135/events","html_url":"https://github.com/ropensci/EML/issues/135","id":130798028,"number":135,"title":"adding `directory` XML attribute to EML document","user":{"login":"mbjones","id":766407,"avatar_url":"https://avatars.githubusercontent.com/u/766407?v=3","gravatar_id":"","url":"https://api.github.com/users/mbjones","html_url":"https://github.com/mbjones","followers_url":"https://api.github.com/users/mbjones/followers","following_url":"https://api.github.com/users/mbjones/following{/other_user}","gists_url":"https://api.github.com/users/mbjones/gists{/gist_id}","starred_url":"https://api.github.com/users/mbjones/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbjones/subscriptions","organizations_url":"https://api.github.com/users/mbjones/orgs","repos_url":"https://api.github.com/users/mbjones/repos","events_url":"https://api.github.com/users/mbjones/events{/privacy}","received_events_url":"https://api.github.com/users/mbjones/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ropensci/EML/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2016-02-02T19:56:07Z","updated_at":"2016-02-18T00:02:17Z","closed_at":null,"body":"@cboettig We want to use the EML `userId` element within the creator field, but it requires the `directory attribute to be set.  I'm unclear how to do that.  In the end, the EML we want would be:\r\n\r\n```xml\r\n<creator>\r\n    <individualName>\r\n        <givenName>Matthew</givenName>\r\n        <surName>Jones</surName>\r\n    </individualName>\r\n    <userId directory=\"http://orcid.org\">http://orcid.org/0000-0003-0077-4738</userId>\r\n</creator>\r\n```\r\n\r\nIn the R client, I think you would do:\r\n```R\r\neml@dataset@creator[[1]]@userID <- \"http://orcid.org/0000-0003-0077-4738\"\r\n```\r\nI'm not sure right off how you set the required `directory` attribute in the EML package. Any pointers? \r\n\r\nAlso, in party_classes.R, shouldn't the responsibleParty `userID` slot be `userId` to match the EML capitalization? \r\n\r\nThanks."},"comment":{"url":"https://api.github.com/repos/ropensci/EML/issues/comments/185467173","html_url":"https://github.com/ropensci/EML/issues/135#issuecomment-185467173","issue_url":"https://api.github.com/repos/ropensci/EML/issues/135","id":185467173,"user":{"login":"cboettig","id":222586,"avatar_url":"https://avatars.githubusercontent.com/u/222586?v=3","gravatar_id":"","url":"https://api.github.com/users/cboettig","html_url":"https://github.com/cboettig","followers_url":"https://api.github.com/users/cboettig/followers","following_url":"https://api.github.com/users/cboettig/following{/other_user}","gists_url":"https://api.github.com/users/cboettig/gists{/gist_id}","starred_url":"https://api.github.com/users/cboettig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cboettig/subscriptions","organizations_url":"https://api.github.com/users/cboettig/orgs","repos_url":"https://api.github.com/users/cboettig/repos","events_url":"https://api.github.com/users/cboettig/events{/privacy}","received_events_url":"https://api.github.com/users/cboettig/received_events","type":"User","site_admin":false},"created_at":"2016-02-18T00:02:17Z","updated_at":"2016-02-18T00:02:17Z","body":"@mbjones Great, thanks.  Will plan to merge into EML repo then as soon as `eml2` has minimal functionality.  Just have to figure out what that entails.  \r\n\r\nCan you give me any hints as to what EML functions you are using currently?  I can try porting over the functions & methods in the EML namespace, but I think some are poorly designed and would be better to deprecate.  Getting a better sense of how you and @ivanhanigan are using EML could also inform what functions need to be in `eml2` before we port it over here.  "}}