Data warehouse schema description
I am trying to write reports for RTC2.0. Have looked at the data warehouse schema.
Unfortunately the schema basically talks about different snapshots, the 'tables' therein and the fields of the table. There is no write up or description on what the fields mean, or how everything fits together.
This makes writing reports a frustrating exercise and takes much longer than should be the case.
Is there some better description of the schema somewhere?
Many thanks.
Unfortunately the schema basically talks about different snapshots, the 'tables' therein and the fields of the table. There is no write up or description on what the fields mean, or how everything fits together.
This makes writing reports a frustrating exercise and takes much longer than should be the case.
Is there some better description of the schema somewhere?
Many thanks.
3 answers
On 9/15/2009 10:38 AM, ltsao wrote:
In the specific case you mention, when you define work item enumerations
in the process configuration tab, you give the enumeration an id - that
is reflected in Enumeration_Id. Also, when defining an enumeration, each
literal in the enumeration gets an id and a human-readable name. Those
are reflected in Literal_Id and Literal_Name, respectively.
Hope this helps.
james
RTC Reports Team Lead
rjaouaniwrote:
The following WIKI topic describes the schema.
https://jazz.net/wiki/bin/view/Main/DataWarehouseSnapshotSchemas20
Thanks for the link. I have seen this, that's why the original post.
Take 'enumerations' for example, it is described in the schema as
Logical Name Type Description
Project_Area_Itemid UUID The UUID of the project area in which the
enumeration is defined.
Enumeration_Id String The id of the enumeration
Literal_Id String The id of an enumeration entry
Literal_Name String The human-readable name of an enumeration
entry
Now, there are 2 X_Id fields, how are they used. This is just one of
many examples.
Just wondering if there is a more 'user friendly' description of how
the fields are used and how they are referenced.
Many thanks.
In the specific case you mention, when you define work item enumerations
in the process configuration tab, you give the enumeration an id - that
is reflected in Enumeration_Id. Also, when defining an enumeration, each
literal in the enumeration gets an id and a human-readable name. Those
are reflected in Literal_Id and Literal_Name, respectively.
Hope this helps.
james
RTC Reports Team Lead
The following WIKI topic describes the schema.
https://jazz.net/wiki/bin/view/Main/DataWarehouseSnapshotSchemas20
Thanks for the link. I have seen this, that's why the original post. Take 'enumerations' for example, it is described in the schema as
Logical Name Type Description
Project_Area_Itemid UUID The UUID of the project area in which the enumeration is defined.
Enumeration_Id String The id of the enumeration
Literal_Id String The id of an enumeration entry
Literal_Name String The human-readable name of an enumeration entry
Now, there are 2 X_Id fields, how are they used. This is just one of many examples.
Just wondering if there is a more 'user friendly' description of how the fields are used and how they are referenced.
Many thanks.