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

General suggestions and discussions on improving structure #6

Open
angelosalatino opened this issue Feb 19, 2019 · 5 comments
Open

Comments

@angelosalatino
Copy link
Contributor

Hi,
Since now the taxonomy section is getting large, we might think of dividing it by disciplines, e.g., Computer science, economy, math, and so on. What do you think? In the future this will allow us to easily find out what is missing and what to add.
On the other hand, I realised that you added SciGraph as a taxonomy. But actually it is a dataset. I would move it up in "Publication and Citation", instead.

Hope this helps

@napsternxg
Copy link
Owner

Hi @angelosalatino I think compared to other sections it is still small, and there is usually going to be 1 or 2 taxonomy for each field, hence the current layout looks good.

@angelosalatino
Copy link
Contributor Author

Ok. I just wanted to give more structure to the list. Maybe we can rearrange the list. Maybe in alphabetical order.

@napsternxg napsternxg changed the title some reflections General suggestions and discussions on improving structure Feb 20, 2019
@napsternxg
Copy link
Owner

@angelosalatino added a new issue for your suggestion. Let us use this thread to find possibilities to improve it. However, I want the curation to be minimal effort so that we have higher coverage of content.

@napsternxg
Copy link
Owner

napsternxg commented Feb 20, 2019

My core guiding principle for this list is that it should be easy to curate (i.e. can be edited using just the browser), has high coverage of content. I think any improvement or changes to the list should consider that aspect. E.g. it is very easy for me to add new items even from my phone, using the github edit, and this updates the page in realtime.

Just wanted to add some personal opinions (I am still open to discussion about these).

Do you think we can have a json file to curate the list which can be used to automatically generate the content on the webpage? I am not sure how will it affect curating the README automatically. I think that limits the accessibility to edit only for those who know JSON, and also runs the issue of keeping the README out of sync.

Currently, I could easily add content to README and the website will be auto updated. I am not sure if that can be achieved and the list curation is still user friendly with any automated method.

@angelosalatino
Copy link
Contributor Author

@napsternxg I completely agree with you. Better if we keep it simple (as it is now for instance).
JSON would be cool. However, curating a json dictionary requires us to manipulate it by hand or specific software.

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

2 participants