Timeframe: April-2023 through March-2024.
On this page...
| """ | |
| To add to server run_tests to ensure xmlcatalog is properly configured, and properly being called. | |
| A MODS file likely be the best candidate for the `xml_filepath`. | |
| """ | |
| import os | |
| from lxml import etree | |
| def validate_xml_with_schema( xml_filepath: str, xsd_filepath: str ) -> None: |
Timeframe: April-2023 through March-2024.
On this page...
(vacation-day experimentation)
(i posted an abbreviated version of this question to [Nim-Discord])
I've been experimenting with nim and am really enjoying it.
Now I want to get compile a binary to run on a Red Hat 7.9 server, and haven't gotten that to work, and would love a few links to some favorite writeups.
Some info, in case it's useful:
| ## ------------------------------------------------------------------ | |
| ## birkin config | |
| ## ------------------------------------------------------------------ | |
| ## aliases ---------------------------------------------------------- | |
| alias cp="cp -i" | |
| alias ls="ls -ahlF" | |
| alias mv="mv -i" | |
| alias rm="rm -i" |
| <record> | |
| <leader>01226nam a2200313Ia 4500</leader> | |
| <controlfield tag="005">20080522191149.0</controlfield> | |
| <controlfield tag="008">050630s2005 nyu 000 1 eng</controlfield> | |
| <controlfield tag="001">991003874639706966</controlfield> | |
| <datafield tag="010" ind1="" ind2=""> | |
| <subfield code="a">2005018927</subfield> | |
| </datafield> | |
| <datafield tag="020" ind1="" ind2=""> | |
| <subfield code="a">0811215881 (alk. paper)</subfield> |
| <mods:mods xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/mods/v3/mods-3-7.xsd"> | |
| <mods:titleInfo> | |
| <mods:title>Time Magazine, Inc.</mods:title> | |
| </mods:titleInfo> | |
| <mods:name type="personal" authority="naf" valueURI="http://id.loc.gov/authorities/names/n50048448" authorityURI="http://id.loc.gov/authorities/names.html"> | |
| <mods:namePart>Luce, Henry R.</mods:namePart> | |
| <mods:namePart type="date">1898-1967</mods:namePart> | |
| <mods:role> | |
| <mods:roleTerm type="text" authority="marcrelator">founder</mods:roleTerm> | |
| </mods:role> |
| <mods:mods xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/mods/v3/mods-3-7.xsd"> | |
| <mods:titleInfo> | |
| <mods:title>American Mercury records -- HH020005_0001</mods:title> | |
| </mods:titleInfo> | |
| <mods:typeOfResource authority="primo" authorityURI="https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/100Loading_Records_from_External_Sources_into_Primo_VE/Configuring_Normalization_Rules_for_External_Resources_(Primo_VE)#Supported_Resource_Types_in_Primo_VE">text_resources</mods:typeOfResource> | |
| <mods:note type="preferredcitation">Item of "American Mercury records, The Gordon Hall and Grace Hoag Collection of Extremist and Dissenting Printed Propaganda, Ms.76.23, Brown University Library"</mods:note> | |
| <mods:language> | |
| <mods:languageTerm type="code" authority="iso639-2b">eng</mods:languageTerm> | |
| <mods:languageTer |
| #!/bin/bash | |
| function usage() { | |
| echo "Usage: $(basename "${0}") <full path to repo directory>" | |
| echo | |
| echo "Example: $(basename "${0}") /path/to/github_project_dir" | |
| exit | |
| } |
Just read a great post from long-time code4libber Jonathan Rochkind, [OCFL and “source of truth” — two options][truth].
To give a nutshell summary, it's first useful to be aware of a common web-development pattern, where the 'data' returned by a browser-request comes from an index. That index is an intermediary between the actual source data/file/image, and the webpage a user loads.
Think of the ["Inscriptions of Israel and Palestine" project][IIP] or the ["U.S. Epigraphy" project][USEP]. In both cases, the source-truth of the scholarly data is in xml-files ([example][usep-example]). Knowedgeable trained folk encode data from headstones or other sources into these xml-files.
But when a user performs a search, or loads an inscription-page from the website, the server looks up info from our [solr][solr] indexer.