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

Make onto_extract and check_urls less developer specific. #12

Open
grosscol opened this issue Aug 6, 2019 · 0 comments
Open

Make onto_extract and check_urls less developer specific. #12

grosscol opened this issue Aug 6, 2019 · 0 comments

Comments

@grosscol
Copy link
Member

grosscol commented Aug 6, 2019

Currently, the ruby and bash scripts make assumptions about the locations of artifacts on disk that are inherent in my system. As such, they won't run on another's system.

These scripts need to be independent of the idiosyncrasies of a single developer's file system.

  • Handle caching ontologies on disk.
  • Handle reading from cached copy or fetching from remote.
  • Handle invoking script from via symlink
  • Handle invoking script from directory other than project root.
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

1 participant