search

bcgov / MFIN-Data-Catalogue

The Finance Data Catalogue enables users to discover data holdings at the BC Ministry of Finance and offers information and functionality that benefits consumers of data for business purposes. The product is built using Drupal and adheres to the Government of BC's Core Administrative and Descriptive etadata Standard.
Other
6 stars 0 forks source link

field for data asset location/name #352

Closed NicoledeGreef closed 7 months ago

NicoledeGreef commented 8 months ago

https://github.com/bcgov/MFIN-Data-Catalogue/labels/Idea

https://openplus.monday.com/boards/4092908516/pulses/6002168402

User story

As a potential consumer of data, I want to discover specifics about the data asset so that I can locate and use the asset.

Describe the idea

Currently, the content model has elements where the nature of the data asset can be described but a remaining question is: is there value in separating out a placeholder element to store, for example: location and filename OR schema_name.object_name?

We already have a hierarchical taxonomy for record_type in place with Data, Form, and Report at the top level.

image image

Data, for example, allows users to specific whether the assets lives in a file or in a database, and the subtypes of those things. What we don't currently have is a specific placeholder for the filename and location OR the schema/object name. These things can be included in the description (body) of the metadata record but then to be used for any other purpose they would have to be parsed out which is not small feat without some sort of standardized input (body is free form text).

If we stored the name/location of the data asset in one or more fields then it's easy to grab the value when/if needed.

These are field(s) we would want to display for logged in users. They would be irrelevant to public users.

NicoledeGreef commented 8 months ago

To do: figure out the list of likely locations (fileshares, DB name, sharepoint?)

mjmcclung commented 8 months ago

Since this Catalogue is public facing there may be security considerations.

CraigClark commented 8 months ago

Since this Catalogue is public facing there may be security considerations.

Good point. We can control access to the field. Similar to what we do for visibility

mjmcclung commented 8 months ago

I'm not sure we can get as specific as schema_name.object_name in all instances as the catalogue is cataloguing collections of things. These collections may be represented as more than one table in the database (e.g. a collection of tables). A group discussion is needed on this subject before getting too far into planning/implementing.

NicoledeGreef commented 8 months ago

@CraigClark Non-mandatory text area as a placeholder

Section 2 below Summary on the Build page On the Record view, below the Summary

CraigClark commented 7 months ago

@lkmorlan ready for review/merge https://github.com/bcgov/MFIN-Data-Catalogue/tree/352-asset-location

@NicoledeGreef , I added this field to the docs https://dv14.openplus.ca/documentation/metadata-fields#location-01 https://cat.data.fin.gov.bc.ca/documentation/metadata-fields#location-01

CraigClark commented 7 months ago

@NicoledeGreef for now this is just a test area, you can type a location, add a link, that type of thing. This field is not available to the puiblic

lkmorlan commented 7 months ago

Merged

NicoledeGreef commented 7 months ago

verified placement, use, and visibility in dv14