{"action":"created","issue":{"url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/1024","repository_url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe","labels_url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/1024/labels{/name}","comments_url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/1024/comments","events_url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/1024/events","html_url":"https://github.com/BjerknesClimateDataCentre/QuinCe/pull/1024","id":384771948,"node_id":"MDExOlB1bGxSZXF1ZXN0MjMzODkyNjI4","number":1024,"title":"#909 and #355 - Exporting and NRT","user":{"login":"squaregoldfish","id":733650,"node_id":"MDQ6VXNlcjczMzY1MA==","avatar_url":"https://avatars1.githubusercontent.com/u/733650?v=4","gravatar_id":"","url":"https://api.github.com/users/squaregoldfish","html_url":"https://github.com/squaregoldfish","followers_url":"https://api.github.com/users/squaregoldfish/followers","following_url":"https://api.github.com/users/squaregoldfish/following{/other_user}","gists_url":"https://api.github.com/users/squaregoldfish/gists{/gist_id}","starred_url":"https://api.github.com/users/squaregoldfish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/squaregoldfish/subscriptions","organizations_url":"https://api.github.com/users/squaregoldfish/orgs","repos_url":"https://api.github.com/users/squaregoldfish/repos","events_url":"https://api.github.com/users/squaregoldfish/events{/privacy}","received_events_url":"https://api.github.com/users/squaregoldfish/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-11-27T12:28:10Z","updated_at":"2018-12-11T15:06:04Z","closed_at":null,"author_association":"COLLABORATOR","pull_request":{"url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/pulls/1024","html_url":"https://github.com/BjerknesClimateDataCentre/QuinCe/pull/1024","diff_url":"https://github.com/BjerknesClimateDataCentre/QuinCe/pull/1024.diff","patch_url":"https://github.com/BjerknesClimateDataCentre/QuinCe/pull/1024.patch"},"body":"This is a big pull request the covers export and NRT data handling capabilities. I know it's really too big, but the development of the two in parallel kind of got tangled together and the two branches rely on each other to some extent.\r\n\r\nMain features are:\r\n\r\n* Workflow for data sets: added steps for ICOS verification and approval. Steps are now:\r\n  * Extraction, Data Reduction and Automatic QC as now\r\n  * User QC\r\n  * User submits for expert review\r\n  * Expert approves dataset for export\r\n* Export API and scripts to discover exportable datasets, export them and (eventually) submit them to Carbon Portal, SOCAT etc. The scripts are still in development but the API is solid.\r\n* NRT data. API and scripts for:\r\n  * Retrieve files from initial sources (IMAP email only so far) and upload them to a local FTP server\r\n  * Transfer from FTP into QuinCe\r\n  * Create NRT data set\r\n\r\nNRT datasets have a special status in QuinCe - users can create a new dataset on top of them (which destroys the NRT dataset). NRT datasets are marked as ready for export as soon as automatic QC is complete (no verification required).\r\n\r\nEventually NRT datasets should be read only (i.e. no user QC allowed) - that will come in a future PR."},"comment":{"url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/comments/446234847","html_url":"https://github.com/BjerknesClimateDataCentre/QuinCe/pull/1024#issuecomment-446234847","issue_url":"https://api.github.com/repos/BjerknesClimateDataCentre/QuinCe/issues/1024","id":446234847,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NjIzNDg0Nw==","user":{"login":"squaregoldfish","id":733650,"node_id":"MDQ6VXNlcjczMzY1MA==","avatar_url":"https://avatars1.githubusercontent.com/u/733650?v=4","gravatar_id":"","url":"https://api.github.com/users/squaregoldfish","html_url":"https://github.com/squaregoldfish","followers_url":"https://api.github.com/users/squaregoldfish/followers","following_url":"https://api.github.com/users/squaregoldfish/following{/other_user}","gists_url":"https://api.github.com/users/squaregoldfish/gists{/gist_id}","starred_url":"https://api.github.com/users/squaregoldfish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/squaregoldfish/subscriptions","organizations_url":"https://api.github.com/users/squaregoldfish/orgs","repos_url":"https://api.github.com/users/squaregoldfish/repos","events_url":"https://api.github.com/users/squaregoldfish/events{/privacy}","received_events_url":"https://api.github.com/users/squaregoldfish/received_events","type":"User","site_admin":false},"created_at":"2018-12-11T15:06:04Z","updated_at":"2018-12-11T15:06:04Z","author_association":"COLLABORATOR","body":"> # Regarding issue #909\r\n> **Doc build script:**\r\n> \r\n> ```\r\n>  $ ./Documentation/Design/ExportScripts/build.sh \r\n> ./Documentation/Design/ExportScripts/build.sh: line 11: pandoc: command not found\r\n> ```\r\n> ...do I need to install pandoc? mermaid?\r\n> \r\nWe should revisit this to decide what the best form of documentation is to use as close to a universal Markdown system as possible. Pandoc is pretty widely used, but requiring other extensions might be going too far.\r\n\r\n> **API**\r\n> \r\n> * In file WebApp/src/uk/ac/exeter/QuinCe/api/export/CompleteExport.java: Why is this a POST-request? Would expect this to be GET\r\n\r\nRemains as a POST, because it's telling QuinCe that we've successfully completed our exporting work and the dataset's status can be updated.\r\n\r\n> * You should probably just remove the api/test - folder\r\n\r\nDone.\r\n\r\n> \r\n> Non - essentials:\r\n> \r\n> * Whitespaces at end of lines in Documentation/Design/ExportScripts/ExportScripts.md\r\n> * Replace author zuj007 with Steve Jones :)\r\n\r\nDone"}}
{"actor":{"display_login":"squaregoldfish"}}