uva-dsi / open-data-lab Goto Github PK

@mlev71 can you check out the ds store file and kill it if we don't need it
-alonzi

One way to start looking into this would be to check open resources like

• https://github.com/awesomedata/awesome-public-datasets
  and see how sustainable/ usable the data are there.

On that basis, we could then decide (see also the inclusion criteria in ODL, as per #18 ) as to whether we'd like to go for datasets scoring high and/or low / average on those scales.

As usual, we should follow the data citation principles. Pinging @timclark .

This mirrors a sister ticket on datasets (cf. #28 ), which need some infrastructure around them to be used.

as per https://github.com/UVA-DSI/Open-Data-Lab/labels

Of course, we should follow the data citation principles. Pinging @timclark .

1. send sms to AWS with project ID and email address
2. lambda function stands up vm
3. lambda function puts .bash_profile on vm with mounting commands
4. lambda function emails user with .pem file and command to connect

e.g. https://www.re3data.org/ .

Again, we should follow the data citation principles. Pinging @timclark .

fill out details of HMTT data transfer here: https://github.com/UVA-DSI/Open-Data-Lab/blob/master/aws/large_s3_transfer/README.md

e.g. as expressed in their Data Management Plans

Would be useful to start thinking about that now, so that we can demonstrate impact right from the start of the public beta.

as per #12 and #4 .

as per #7 .

right now vm_stand_up emails text to copy into a script. it should be changed to just send the email with the script attatched.

currently the api gateway throws a 502 error. The function still runs and the vm is created sucessfully but the response code should be 200 and a success message should be sent.

as per https://github.com/UVA-DSI/Open-Data-Lab/projects .

as per https://github.com/UVA-DSI/Open-Data-Lab/milestones .

Probably not necessary for the small number of labels we have right now, but potentially very useful if that number grows.

Adding #12 for tracking.

as per #3 and #4.

@Daniel-Mietchen would you take the lead on setting up issue templates?
-alonzi

some potential dimensions:

• relevance
  • to other DSI activities
  • to communities around DSI
• openness
  • licensing
  • formats
  • standards