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

ESGF node information stored in db instead of requiring registration.xml #127

Open
sterlingbaldwin opened this issue Jul 1, 2015 · 2 comments
Assignees

Comments

@sterlingbaldwin
Copy link
Contributor

RIght now, every time the dashboard loads, it parses the registration.xml for ESGF node information. Instead, that information should be stored in the django database. Additionally, we currently only check the pcmdi9.llnl.gov node for its registration file, instead we should query all visible nodes, and build up the db of node information. This way there wont be as much volatility of node list size, and we will have a list of all nodes that have appeared on the network.

@sterlingbaldwin
Copy link
Contributor Author

I would also like to refactor the ESGF UI to use a tree instead of the carousel. The only reason I put the carousel in there was because it was in the mock up, not because it actually made sense from a UI perspective.

@mattben mattben added this to the Sooner than Later milestone Oct 5, 2015
@sterlingbaldwin
Copy link
Contributor Author

Im going to hold off on this until the node manager is working.

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

No branches or pull requests

2 participants