Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore yaml/code/git-based configs #5

Open
LanesGood opened this issue Aug 19, 2024 · 3 comments
Open

Explore yaml/code/git-based configs #5

LanesGood opened this issue Aug 19, 2024 · 3 comments

Comments

@LanesGood
Copy link
Member

@yunica @Rub21 As we start to understand how the AtlasArena application data is structured, we will also want to lay out a few proposed ideas for how models, data, and content can be updated and managed by the UC Davis team.

Our proposal and past projects use a YAML-based approach. Do you think this is feasible for this application? What would the requirements for setting up YAML config be, and does the data and models you're investigating lend itself to this approach?

Are there any other approaches or methods you would recommend or prefer based on the datasets and models?

@yunica
Copy link
Collaborator

yunica commented Aug 19, 2024

@LanesGood , the structure provided by the yaml files seems to be sufficient to manage the model data, configuration parameters and static information, we can separate them into a folder so that the UC Davis team can update them.

@Rub21
Copy link
Collaborator

Rub21 commented Sep 9, 2024

@LanesGood It seems YAML files have already worked for past projects. Could you share a couple of those YAML files so we can review them and adapt them for the AtlasArena project?

@LanesGood
Copy link
Member Author

@Rub21 this seems to be under your area of expertise, so I defer to your leadership here. Areas where I know you have lead these efforts include Afghanistan Elections.

Here's a link from Afghanistan, where the API was configured by a YAML file:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants