atlas-bi / library Goto Github PK

• I've searched the issues
• I've read the docs

Feature Request

• Update Analytics
• Update user profiles
• Update Report/collection/term profiles

• I've searched the issues
• I've read the docs

Feature Request

Options should be added to the appsettings.json file or as security points to enable/disable app features.

• Demo video
• Access request buttons
• Feedback buttons
• Terms
• Initiatives
• Relationships
• Comments
• User profiles

allow text changes

• GitlabURL and View source on report documentation

currently limited to numbers, it would be useful to allow alpha chars as well for different id schemes.

Split favorites db table into a table per favorite type so that we can use fk's to quickly link favorites.

• I've searched the issues
• I've read the docs

Feature Request

Change from db first to code first so we can run migrations to update the database when deploying new versions.

Also, clean up db table names.

Potential Updates

ReportGroupsMemberships

• table ReportGroupsMemberships > ReportGroupMemberships
• col MembershipId > membership_id
• col GroupId > group (fk)
• col ReportId > report (fk)
• col LastLoadDate > etl_date

ReportObject

• table ReportObject > Reports
• col ReportObjectID > report_id
• col ReportObjectBizKey > report_key
• col ReportObjectTypeID > type
• col Name > name
• col DisplayTitle > title
• col Description > description
• col DetailedDescription > detailed_description
• col RepositoryDescription > system_description
• col SourceServer > system_server
• col SourceDB > system_db
• col SourceTable > system_table
• col AuthorUserID > created_by
• col LastModifiedByUserID > modified_by
• col LastModifiedDate > _modified_at
• col ReportObjectURL > url
• col EpicMasterFile > system_identifier
• col EpicRecordID > system_id
• col EpicReportTemplateId > system_template_id
• col ReportServerCatalogID > system_catalog_id
• col DefaultVisibilityYN > visible
• col OrphanedReportObjectYN > orphan
• col ReportServerPath > system_path
• col LastLoadDate > etl_date
• col CertificationTag > certification_tag

ReportObjectHierarchy

• table ReportObjectHierarchy > ReportHierarchies
• col ParentReportObjectID > parent
• col ChildReportObjectID > child
• col Line > rank
• col LastLoadDate > etl_date

ReportObjectQuery

• table ReportObjectQuery > ReportQueries
• col ReportObjectQueryId > query_id
• col ReportObjectId > report_id
• col Query > query
• col LastLoadDate > etl_date

ReportObjectRunData

• table ReportObjectRunData > ReportRuns
• col ReportObjectID > report_id
• col RunID > run_id
• col RunUserID > user
• col RunStartTime > start_time
• col RunDurationSeconds > duration_seconds
• col RunStatus > status
• col LastLoadDate > etl_date

ReportObjectSubscriptions

• table ReportObjectSubscriptions > ReportSubscriptions
• col ReportObjectSubscriptionsId > subscriptions_id
• col ReportObjectId > report
• col UserId > user_id
• col SubscriptionId > unique_id
• col InactiveFlags > inactive
• col EmailList > email_list
• col Description > description
• col LastStatus > status
• col LastRunTime > last_run
• col SubscriptionTo > email
• col LastLoadDate > etl_date

ReportObjectType

• table ReportObjectType > ReportTypes
• col ReportObjectTypeID > type_id
• col Name > name
• col ShortName > short_name
• col DefaultEpicMasterFile > code
• col LastLoadDate > etl_date

User

• table User > Users
• col UserID > user_id
• col Username > username
• col EmployeeID > employee_id
• col AccountName > account_name
• col DisplayName > display_name
• col FullName > _full_name
• col FirstName > _first_name
• col LastName > last_name
• col Department > department
• col Title > title
• col Phone > phone
• col Email > email
• col Base > base
• col EpicId > system_id
• col LastLoadDate > etl_date
• col LastLogin > last_login

Analytics

• table Analytics > Analytics
• col Id > analytics_id
• col Username > username
• col appCodeName > app_code_name
• col appName > app_name
• col appVersion > app_version
• col cookieEnabled > cookie_enabled
• col language
• col oscpu
• col platform
• col userAgent > useragent
• col host
• col hostname
• col href
• col protocol
• col search
• col pathname
• col hash > unique_id
• col screenHeight > screen_height
• col screenWidth > screen_width
• col origin
• col title
• col loadTime > load_time
• col accessDateTime > access_date
• col referrer
• col UserId > user
• col Zoom > zoom
• col Epic > epic
• col pageId > page_id
• col sessionId > session_id
• col pageTime > page_time
• col sessionTime > session_time
• col updateTime > update_time

