{"action":"created","issue":{"url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1391","repository_url":"https://api.github.com/repos/datacleaner/DataCleaner","labels_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1391/labels{/name}","comments_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1391/comments","events_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1391/events","html_url":"https://github.com/datacleaner/DataCleaner/issues/1391","id":159918093,"number":1391,"title":"DC Monitor REST API to get jobs should return more information about the jobs","user":{"login":"JoosjeBoon","id":12826034,"avatar_url":"https://avatars.githubusercontent.com/u/12826034?v=3","gravatar_id":"","url":"https://api.github.com/users/JoosjeBoon","html_url":"https://github.com/JoosjeBoon","followers_url":"https://api.github.com/users/JoosjeBoon/followers","following_url":"https://api.github.com/users/JoosjeBoon/following{/other_user}","gists_url":"https://api.github.com/users/JoosjeBoon/gists{/gist_id}","starred_url":"https://api.github.com/users/JoosjeBoon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JoosjeBoon/subscriptions","organizations_url":"https://api.github.com/users/JoosjeBoon/orgs","repos_url":"https://api.github.com/users/JoosjeBoon/repos","events_url":"https://api.github.com/users/JoosjeBoon/events{/privacy}","received_events_url":"https://api.github.com/users/JoosjeBoon/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/datacleaner/DataCleaner/labels/Type:%20Enhancement","name":"Type: Enhancement","color":"006b75"}],"state":"open","locked":false,"assignee":{"login":"LosD","id":1282832,"avatar_url":"https://avatars.githubusercontent.com/u/1282832?v=3","gravatar_id":"","url":"https://api.github.com/users/LosD","html_url":"https://github.com/LosD","followers_url":"https://api.github.com/users/LosD/followers","following_url":"https://api.github.com/users/LosD/following{/other_user}","gists_url":"https://api.github.com/users/LosD/gists{/gist_id}","starred_url":"https://api.github.com/users/LosD/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LosD/subscriptions","organizations_url":"https://api.github.com/users/LosD/orgs","repos_url":"https://api.github.com/users/LosD/repos","events_url":"https://api.github.com/users/LosD/events{/privacy}","received_events_url":"https://api.github.com/users/LosD/received_events","type":"User","site_admin":false},"milestone":null,"comments":3,"created_at":"2016-06-13T10:23:18Z","updated_at":"2016-06-22T08:44:12Z","closed_at":null,"body":"The API to get available jobs (repository/{tenant}/jobs) returns a list of job names and path. However this information is not enough for smooth integration in DataHub. Additionally this (or another) API endpoint should return the following information:\r\n\r\n1) Job metadata (the metadata-properties of the job as shown in the example below)\r\n```\r\n <metadata-properties>\r\n            <property name=\"Group\">Person Enrichment</property>\r\n            <property name=\"Category\">Enrichment</property>\r\n            <property name=\"CoordinatesX.GoldenRecords.person\">154</property>\r\n            <property name=\"CoordinatesY.GoldenRecords.person\">77</property>\r\n        </metadata-properties>\r\n```\r\n\r\n2) Job components list\r\nA list of the component descriptors present in the job. E.g.\r\n```\r\n[\r\n  {type: \"transformer\", descriptor: \"NL Consumer Check\", medatataProperties: [the metadata properties of the component]},\r\n {type: \"transformer\", descriptor: \"NL Deceased Check\", medatataProperties: [the metadata properties of the component]}\r\n]\r\n```"},"comment":{"url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/comments/227680485","html_url":"https://github.com/datacleaner/DataCleaner/issues/1391#issuecomment-227680485","issue_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1391","id":227680485,"user":{"login":"JoosjeBoon","id":12826034,"avatar_url":"https://avatars.githubusercontent.com/u/12826034?v=3","gravatar_id":"","url":"https://api.github.com/users/JoosjeBoon","html_url":"https://github.com/JoosjeBoon","followers_url":"https://api.github.com/users/JoosjeBoon/followers","following_url":"https://api.github.com/users/JoosjeBoon/following{/other_user}","gists_url":"https://api.github.com/users/JoosjeBoon/gists{/gist_id}","starred_url":"https://api.github.com/users/JoosjeBoon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JoosjeBoon/subscriptions","organizations_url":"https://api.github.com/users/JoosjeBoon/orgs","repos_url":"https://api.github.com/users/JoosjeBoon/repos","events_url":"https://api.github.com/users/JoosjeBoon/events{/privacy}","received_events_url":"https://api.github.com/users/JoosjeBoon/received_events","type":"User","site_admin":false},"created_at":"2016-06-22T08:44:12Z","updated_at":"2016-06-22T08:44:12Z","body":"Hey guys just adding my two cents. If you do it this way that means that a REST user is forced to know up front which job they want to use. The idea we had was to put some metadata inside the job like shown below: \r\n\r\n`<property name=\"Category\">Enrichment</property>`\r\n\r\nAnd then fetch all jobs and filter the ones belonging to this group. Otherwise we will have to do something with file names: e.g.: \r\n\r\n> enrichment.NLCC.analysis.xml\r\n\r\n Which we would like to avoid.\r\n\r\nSo I was expecting an additional endpoint more like: repository/{tenant}/jobs/metadata\r\nWhich returns something like:\r\n\r\n`[\r\n{filename: \"job1.analysis.xml\", name:\"job1\", metadata:{\r\nCategory: \"Enrichment\"\r\n}},\r\n{filename: \"job2.analysis.xml\", name:\"job2\", metadata:{\r\nCategory: \"Onboarding\"\r\n}}\r\n]`"}}
{"actor":{"display_login":"JoosjeBoon"}}