0

Verify Data Model and upload Glossary file

Hyeyoon Moon TPV

September 11, 2024 07:35

None

Follow

Hi,

 

I tried [Verify Data Model] and found the document about "Verify Data Model" but had some Questions.

Example)
Terms in Glossary file :
 - print_flag
 - move_type_print_flag

Result :
 - print_flag - correct
 - move_type_print_flag - Inconsistent terms

 

Question 1.
The two terms were in the Glossary file but I couldn't understand why 'move_type_print_flag' is inconsistent terms.
Could you explain the criteria for distinguishing between 'Class terms' and 'Prime terms'?
Because they both can be 'a word' or 'phrases'.
I'm wondering how the tool identifies them.

 

Question 2.
If a file uploaded on Hackolade changes, should I upload it again?
Because the path and file name are the same, it would be nice to have a function to refresh the file.

 

Question 3.
Can I load the Glossary file by Github (or link such as google drive)?
Because Glossary file and Attribute properties rules file will be shared by public storages.
Please let me know whether files can be uploaded only direct path or links.

Best regards,
Hyeyoon Moon

• Facebook
• Twitter
• LinkedIn

1 comment

• 
  Helpdesk September 11, 2024 19:36 Official comment

  Hello Hyeyoon,

  If I may suggest, you should ask your questions to support@hackolade.com instead of this inactive forum.

  Thanks for reviewing the documentation!  

  1) we consider as a "term" something that is separated from other words.  And they are typically in Business names (as opposed to technical names which are typically "attached" like snake_case or camelCase.)  In your example you cite snake_case names that are probably technical, which is not the purpose of the feature.  Did you try with separate class and prime terms?

  2) We could have that feature indeed.  We will add it to the backlog.  In the meantime, you should just restart the application.

  3) Yes, absolutely.  We already promote this approach for other customizations, as described here https://hackolade.com/help/Userdefinedcustomproperties.html#Share%20customization%20with%20team%20members  I suggest you leverage a global approach to sharing custom properties and include the Glossary file in there.

  Best regards