stephenfuqua
commented
3 weeks ago Jira Comment
This is the first step in creating deliverables for the Analytics project. There are two separate components in this:
Tabular Data Model (Visual Studio Project)
Azure Assets (AAS, Azure Functions, Azure Automation)
We're currently keeping everything in the Ed-Fi-Data-Analytics GitHub repo. I think we should separate the data model into its own repository, and move the Azure pieces to the CODS repo. Changes to the data model don't have any impact on the Azure services. The Azure pieces, on the other hand, tie in directly with the CODS deployment.
On the second point - this depends completely on the release cycle. The Azure components may need to be updated within the same version of CODS - is this considered a 'CODS update' or its own thing?
Similarly, the data model shouldn't be dependent on the version of CODS so much as the version of the ODS Schema, so it should be on its own versioning. This would then require a separate update procedure.
Jira Metadata
Created: 2017-03-23T13:12:04.640-0500 Commenter: Dan Malagari
Jira Description
Two separate items of interest:
Location of PBI assets within source control (i.e. within the Cloud ODS repo, a new repo, elsewhere.)
Location of PBI assets at publication (i.e. in same place as Cloud ODS and therefore versioned the same as Cloud ODS, or separate)
Jira Metadata
Key: BIA-42 Epic: n/a Created: 2017-03-15T14:15:26.000-0500 Reporter: Dean Goodman