As aData Administrator, I wantto be able to define a resource that isn't a file or URL so thatI don't have to a specify dummy link (e.g., the "faq" resource) when defining, for example, a not downloadable BCGW table/view.
In the current BC Data Catalogue, resources cannot be added unless you upload a file or specify a URL. This means that in order to add a BCGW table or view as a resource it either has to be downloadable (it has an OFI link) or we have to associate it with the dummy "FAQ" URL (http://apps.gov.bc.ca/notice/edc/faq/). (See for example this record). This is bad UX - the user navigates to a resource in order to access it and is then told they can't. Some non-downloadable tables/views have Catalogue records that have no resources defined. This isn't good either, as we should define a resource where we can describe the table or view, even if it is not downloadable (such as supplying the last refresh date value).
This issue could easily be fixed by removing the restriction that a resource has to be either an uploaded file or a URL.
@mdunhamwilkie commented on Tue Sep 01 2020
User Story
As a Data Administrator,
I want to be able to define a resource that isn't a file or URL
so that I don't have to a specify dummy link (e.g., the "faq" resource) when defining, for example, a not downloadable BCGW table/view.
In the current BC Data Catalogue, resources cannot be added unless you upload a file or specify a URL. This means that in order to add a BCGW table or view as a resource it either has to be downloadable (it has an OFI link) or we have to associate it with the dummy "FAQ" URL (http://apps.gov.bc.ca/notice/edc/faq/). (See for example this record). This is bad UX - the user navigates to a resource in order to access it and is then told they can't. Some non-downloadable tables/views have Catalogue records that have no resources defined. This isn't good either, as we should define a resource where we can describe the table or view, even if it is not downloadable (such as supplying the last refresh date value).
This issue could easily be fixed by removing the restriction that a resource has to be either an uploaded file or a URL.