item: #1 of 9
          id: addrakatti-fast-2023
      author: addrakatti
       title: addrakatti-fast-2023
        date: 2023
       words: 2365
      flesch: 48
     summary: The students access published lecture videos independent of time and location. Lecture videos and MOOCs are hosted on cloud platforms to make them available to registered users.
    keywords: access; admin; application; audio; based; cbmir; content; engine; extraction; fast; figure; file; indexing; information; institutions; issue; learning; lecture; library; metadata; module; ocr; online; platforms; popular; python; repositories; research; retrieval; search; source; speech; storage; text; time; user; video
       cache: addrakatti-fast-2023.html
  plain text: addrakatti-fast-2023.txt

        item: #2 of 9
          id: bradley-creating-2023
      author: bradley
       title: bradley-creating-2023
        date: 2023
       words: 5060
      flesch: 46
     summary: Git was already part of the workflow for development of the app, and we had used git pulls as a way of deploying other apps, such as the aforementioned feedback kiosks, so this seemed like a reliable solution here as well. When clicked, the app is opened in the default browser, and the user can go about managing queue functions as normal.
    keywords: api; app; application; build; code; computer; data; database; delete; deployment; design; development; dreamfactory; electron; export; figure; file; folder; form; functions; job; key; label; libraries; machine; multiple; need; new; options; patron; print; process; project; prototyping; queue; queueing; react; select; server; service; single; structure; student; studio; system; text; time; type; university; user; value; version; web
       cache: bradley-creating-2023.html
  plain text: bradley-creating-2023.txt

        item: #3 of 9
          id: eaton-drying-2023
      author: eaton
       title: eaton-drying-2023
        date: 2023
       words: 2816
      flesch: 61
     summary: <i v-bind:class=item.icon aria-hidden=true></i> <strong>{{ item.description }}</strong> </div>`, props: ['item'] } And the Vue constructor: new Vue({ el: '#app', components: { 'menus-component': menusComponent … }, data() { return { hamburger: We tested this proposed approach ahead of time, by implementing Vue’s v-for directive on the web librarian’s personal projects page.
    keywords: aria; bigger; class="highlight; class="searchmenu; code; div; dry; fancy; hand; hidden="true"></i; html; icon; id="hamburger; issue; item; javascript; libguides; library; menu; new; page; project; site; strong; text; use; vue; way; webpage; work
       cache: eaton-drying-2023.html
  plain text: eaton-drying-2023.txt

        item: #4 of 9
          id: heng-revamping-2023
      author: heng
       title: heng-revamping-2023
        date: 2023
       words: 6345
      flesch: 52
     summary: The Code4Lib Journal – Revamping Metadata Maker for ‘Linked Data Editor’: Thinking Out Loud Mission Editorial Committee Process and Structure Code4Lib Issue 55, 2023-1-20 Revamping Metadata Maker for ‘Linked Data Editor’: Thinking Out Loud With the development of linked data technologies and launch of the Bibliographic Framework Initiative (BIBFRAME), the library community has conducted several experiments to design and build linked data editors. Specifically, there are two expectations for the name entity search function in linked data editors: (1) no restraints on the order of a name; and (2) supporting variant name searching.
    keywords: /bf; annif; api; application; authority; authors; auto; bibframe; bibframe data; bibliographic; catalogers; cataloging; congress; copy; creation; data; data editor; description; development; different; editors; figure; function; han; hard; information; input; interface; issue; john; json; knowledge; label; language; lcnaf; lcsh; level; libraries; library; maker; marc; metadata; metadata maker; names; national; need; new; non; notation; oclc; paraprofessional; participants; paul; personal; production; rda; rdf; records; resources; score; search; sinopia; skills; source; subject; suggest; terms; tool; uri; uris; use; users; var; viaf; web; work
       cache: heng-revamping-2023.html
  plain text: heng-revamping-2023.txt

        item: #5 of 9
          id: lou-using-2023
      author: lou
       title: lou-using-2023
        date: 2023
       words: 2011
      flesch: 54
     summary: However, this is not a perfect solution, and over time a problem with record discrepancies can become severe with thousands of records out of sync. This reduced the cataloging effort eventually needed to fix record discrepancies. Figure VI.
    keywords: analysis; author; column; cutoff; data; dataframe; discrepancies; fields; figure; file; function; google; ils; isbn; issue; library; marc; new; numbers; online; overdrive; pandas; python; records; sierra; similarity; title; vendors
       cache: lou-using-2023.html
  plain text: lou-using-2023.txt

        item: #6 of 9
          id: schriner-data-2023
      author: schriner
       title: schriner-data-2023
        date: 2023
       words: 3853
      flesch: 60
     summary: We can now start the training: fairseq-train \ --data-bin \ --source-lang epo.g \ --target-lang epo.p \ --encoder-bidirectional \ --seed {choose a random whole numeral} \ --arch lstm \ --dropout 0.2 \ --lr .001 \ --max-update 800 \ --no-epoch-checkpoints \ --batch-size 3000 \ --clip-norm 1 \ --label-smoothing .1 \ --optimizer adam \ --clip-norm 1 \ --criterion label_smoothed_cross_entropy \ --encoder-embed-dim 128 \ --decoder-embed-dim 128 \ --encoder-layers 1 \ --decoder-layers 1   With these parameters it took my machine[15] a half-hour to train.  i t a ʒ o     The TSV is shuffled using shuf and then split into three TSV files: an 80% training set, a 10% development set, and a 10% test set using a Python script.[14] python3 split.py \ --seed 103 \ --input_path epo.tsv \ --train_path epo_train.tsv \ --dev_path epo_dev.tsv \ --test_path epo_train.tsv   To prepare the data for Fairseq, the important part of the code to note is that each of the three TSV files are then split into .g (for grapheme) and .p (for phoneme) files for training, dev, and test:
    keywords: article; best; characters; code; column; data; different; error; esperanto; example; experiments; fairseq; features; file; information; issue; language; learning; linguistics; machine; model; open; project; pronunciation; research; results; russian; sequence; set; software; source; speech; stress; table; target; test; text; tools; training; tsv; use; wikipron; word
       cache: schriner-data-2023.html
  plain text: schriner-data-2023.txt

        item: #7 of 9
          id: tidal-editorial-2023
      author: tidal
       title: tidal-editorial-2023
        date: 2023
       words: 758
      flesch: 51
     summary: This is my second time and last time as coordinating editor for Code4Lib Journal. The guest editor policy is in place to make it clear to the author, guest editor, and readers, their role in the review process.
    keywords: article; code4lib; committee; editorial; editors; guest; issue; journal; library; policy; process; retraction; review; updates
       cache: tidal-editorial-2023.html
  plain text: tidal-editorial-2023.txt

        item: #8 of 9
          id: weideman-designing-2023
      author: weideman
       title: weideman-designing-2023
        date: 2023
       words: 9219
      flesch: 40
     summary: It offers a custom indexer as a working example that adds the full text of digital content to an Arclight instance and argues that the extensibility of archival description makes it a perfect match for automated description. Implementing these systems requires cross-domain partnerships, and the misunderstandings and miscommunications around archival description in particular have severely hindered the development of discovery and access systems for archives.
    keywords: access; access systems; additional; aids; american; applications; approaches; archival; archival description; archival discovery; archives; archivesspace; archivists; arclight; available; better; bibliographic; bibliographic description; case; challenging; collection; complex; components; content; core; current; dacs; dams; dataset; description; description_indexer; design; detailed; different; digital; digital materials; digital objects; digitization; discovery; discovery systems; early; elements; espy; example; fields; file; finding; folder; higher; hyrax; index; information; issue; item; journal; labor; level; libraries; library; lower; major; materials; metadata; methods; model; national; need; new; objects; online; overall; papers; potential; practice; process; processing; project; quality; records; relationships; repositories; repository; request; research; series; set; single; source; special; stanford; states; systems; text; ualbany; united; university; usability; use; useful; users; value; vol; way; web; work
       cache: weideman-designing-2023.html
  plain text: weideman-designing-2023.txt

        item: #9 of 9
          id: zhang-click-2023
      author: zhang
       title: zhang-click-2023
        date: 2023
       words: 2409
      flesch: 60
     summary: The Code4Lib Journal – Click Tracking with Google Tag Manager for the Primo Discovery Service Mission Editorial Committee Process and Structure Code4Lib Issue 55, 2023-1-20 Click Tracking with Google Tag Manager for the Primo Discovery Service This article introduces practices at the library of Oregon State University aiming to track the usage of Unpaywall links with Google Tag Manager for the Primo discovery interface. This article will detail how to set up Google Tag Manager for tracking the usage of Unpaywall links and creating reports in Google Analytics.
    keywords: access; analytics; articles; click; container; content; discovery; figure; google; google tag; issue; library; links; manager; open; open access; patrons; primo; tag; tag manager; text; tracking; trigger; university; unpaywall; usage; website
       cache: zhang-click-2023.html
  plain text: zhang-click-2023.txt