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

Resource form misses license, language, format and more #18

Open
3 tasks
wenzeslaus opened this issue Aug 10, 2017 · 4 comments
Open
3 tasks

Resource form misses license, language, format and more #18

wenzeslaus opened this issue Aug 10, 2017 · 4 comments

Comments

@wenzeslaus
Copy link
Member

wenzeslaus commented Aug 10, 2017

In comparison to the edu content inventory (e.g. http://www.osgeo.org/node/1592), the resource form does not have a field for a:

  • license (e.g. can I reuse commercially?)
  • (natural) language
  • format (that's good to know what you will get when you get there; a web page, website, GitHub repo with Markdown files, PDF, ...?).

The level of experience (Graduate Students, Intermediate GIS Users, Mid-career, ...) and multiple URLs are also missing, but I can see good reasons to leave them out (e.g. unclear definitions).

@jodygarnett
Copy link
Sponsor Contributor

Those are some good suggestions, I also want to make sure that it is easy/quick to add content so we should balance the number of fields we require.

Would it be okay to have a "spec" section like projects where you can list details such as you describe? Or does it need to be structured.

@wenzeslaus
Copy link
Member Author

I don't think it needs to be structured much, but it can be on some Spec page. Pages actually helped me with filling.

It definitively should be optional. However, searching by a license is an important case and we should be care about licensing of these in the same way we care about licenses for code. Having them as explicit (rather than fields) I think may encourage people to actually fill it if they know the answer. Some radio buttons e.g. "CC BY, CC BY-SA, ... + Not specified + Other:" for license would make filling faster. Minimizing the number of fields makes sense, but I would prefer to see Language rather than Discipline which seem to me quite restrictive.

I'm actually fine with more and overlapping fields because it may improve search or systematic sorting, but if we are trying to minimize them, I think there is some overlap. Community, Tags and Initiative have similar descriptions (I think I ended up putting GeoForAll everywhere). Obviously, anything/everything can go to Tags, so I actually don't know what to do with this field. Again, if it is from GeoForAll community seems to be of lesser importance for the user than if they can take it, modify it, and resuse it.

@jodygarnett
Copy link
Sponsor Contributor

@jodygarnett
Copy link
Sponsor Contributor

For multiple URLs you should be able to add multiple call to actions, I have done so in a few places.

Example: http://osgeo.getinteractive.nl/resources/osgeo-agm-2017/

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