atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-1054) Allow Terms rather than assets to be the primary entities in the API and UI.
Date Tue, 26 Jul 2016 16:24:20 GMT

     [ https://issues.apache.org/jira/browse/ATLAS-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Radley updated ATLAS-1054:
--------------------------------
    Description: 
I see that ATLAS-812 allows the user to associate terms with Assets. 

For governance use cases a natural way is to work with terms and assets is to work with the
business glossary terms as the primary entities both in the Ui and in the REST API. 

I suggest the user be allowed :
- find the term of interest and then associate it with an asset
- be able to view terms and their associated assets in one REST GET term call. I suggest returning
the assets as a subobjects (I suspect we will want to have a inquirylevel where 1 would just
return the terms , and 2 would include subobjects.
- allow classifications to be specified against the terms.  I would like to see more intuitive
words like term, asset and classification rather than tag , trait or trait name in the UI
and API. 


  

  was:
I see that ATLAS-812 allows the user to associate terms with Assets. 

For governance use cases a natural way is to work with terms and assets is to work with the
business glossary terms as the primary entities both in the Ui and in the REST API. 

I suggest the user be allowed :
- find the term of interest and then associate it with an asset
- be able to view terms and their associated assets in one REST GET term call. I suggest returning
the assets as a subobjects (I suspect we will want to have a inquirylevel where 1 would just
return the terms , and 2 would include subobjects.
- allow classifications to be specified against the terms ( am am currently unclear whether
this classification would be a tag , trait or trait name). 
  


> Allow Terms rather than assets to be the primary entities in the API and UI.
> ----------------------------------------------------------------------------
>
>                 Key: ATLAS-1054
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1054
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: David Radley
>
> I see that ATLAS-812 allows the user to associate terms with Assets. 
> For governance use cases a natural way is to work with terms and assets is to work with
the business glossary terms as the primary entities both in the Ui and in the REST API. 
> I suggest the user be allowed :
> - find the term of interest and then associate it with an asset
> - be able to view terms and their associated assets in one REST GET term call. I suggest
returning the assets as a subobjects (I suspect we will want to have a inquirylevel where
1 would just return the terms , and 2 would include subobjects.
> - allow classifications to be specified against the terms.  I would like to see more
intuitive words like term, asset and classification rather than tag , trait or trait name
in the UI and API. 
>   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message