Update validation use cases (model registering issue)

[alex4200]

Summary

Aspect	Detail
Summary	Will manage duplication of model entries
Usecase Group	Validation
State	Update
Expert	Shailesh
User	All
Deadline	M12 (March 2019)
Target audience	All
Target interface	Notebook
HPC Requirements	None
Dependencies	None
Nominal runtime	Highly variable depending on usecase/test/model (typical cases < 1h)

List of features

Update the existing validation usecases to prevent duplication of model catalog entries. Features/purpose remains same as before.

Tasks

• [ ] Requires completion of #85
• [x] Prevent duplication of entries in model catalog
• [x] Update UseCases to work with latest releases of packages

Acceptance Criteria

• [ ] Check if all the validations use cases are working
• [ ] Confirm that no duplicate model catalog entries are created for the same model

Extra Requirements

System

None at the moment.

Performance

None defined. Highly variable depending on usecase/test/model (typical cases < 1h)

[appukuttan-shailesh]

As this isn't too urgent, we have decided to attend to this after we complete the switch to KnowledgeGraph. The current milestone (M12) seems appropriate.

[alex4200]

Requires completion of #85 first.

[alex4200]

Will be started in Feb/Mar 2019

[appukuttan-shailesh]

Resolves model duplication in UseCases via fix in #428