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

R1.2: Determine what platform the service runs on in order to make a decision about feasibility of local deployment #2

Open
nsjuty opened this issue Mar 26, 2020 · 4 comments
Assignees
Labels
Projects

Comments

@nsjuty
Copy link

nsjuty commented Mar 26, 2020

Kurt & Petros
reviewer #1: @karsten-quast
see: https://drive.google.com/open?id=1RBa2YOltsOL_I_sbmEwop48HXAVLI6C0ocBBckVRW4Y

  1. Determine what platform the service runs on in order to make a decision about feasibility of local deployment
    Branch/decision point: Decide if the service runs in house based on the feasibility analysis
@nsjuty nsjuty added this to planning in UC3 Mar 26, 2020
@nsjuty nsjuty moved this from planning to in progress in UC3 Mar 26, 2020
@nsjuty nsjuty moved this from in progress to planning in UC3 Mar 27, 2020
@nsjuty nsjuty changed the title r1.2.1.2.1.2 R1.2: Determine what platform the service runs on in order to make a decision about feasibility of local deployment Mar 27, 2020
@nsjuty nsjuty moved this from planning to in progress in UC3 Mar 27, 2020
@nsjuty nsjuty added this to the 5th F2F (virtual) milestone Mar 27, 2020
@nsjuty
Copy link
Author

nsjuty commented Apr 8, 2020

change title to:
Technical & architectural selection criteria of ontology lookup services
(gi to >1 public ontologies)

@petrospaps
Copy link

@petrospaps
Copy link

in markdown

@petrospaps
Copy link

The recipe is now merged to the dev branch.

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

No branches or pull requests

2 participants