Startrekzky commented on code in PR #552: URL: https://github.com/apache/incubator-devlake-website/pull/552#discussion_r1229438386
########## docs/Overview/KeyConcepts.md: ########## @@ -45,12 +45,10 @@ DevLake normally uses one [data plugin](#data-plugins) to pull data for a single You can set up a new data connection either during the first step of creating a blueprint, or in the Connections page that can be accessed from the navigation bar. Because one single data connection can be reused in multiple blueprints, you can update the information of a particular data connection in Connections, to ensure all its associated blueprints will run properly. For example, you may want to update your GitHub token in a data connection if it goes expired. -### Data Scope -**In a blueprint, each data connection can have multiple sets of data scope configurations, including GitHub or GitLab projects, Jira boards and their corresponding [data entities](#data-entities).** The fields for data scope configuration vary according to different data sources. +### Data Scopes +**A data connection can have multiple data scopes. The term "data scope" refers to the top-level entity that a Data Source uses to isolate different groups of data. e.g. Boards on JIRA, Repository on GitHub or Projects on GitLab.** The fields for data scope configuration vary according to different data sources. Review Comment: Suggestion: You can add multiple data scopes to a data connection. A data scope determines what data to collect. Data scopes vary for different data sources. For example, a data scope for Jira is a Jira board. The same goes for TAPD workspaces, GitHub/GitLab/BitBucket repos, Jenkins jobs, etc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