DP_Agreement

• table DP_Agreement > drop table

DP_AgreementUsers

• table DP_AgreementUsers > drop table

DP_Attachments

• table DP_Attachments > drop table

DP_Contact

• table DP_Contact > drop table

DP_Contact_Links

• table DP_Contact_Links > drop table

DP_DataInitiative

• table DP_DataInitiative > Initiatives
• col DataInitiativeID> initiative_id
• col Name> name
• col Description> description
• col OperationOwnerID> ops_owner
• col ExecutiveOwnerID> exec_owner
• col FinancialImpact> financial_impact
• col StrategicImportance> strategic_importance
• col LastUpdateDate> _modified_at
• col LastUpdateUser> modified_by

DP_DataProject

• table DP_DataProject > Collections
• col DataProjectID> collection_id
• col DataInitiativeID> initiative
• col Name> name
• col Purpose> search_summary
• col Description> description
• col LastUpdateDate> _modified_at
• col LastUpdateUser> modified_by
• col Hidden> hidden

DP_MilestoneChecklist

• table DP_MilestoneChecklist > drop table

DP_MilestoneFrequency

• table DP_MilestoneFrequency > drop table

DP_MilestoneTasks

• table DP_MilestoneTasks > drop table

DP_MilestoneTasksCompleted

• table DP_MilestoneTasksCompleted > drop table

DP_MilestoneTemplates

• table DP_MilestoneTemplates > drop table

DP_ReportAnnotation

• table DP_ReportAnnotation > CollectionReport
• col ReportAnnotationID> link_id
• col ReportId> report
• col DataProjectId> collection
• col Rank> drop

DP_TermAnnotation

• table DP_TermAnnotation > CollectionTerm
• col TermAnnotationID> link_id
• col TermId> term
• col DataProjectId > collection
• col Rank > rank

Dp_DataProjectConversation

• table Dp_DataProjectConversation > drop table

Dp_DataProjectConversationMessage

• table Dp_DataProjectConversationMessage > drop table

EstimatedRunFrequency

• table EstimatedRunFrequency > RunFrequency
• col EstimatedRunFrequencyID > frequency_id
• col EstimatedRunFrequencyName > name

FinancialImpact

• table FinancialImpact > FinancialImpact
• col FinancialImpactId > impact_id
• col Name > name

Fragility

• table Fragility > Fragility
• col FragilityID > fragility_id
• col FragilityName > name

FragilityTag

• table FragilityTag > FragilityTag
• col FragilityTagID > tag_id
• col FragilityTagName > name

MaintenanceLog

• table MaintenanceLog > MaintenanceLogs
• col MaintenanceLogID > log_id
• col MaintainerID > maintainer
• col MaintenanceDate > maintained_at
• col Comment > comments
• col MaintenanceLogStatusID > status

MaintenanceLogStatus

• table MaintenanceLogStatus > MaintenanceLogStatus
• col MaintenanceLogStatusID > status_id
• col MaintenanceLogStatusName > name

MaintenanceSchedule

• table MaintenanceSchedule > MaintenanceSchedule
• col MaintenanceScheduleID > schedule_id
• col MaintenanceScheduleName > name

OrganizationalValue

• table OrganizationalValue > OrganizationalValue
• col OrganizationalValueID > value_id
• col OrganizationalValueName > name

ReportManageEngineTickets

• table ReportManageEngineTickets > ReportTickets
• col ManageEngineTicketsId > ticket_id
• col TicketNumber > number
• col Description > description
• col ReportObjectId > report_id
• col TicketUrl > ticketurl

ReportObjectConversation_doc

• table ReportObjectConversation_doc > drop table

ReportObjectConversationMessage_doc

• table ReportObjectConversationMessage_doc > drop table

ReportObjectDocFragilityTags

• table ReportObjectDocFragilityTags > ReportFragilityTags
• col LinkId > link_id
• col ReportObjectID > report
• col FragilityTagID > fragility_tag

ReportObjectDocMaintenanceLogs

• table ReportObjectDocMaintenanceLogs > ReportMaintenanceLogs
• col LinkId > link_id
• col ReportObjectID > report
• col MaintenanceLogID > log

ReportObjectDocTerms

• table ReportObjectDocTerms > ReportTerms
• col LinkId > link_id
• col ReportObjectID > report_doc
• col TermId > term

ReportObjectImages_doc

• table ReportObjectImages_doc > ReportImages
• col ImageID > image_id
• col ReportObjectID > report_id
• col ImageOrdinal > image_rank
• col ImageData > image_data
• col ImageSource > image_source

ReportObject_doc

