Automatically importing a study with lists and reports | gkericks | 2017-04-24 14:54 | |||||||||||||||||||||||||||
Status: Closed | |||||||||||||||||||||||||||||
Hi there, I have been working working on a system to facilitate using Labkey with an external data collection service. Our use case is as follows: We have many different teams accessing various project on a Labkey server. They are mostly using the tool to share files and post wikis. For each project (or at least most of the projects) we will have a corresponding project in the aforementioned external service. The corresponding projects in the external service are the points of data collection and they will be constantly updated. What I want to do: I have been working to standardise and automate moving data out of the external service and in to labkey. I have wrote a simple program that requests data from the external service using an API. I want to also automate the importing of that data into Labkey. Now, I started using the study import/reload features. I have gotten pretty far with this approach and can automate the data reloading as a study. As I have tried to add more details to the import, this has gotten more difficult. Current challenge: The study reload feature doesn't include lists or reports. This is problematic for two reasons: 1) Lists are needed to encode complex data types where the raw representation is different from the labels. 2) Reports will change as the number of projects we support changes and we want to be able to easily export a a 'stock' report to many different projects. I have been trying to get the technique described here (https://www.labkey.org/home/Support/Developer%20Forum/announcements-thread.view?rowId=11385) to work with no success. I am using Labkey 16.2. I am also using pycurl to give commands to curl. Does anyone know if this technique still works? Does the fact that I am using pycurl (python) matter? I would really appreciate some feedback and discussion around this. The automation of the study export/import/reload went fairly smoothly, however trying to add in extra features (reports, data type encoding via lists, anything to do with folder structure) has been a headache. I am guessing these challenges arise because Labkey does not explicitly support reloading of arbitrary folder types so perhaps I am simply looking into the wrong features for our use case. |
|||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||