[Agenda] Developers' Setup for Running Scripts

By Derrek Croney
1 min

@Jeffrey Fleming @Zeke Graves @Matthew Harrington @Stewart Engart @Derrek Croney

Scripts / Programs

About the scripts -- what languages are in use:

  • Perl (historic)

  • Java / Javascript / Ruby (previous FOLIO integrations)

  • Ruby

  • Python

Gitlab Repository Location

URL: https://gitlab.oit.duke.edu/dul-its/trln-discovery-ingest

Legacy “Aleph” Perl code:
https://gitlab.oit.duke.edu/aleph/home/-/tree/23_prod/home-slash-aleph?ref_type=heads

FOLIO repository:

https://gitlab.oit.duke.edu/dul-folio

(Abele is still active)

Python
https://gitlab.oit.duke.edu/hse9/folio2alma (courses & licenses)

Ruby
https://gitlab.oit.duke.edu/dul-folio/discovery (discovery .. abandoned)

JavaScript / Angular (Alma widget / cloud apps)

Interest in Moving Some Code to Golang?

Yes – we’ll need to revisit to determine scope of parts where “Go” would be useful?

Concerns about time

Docker

  • (Docker) Containerization: Would we benefit from containerizing the scripts?

Since "Perl" is a thing:

  • NOTE: Use primary as a document reference – see how it’s running, but not to run.

  • What's the minimum version requirement?

  • Would a new developer need to install cpanminus (for module management)? (REVISIT if needed)

    • If "Yes", what additional modules are needed? (could someone create a short list?)

Other Languages/Platforms and Considerations

  • bullet point 1

Next Steps

Related content