atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <>
Subject [jira] [Commented] (ATLAS-491) Business Catalog / Taxonomy
Date Mon, 16 May 2016 15:20:13 GMT


Hemanth Yamijala commented on ATLAS-491:

One other requirements issue which I missed. In the current patch, every business term could
have an independent set of attributes. Is this by design? Or would each business term have
a standard set of attributes. Or somewhere in-between - as in some fixed set and some extensible.

> Business Catalog / Taxonomy
> ---------------------------
>                 Key: ATLAS-491
>                 URL:
>             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
> 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,
> 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

View raw message