Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VMA - need a way to distinguish reused interfaces #1089

Open
ahafele opened this issue Jun 21, 2024 · 0 comments
Open

VMA - need a way to distinguish reused interfaces #1089

ahafele opened this issue Jun 21, 2024 · 0 comments
Labels
enhancement New feature or request vendor load part of flask plugin for vendor load "app"

Comments

@ahafele
Copy link

ahafele commented Jun 21, 2024

This needs technical discussion

FOLIO interfaces are reusable in VMA because we have different vendors that might get their records from the same place, e.g. OCLC worldshare.
Example - https://sul-libsys-airflow-prod.stanford.edu/vendor_management/vendors/1371
Ebsco will continue to add interfaces that will have distinct filename patterns.

Can the interface be renamed in VMA after adding? Or can we enable tags in the UI?
Enabling tags might also solve other issues reported
e.g. linking an interface to a JIRA ticket, "starring" most used interfaces for a particular user

@ahafele ahafele added enhancement New feature or request question Further information is requested vendor load part of flask plugin for vendor load "app" labels Jun 21, 2024
@ahafele ahafele removed the question Further information is requested label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request vendor load part of flask plugin for vendor load "app"
Projects
None yet
Development

No branches or pull requests

1 participant