You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to check a source against a set of baseline checks would be useful, and to see the results. It would allow end-users to add a source and run some checks to make sure it's valid (or, do it as the source is added). Currently, if you want to check a source, you'll run a search or an installation against it.
We would need to determine what "baseline" means and what checks to perform. As an example, we could:
Check if it's reachable. Is the URL correct?
What type of source is it: v2 oData, v3 JSON, local folder / shared drive, etc.
If authentication is provided, can we authenticate?
Checklist
Is Your Feature Request Related To A Problem? Please describe.
The idea for this came from this comment.
Describe The Solution. Why is it needed?
Being able to check a source against a set of baseline checks would be useful, and to see the results. It would allow end-users to add a source and run some checks to make sure it's valid (or, do it as the source is added). Currently, if you want to check a source, you'll run a search or an installation against it.
We would need to determine what "baseline" means and what checks to perform. As an example, we could:
Additional Context
None.
Related Issues
The text was updated successfully, but these errors were encountered: