atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Selvamohan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-491) Business Catalog / Taxonomy
Date Sat, 07 May 2016 03:56:13 GMT

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

Selvamohan Neethiraj updated ATLAS-491:
---------------------------------------
    Attachment:     (was: 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch)

> Business Catalog / Taxonomy
> ---------------------------
>
>                 Key: ATLAS-491
>                 URL: https://issues.apache.org/jira/browse/ATLAS-491
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 0.7-incubating
>            Reporter: Erik Bergenholtz
>            Assignee: John Speidel
>             Fix For: 0.7-incubating
>
>         Attachments: 0001-ATLAS-491-Business-Catalog-API-changes-by-John-Speid.patch,
business-catalog-WIP.patch
>
>
> s a Atlas UX user, I need to:
> Browse business taxonomy hieracharlically through tree
> Search by Tags
> Search by combination of keyword, tag, free text in search field
> All search from view context of taxonomy. If 3 levels deep, then the search should be
narrow to that scope.
> expose search ordering capabilities available through SOLR.
> As a Data Steward, I need to:
> Manage the taxonomy of objects including
> Objects Management:
> Creating new objects
> Modify the object details - annotations, external links, tags, acceptable use policy,
etc
> Delete objects (in UI - changing status in backend,and versioning changes)
> Relationship management:
> creating relationship of objects as a parent or child
> assigning tagging to taxonomy
> verify tag inheritance
> Verify tag impact on tag based policy - ranger API call
> Tag Management:
> List
> Search
> Edit
> Delete (change state to archive)
> All user should be able to comment on any business catalog entity.



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

Mime
View raw message