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
Staff will use a UI in airflow to upload a file of instance UUID's that they want to add 979 fields to. The upload form should present the user with a list of available bookplate fund metadata to add to records in FOLIO. This is what that form looks like in libsys-webforms:
The upload form will trigger the add 979 field DAG. We have a pattern for this interaction with the boundwiths form. We should also keep track of the user who submitted the form so that they can be emailed when the add 979 field DAG is complete. The email should also go to sul-unicorn-devs list and [email protected] (confirm Tech Services still uses this list).
The text was updated successfully, but these errors were encountered:
When there is no fund_name for the bookplate, in the form we previously used, we would use "ZZ_NO_FUND" as the fund name, see screenshot:
We should maybe do something similar. We used "ZZ_" because then those would sort at the bottom. Maybe it doesn't matter with whatever data table we use to present the information. The column for "Fund name" could be blank for these since I think users might search by the title anyways (and not ZZ_NO) in order to find the bookplate for the gift funds, etc.
When the form is submitted, an email of the submission should go to sul-unicorn-devs, sul_bulk_bookplates list and whatever email was entered in the form. The body of the email should be similar to the boundwiths email, in that it includes the filename and a link to a download page. (see #1270)
Staff will use a UI in airflow to upload a file of instance UUID's that they want to add 979 fields to. The upload form should present the user with a list of available bookplate fund metadata to add to records in FOLIO. This is what that form looks like in libsys-webforms:
The upload form will trigger the add 979 field DAG. We have a pattern for this interaction with the boundwiths form. We should also keep track of the user who submitted the form so that they can be emailed when the add 979 field DAG is complete. The email should also go to sul-unicorn-devs list and [email protected] (confirm Tech Services still uses this list).
The text was updated successfully, but these errors were encountered: