search

sul-dlss / FOLIO-Project-Stanford

Task management for Stanford’s analysis of FOLIO.
2 stars 0 forks source link

Input vendor connection details in folio organization record #626

Open shelleydoljack opened 7 months ago

shelleydoljack commented 7 months ago

For organizations that already exist in FOLIO, we should maybe create a new interface specific to data export. For the other vendors, we should create organizations. We probably will need a mechanism to match the vendor name used in airflow to the one in FOLIO. For instance, the organization code is YANKEE-SUL but we are calling it "gobi" in airflow.

dlrueda commented 7 months ago

So now, after voting for Gobi before, if we're going to hook to the Folio organization record, I switch my vote to match YANKEE-SUL. If it needs to match the Folio organization name at least.

I assume we'll want a Folio organization "OCLC" and have different interfaces for the different holding codes (STF, etc)?

shelleydoljack commented 7 months ago

There's no easy way to do this. We currently have "vendor" as part of the names of files on the system and in the name of the dag, etc. At this point, I think it will be easier to just have a mapping for them if they are not 1:1, which they won't be. Makes me think though if for OCLC we have a separate one for each "library" since we have to split them into the different OCLC library codes anyways.

ahafele commented 6 months ago

Sorry for a delayed two cents - if a mapping is an OK solution I like keeping the name gobi and moving away from Yankee wherever possible. For OCLC - on the Organization record side I think a different Org record for each "library" makes sense. There will be data imports related to these as well and keeping the org records separate will follow the pattern we have for other vendors. There are already separate ones from Lane, Law, and SUL

ahafele commented 5 months ago

Won't do right now. May consider in the future if need becomes greater.