• table ReportObject_doc > ReportDocs
• col OperationalOwnerUserID > ops_owner
• col Requester > requester
• col GitLabProjectURL > collection_url
• col DeveloperDescription > description
• col KeyAssumptions > assumptions
• col OrganizationalValueID > org_value
• col EstimatedRunFrequencyID > frequency
• col FragilityID > fragility
• col ExecutiveVisibilityYN > executive_report
• col MaintenanceScheduleID > maintenance_schedule
• col LastUpdateDateTime > _modified_at
• col CreatedDateTime > _created_at
• col CreatedBy > created_by
• col UpdatedBy > modified_by
• col EnabledForHyperspace > enabled_for_hyperspace
• col DoNotPurge > do_not_purge
• col Hidden > hidden
• col ReportObjectID > report

RolePermissionLinks

• table RolePermissionLinks > RolePermissionLinks
• col RolePermissionLinksId > permissionlinks_id
• col RoleId > role_id (pk)
• col RolePermissions > permission_id (pk)

RolePermissions

• table RolePermissions > RolePermissions
• col RolePermissionsId > permissions_id
• col Name > name
• col Description > description

StrategicImportance

• table StrategicImportance > StrategicImportance
• col StrategicImportanceId > importance_id
• col Name > name

Term

• table Term > Terms
• col TermId > term_id
• col Name > name
• col Summary > summary
• col TechnicalDefinition > technical_definition
• col ApprovedYN > approved
• col ApprovalDateTime > _approved_at
• col ApprovedByUserId > approved_by (fk)
• col ExternalStandardUrl > external_standard_url
• col ValidFromDateTime > _valid_from
• col ValidToDateTime > _valid_to
• col UpdatedByUserId > modified_by (fk)
• col LastUpdatedDateTime > _modified_at

TermConversation

• table TermConversation > drop table

TermConversationMessage

• table TermConversationMessage > drop table

UserFavoriteFolders

• table UserFavoriteFolders > FavoriteFolders
• col UserFavoriteFolderId > folder_id
• col FolderName > name
• col favorite_folders > user (fk)
• col FolderRank > rank

UserFavorites

• table UserFavorites > Favorites
• col UserFavoritesId > favorite_id
• col ItemType > item_type
• col ItemRank > rank
• col ItemId > item_id
• col UserId > user (fk)
• col ItemName > name
• col FolderId > folder = (fk)

UserPreferences

• table UserPreferences > UserPreferences
• col UserPreferenceId > preference_id
• col ItemType > key
• col ItemValue > value
• col ItemId > item_id
• col UserId > user_id (fk)

UserRoleLinks

• table UserRoleLinks > UserRolelinks
• col UserRoleLinksId > rolelinks_id
• col UserId > user (fk)
• col UserRolesId > role (fk)

UserRoles

• table UserRoles > UserRoles
• col UserRolesId > role_id
• col Name > name
• col Description > description

• I've searched the issues
• I've read the docs

Feature Request

It would be nice to have a welcome message for first-time visitors.

Little snowflakes and stuff, reindeers, fireworks on the 4th of July, etc etc, REALLY MAKE IT POP!

• I've searched the issues
• I've read the docs

Feature Request

Some report items are children that cannot be run - subcomponents etc. When a user is viewing one of these we should show the run url for the next runnable parent.

• I've searched the issues
• I've read the docs

Feature Request

Add the option for access control points to be assigned to groups that have been ETL'd in.

• I've searched the issues
• I've read the docs

Feature Request

When searching for users, the search works too well :) We find users who have no activity at the top when there is a closer match on them. We should try to do a bit of rank boosting using the quantity of report runs/atlas usage. Big users should be closer to the top.

For example, searching for the analytics directory... we get 10 matches, but he is on the bottom. He should be on the top based on usage... and employees who have left the company and have 0 usage should be closer to the bottom.

• I'm on the latest version
• I've searched the issues
• I've read the docs

Issue

The send button from the share form is missing.

• I've searched the issues
• I've read the docs

Feature Request

Enhance site wide messages to enable multiple messages.

• I've searched the issues
• I've read the docs

Feature Request

It would be nice to be able to reorder the attached images on report documentation to choose which image displays first.

atlas-test bug

Issue

SQL queries are not formatted. No line breaks, just wrapped text.

How To Reproduce

Look at a query

Table is currently joined to reportobject, but should be joined to reportobjectdoc.

Issue

Adding multiple service tickets to report documentation results in duplicates being added.

• I've searched the issues
• I've read the docs

Feature Request

