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

MC-9891 Update subscribed catalogue UI due to breaking core changes #612

Merged
merged 3 commits into from
Jul 25, 2022

Conversation

pjmonks
Copy link
Contributor

@pjmonks pjmonks commented Jul 20, 2022

Note: this depends on MauroDataMapper/mdm-resources#71

  • Update admin setup forms to use Angular reactive forms
  • Add new connection type field to add/edit subscribed catalogue
  • Display connection type of each subscribed catalogue in the list view
  • Handle case where published model type is not known
  • Display published data model dates
  • Update Subscribe Data Model dialog to use Angular reactive forms
  • Send additional properties during subscribed model creation - content link and/or importer

Screenshots

Admin screen of subscribed catalogues with subscribed catalogue types:

image

Inclusion of dates from published data models:

image

Updates to subscribe dialog:

image

@pjmonks pjmonks added this to the 7.2.0 milestone Jul 20, 2022
Copy link
Contributor

@joe-crawford joe-crawford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @pjmonks.

I'm testing this by using develop of mdm-core, feature/mc-9681 of mdm-ui and mdm-resources.

I have been able to use the UI to add a Mauro JSON subscription to https://modelcatalogue.cs.ox.ac.uk/continuous-deployment and use the new modal to subscribe to a model.

There's an issue when viewing published models when connecting to an Atom catalogue however, I'm testing using an Atom subscription to https://modelcatalogue.cs.ox.ac.uk/continuous-deployment/api/feeds/all (with an API key).

I can see a list of published models in the tree on the left hand side of the UI, however when selecting these models a Not Found error appears in the main panel. Could you have a look at this?

N.B. When subscribing to an Atom catalogue, the modelIds returned in the /publishedModels and other endpoints will be unique but are not of any particular format as they come from the Atom source. In the Mauro Atom subscribed catalogue they are of the form urn:uuid:<UUID> but in general they could be any string. I'm wondering if this may be causing the issue.

@joe-crawford
Copy link
Contributor

I've noticed the backend error text isn't very user friendly when selecting an incompatible model content type and importer to subscribe to, I'll try to update this.

@joe-crawford
Copy link
Contributor

Also looking at the published models ordering on the backend as that seems out of order.

* Update admin setup forms to use Angular reactive forms
* Add new connection type field to add/edit subscribed catalogue
* Display connection type of each subscribed catalogue in the list view
* Handle case where published model type is not known
* Display published data model dates
* Update Subscribe Data Model dialog to use Angular reactive forms
* Send additional properties during subscribed model creation - content link and/or importer
* Remove checks for UUID model IDs, there are no longer guarantees the model ID of a published model is in this format
* Display Catalogue type and URL when viewing a Subscribed Catalogue from the model tree
* Remove error triggered by trying to redirect to a data model, this was unnecessary
* Removed newer versions table error on having two columns sortable by same key
@pjmonks pjmonks marked this pull request as ready for review July 25, 2022 12:34
@pjmonks pjmonks merged commit 5e4b666 into develop Jul 25, 2022
@pjmonks pjmonks deleted the feature/mc-9891 branch July 25, 2022 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Released
Development

Successfully merging this pull request may close these issues.

None yet

2 participants