Reading an asset
Definition, attributes, who is responsible, links and history.
On this page
Every table, column, business term, domain and report in KRISID has a page of its own. It shows what the asset is, who answers for it, what it is linked to and what has changed. This page goes through the parts of that page from top to bottom.
What you see depends on the kind of asset. The attributes and links come from your repository's metamodel, so a business term and a table show different fields.
The top of the page
- The name, with the type beside it, for example Table or Business Term.
- The key, the identifier KRISID merges on when assets are loaded again. For a harvested asset this is its path in the source, such as
SALES_DB.PUBLIC.ORDERS. - Asset id, the asset's permanent identifier. Press copy to copy it.
- Trace it has two links. Lineage and connections opens the lineage diagram. whole graph in a new tab opens a diagram of everything connected to this asset, at any distance. See Lineage and connections.
Press ← back to return to where you came from.
Notices you may see
A notice under the name tells you something that changes how you read the rest of the page.
- Missing in Source. The last harvest did not find this asset, and the notice says when it was first missed. Nothing has been deleted. The asset changes back to In Source when the source presents it again.
- Read-only for your name. You cannot edit this asset. Editing needs ASSET_EDIT here, and a role held over the asset's data domain would cover it.
- Harvested. The name and key come from the source system, so you cannot edit them here. You can still edit the attributes, responsibilities and links.
- Changes here are proposed, not written. A workflow governs this kind of asset. Each edit you make, to a value, the name, a responsibility or a link, goes into Your change set on this page instead of being saved. When you are done, Submit sends the whole set as one request. A draft stays until you submit or discard it. The notice shows how many requests are already waiting. See Build and submit a change set.
- A proposed type. This asset was proposed and is waiting for approval. Until it is approved, only you, the approvers and administrators can see it, and it is left out of lists, counts and search. Submit for approval sends it if it is still a draft. See A new asset.
Responsible
Responsible lists who answers for the asset. It comes before the attributes because it is usually the first thing people need to know.
| Column | What it tells you |
|---|---|
| Role | The responsibility, such as Data Owner or Data Steward. A locked chip means it was set higher up and cannot be overridden here. |
| Who | The person or team, and which of the two it is. |
| Assigned on | Where the responsibility comes from. A chip naming this asset's type, such as this table, means it was assigned directly on this asset. inherited from names the asset above it that passes it down, such as a schema or a data domain. |
You can only remove a direct responsibility on this page. To change an inherited one, open the asset it was inherited from.
Passes down says what happens to this asset's responsibilities below it. inherit means they flow down and can be overridden. inherit locked means they flow down and cannot be overridden. none means they stop here. (default) means nobody has changed the setting.
If the asset has no responsibilities, the page says that nobody is recorded and nothing above passes anyone down. For how inheritance works and how to assign someone, see Owners, stewards and responsibilities.
Attributes
Attributes lists every field the metamodel gives this type, such as Definition, Status or Classification. A required chip marks a mandatory field. An empty required field shows missing, and other empty fields show a dash.
If you may edit, click a value to change it. See Editing an asset.
Relations
Relations lists what the asset is linked to, grouped by the kind of link, for example This table realises or This column is in. The words depend on your metamodel. Each linked asset is a link to its own page.
- A long group shows the first twelve links. Press show all to see the rest.
- A small label after a link says how it was recorded when a person did not write it, for example parsed from DDL.
- If nothing is linked yet, the page says so.
Lineage from its SQL
Tables and views have a Lineage from its SQL section. Paste a CREATE VIEW statement, or leave the box empty to use the statement harvested with the asset. Then press Read it. KRISID proposes the links it finds. Nothing is saved until you accept them, and accepted links are recorded as read from SQL.
From the source
For a harvested asset, From the source lists what the source system says about it, each as an attribute: for example Description from Source, Owner at Source, Modified By at Source, Created at Source, Changed at Source, Sources, Sensitivity Label, Endorsement, Row Count, Size, Data Type, Nullable, Web URL and Last Run At. Only the ones the source actually sent are shown.
- They are attributes like the ones above them. You can pick them as columns, filter a list on them, search on them and export them.
- They are read-only. Each harvest writes them, and KRISID refuses a change to one from the screen, a workbook or a workflow. To change one, change it in the source and harvest again.
- Your own words go in the attributes above: Description is only ever written by people, and a harvest never fills it in.
Source tags and technical details
- Source tags shows the tags the source system itself puts on the asset. A tag that came from a container shows from and the container's name. They are also the attribute Tags at Source. You cannot change source tags in KRISID. Change them in the source and harvest again.
- Technical details shows everything else the connector records: definitions (DDL), queries, DAX and Power Query expressions, YAML and the connector's own bookkeeping.
What this role can read
On a source role's page, What this role can read shows everything the role can reach. That covers what it was granted, what sits inside those grants, and what the roles it holds were granted. The list is a tree. Columns are folded into their table, and Expand all opens every branch.
History
History lists every change to the asset, newest first and grouped by day. Each line shows the time, who made the change, the field, the old value and the new one. Changes made by a harvest or by KRISID itself name that instead of a person. Press Show earlier changes to load more.
A field that has since been removed from the metamodel is marked no longer in the model.
Good to know
- Opening an asset's page adds it to Recently viewed on the Ask front page.
- An inherited responsibility counts in the same way as a direct one. The Assigned on column shows you where to change it.
- Missing in Source is something the harvest noticed. It is not an error, and you do not need to delete the asset. If you eventually decide it really has gone, you do not have to delete it one at a time either — see Clearing up what has gone.