Would ultimately replace any public/hidden classification in ETL. Admin users should be able to go by Report Object Type and classify both globally as public/hidden and and criteria to determine public/hidden. Criteria should include:

Run quantity threshold
Last run date
Custom column criteria
group membership of run users
group membership of report object (report group, inherited users)
Is Private Report for workbench

Remove unused db columns on reportobjectdoc:

• gitlabbloburl
• gitlabtreeurl

• I'm on the latest version
• I've searched the issues
• I've read the docs

System Info

• Browser: IE 11
• OS: Windows 10

Issue

Got into Atlas to update the documentation on this report.
Clicked on Images. Deleted one image and saved a new one.
Then I got this error.

atlas-test issue

Issue

quoted exact string matching does not work for strings with underscore.

How To Reproduce

Search for EE_LIST. Should match to several not visible reports.

This for atlas-test

Issue

screenshots do not render on collections page

How To Reproduce

See the CT Reporting collection as an example. Changed Orders should have a screenshot.

Should help improve load times on reports with many images.

There is an extra layer of foreign keys between the maintenance logs and the docs table. We can join directory and get rid of the middle man to simplify things a bit.

• I've searched the issues
• I've read the docs

Feature Request

Before running a workbench report, check that the report belongs to the users groups.

Right now if someone enters "hyperspace mode" outside of hyperspace they have now way of leaving it, other than clearing their cookie cache.

If we have the hyperspace cookie set, but no longer detect hyperspace, we should probably show an option for them to exit hyperspace mode.

some browsers are caching the search results too long and showing old/changed data such as missing images.

• I've searched the issues
• I've read the docs

Feature Request

Add a way to find/filter favorites, either through the main search, or filtering on favorites.

• I've searched the issues
• I've read the docs

Feature Request

The feature didn't catch on as expected and will be killed in the next release.

• I'm on the latest version
• I've searched the issues
• I've read the docs

System Info

• Browser: e.g. IE 11
• OS: e.g. Windows 95

Issue

How To Reproduce

and you can no longer type

these fields should joint to user_namedata to take advantage of the nicely formatted usernames.

• I've searched the issues
• I've read the docs

Feature Request

Being able to use quotes in the search to do exact matches would be cool!

Issue

Probably a caching issue on the fav page?

All doc items are currently linking to reportobjectdoc table, except ReportObjectImagesDocs and ReportManageEngineTickets.

Terms are also linked to reportobjectdoc while collections are linked directly to reportobject.

• I'm on the latest version
• I've searched the issues
• I've read the docs

System Info

• Browser: e.g. IE 11
• OS: e.g. Windows 95

Issue

How To Reproduce

• I've searched the issues
• I've read the docs

Feature Request

We'd like to move the logic used to calculate the certification tags into the web app settings so admins can tweak the setting on the fly.

Issue

• I've searched the issues
• I've read the docs

Feature Request

It would be nice to have some editable space on some of the static pages.

• Analytics page - so custom html can be included
• About page
• 404 page

• I've searched the issues
• I've read the docs

Feature Request

User should be able to have "pre-parameterized" links to reports, either on their profile, or even on the report they are trying to run.

This could be based on the users run history.
Get run params from runs > 2 in last x days and build a url? Add to favs somewhere?
List of "common parameter sets" can we infer param sets from ssrs history? get exact run links from history and let people fav them
pull SSRS params into Atlas, let users customize params in Atlas, then build a run link w/ them.

• I'm on the latest version
• I've searched the issues
• I've read the docs

Issue

Changing roles (admin > user etc) from a report does not open the report with the new role until the local cache is cleared. Changing roles from the home page seems to work fine.

• I've searched the issues
• I've read the docs

Feature Request

It would be nice for shared items to also show up in email. We should have a notifications section on user profiles to enable/disable.

• I'm on the latest version
• I've searched the issues
• I've read the docs
  Instead of report name it has the search url.

• I've searched the issues
• I've read the docs

Feature Request

Add a dev notes section for documentation entries, and add security point to show/hide.

• I've searched the issues
• I've read the docs

Feature Request

It would be nice to have the option to manually add reports that cannot be ETL'd for whatever reason. Also we should be able to add hierarchy to manually created reports.

• I've searched the issues
• I've read the docs

Feature Request

This can probably be done with a "custom" sass file that users can add. It should probably be in a gitignored folder that can also contain custom fonts etc.

• I've searched the issues
• I've read the docs

Feature Request

Can spell check be added to code mirror to underline spelling errors as we type?

• I'm on the latest version
• I've searched the issues
• I've read the docs

Issue

Orphaned reports should not show any system action urls.... if the urls were still valid the report would not be an orphan.