[
https://issues.apache.org/jira/browse/ATLAS-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087180#comment-16087180
]
Stefhan van Helvoirt commented on ATLAS-1698:
---------------------------------------------
HI [~davidrad], hereby my feedback hopefully its helpfull.
Page 1: you mention
- 'Create a new word'
- 'Create a term'
What is the difference between 'word' and 'term'?
I really like the picture you put on page 2, i see it now in the current work
we do with creating a glossary. It would be highly desirable if the workflow
relating the approval process of terms could be adjusted based on the type of
change that occured. For example, for the creation of a term and the setting of
a definition you would like to have the Definition Owner involved. However when
linking terms together to state in which context they are used, it might not be
needed to follow this same approval process, or at least not need the same
people involved.
Might not be relevant for this JIRA, but something to take into consideration
in the overal design.
Page 3:
What is a visualizable term? Do also non-visualizable terms exsist?
"Need to ensure we have a way to scope what is displayed", would be good if you
could group sets of terms in a category/collection or whatever you call it and
that a graph can be created based on this context. Sometimes you want to have a
graph from a hierarchical perspective, in other situations a functional view
might be more desirable. Should be possible to have both.
Page 4: I don't understand the mentioning of ETL / ELT in this context. Are you
referring here to using ETL/ELT for creating metadata?
> Create Glossary OMAS API
> ------------------------
>
> Key: ATLAS-1698
> URL: https://issues.apache.org/jira/browse/ATLAS-1698
> Project: Atlas
> Issue Type: Sub-task
> Reporter: David Radley
> Assignee: David Radley
> Labels: VirtualDataConnector
> Attachments: apidocs-3.zip, Atlas Glossary OMAS API proposal v1.0
> .pdf, Atlas Glossary OMAS API proposal v1.1.pdf
>
>
> The Glossary OMAS provides a specialized API for glossary applications to
> retrieve and store their glossary metadata and link assets of different types
> to these glossary entries.
> The Glossary OMAS makes heavy use of the Area 2 open metadata model. See
> https://cwiki.apache.org/confluence/display/ATLAS/Area+2+-+Glossary
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
