58,932 research outputs found
alan-turing-institute/uatk-spc: v2.0.0
No full text<h2>SPC v2.0.0</h2>
<p>Released 09/03/2023 with <a href="https://github.com/alan-turing-institute/uatk-spc/blob/f550a323afadd03bd3bfdd797b66ff2276a2a6d5/synthpop.proto">schema</a>.</p>
<ul>
<li>New per-person and per-household fields</li>
<li>Various changes to existing fields (adjusting enum number, removing the BMI enum, etc)</li>
<li>Adding time-use diaries</li>
<li>Expanding to Wales</li>
<li>Adding multiple years of output</li>
</ul>
<h2>What's Changed</h2>
<ul>
<li>Add the new BMI field. by @dabreegster in https://github.com/alan-turing-institute/uatk-spc/pull/38</li>
<li>Switch to proto2 by @dabreegster in https://github.com/alan-turing-institute/uatk-spc/pull/43</li>
<li>Start a web app to visualize SPC output by @dabreegster in https://github.com/alan-turing-institute/uatk-spc/pull/44</li>
<li>SPC v2 by @dabreegster in https://github.com/alan-turing-institute/uatk-spc/pull/48</li>
</ul>
<p><strong>Full Changelog</strong>: https://github.com/alan-turing-institute/uatk-spc/compare/v1.1...v2.0.0</p>
alan-turing-institute/uatk-spc: v2.1.0
No full text<h1>Release notes</h1>
<p>Released 25/07/2023 with <a href="https://github.com/alan-turing-institute/uatk-spc/blob/f550a323afadd03bd3bfdd797b66ff2276a2a6d5/synthpop.proto">schema</a>.</p>
<ul>
<li>Expanding to Scotland</li>
<li>Adding special area: Oxford-Cambridge arc</li>
<li>Adding previously missing LADs to their counties:<ul>
<li>Greater London (E09000001)</li>
<li>Cornwall (E06000053)</li>
<li>Dorset (E06000058 & E06000059)</li>
<li>Buckinghamshire (E06000060)</li>
<li>Leicestershire (E07000135)</li>
<li>Suffolk (E07000244 & E07000245)</li>
<li>Somerset (E07000246)</li>
</ul>
</li>
</ul>
<h2>What's Changed</h2>
<ul>
<li>Some minor updates for Docs and Main site for the AIUK app by @mfbenitezp in https://github.com/alan-turing-institute/uatk-spc/pull/50</li>
<li>Make proto output deterministic by @sgreenbury in https://github.com/alan-turing-institute/uatk-spc/pull/54</li>
<li>Fix special areas by @sgreenbury in https://github.com/alan-turing-institute/uatk-spc/pull/59</li>
<li>Release v2.1 by @sgreenbury in https://github.com/alan-turing-institute/uatk-spc/pull/64</li>
</ul>
<p><strong>Full Changelog</strong>: https://github.com/alan-turing-institute/uatk-spc/compare/v2.0.0...v2.1.0</p>
alan-turing-institute/MLJ.jl: v0.20.0
No full textMLJ v0.20.0
<p><a href="https://github.com/alan-turing-institute/MLJ.jl/compare/v0.19.5...v0.20.0">Diff since v0.19.5</a></p>
<ul>
<li>(<strong>breaking</strong>) Adapt to the migration of measures from MLJBase.jl to StatisticalMeasures.jl (#1054). See the <a href="https://github.com/alan-turing-institute/MLJ.jl/blob/dev/docs/src/performance_measures.md#migration-guide-for-changes-to-measures-in-mljbase-10">MLJBase 1.0 migration guide</a> for details.</li>
</ul>
<p><strong>Merged pull requests:</strong></p>
<ul>
<li>CI: fix the YAML syntax for the docs job, and thus properly surface any docbuild failures (#1046) (@DilumAluthge)</li>
<li>Update docs (#1048) (@ablaom)</li>
<li>Try again to generate the documentation (#1049) (@ablaom)</li>
<li><code>docs/make.jl</code>: set <code>devbranch</code> to <code>master</code>, which means that the docs will be deployed for pushes to `master (#1051) (@DilumAluthge)</li>
<li>Try to deploy docs again x 3 (#1052) (@ablaom)</li>
<li>Adapt to migration of measures MLJBase.jl -> StatisticalMeasures.jl (#1054) (@ablaom)</li>
<li>For a 0.20 release (#1060) (@ablaom)</li>
</ul>
<p><strong>Closed issues:</strong></p>
<ul>
<li>Julia crashes when fitting a SVC (#1030)</li>
<li>Update deprecated document example in "Transformers ..." section of manual (#1040)</li>
<li><code>fit!</code> not exported in 0.19.3/0.19.4? (#1041)</li>
<li>Doc generation is failing silently (#1045)</li>
</ul>
Assessment of Self-Archiving in Institutional Repositories: Depositorship and Full-Text Availability
No full textThis research evaluates the success of open access self-archiving in several well-known institutional repositories. Two assessment factors have been applied to examine the current practice of self-archiving: depositorship and the availability of full text. This research discovers that the rate of author self-archiving is low and that the majority of documents have been deposited by a librarian or administrative staff. Similarly, the rate of full-text availability is relatively low, except for Australian repositories. By identifying different practices of self-archiving, repository managers can create new strategies for the operation of their repositories and the development of archiving policies
alan-turing-institute/MLJ.jl: v0.20.1
No full textMLJ v0.20.1
<p><a href="https://github.com/alan-turing-institute/MLJ.jl/compare/v0.20.0...v0.20.1">Diff since v0.20.0</a></p>
<ul>
<li>(<strong>new feature</strong>) Add the <code>BalancedModel</code> wrapper from MLJBalancing.jl (#1064)</li>
<li>(<strong>docs</strong>) Add the over/undersampling models from Imbalance.jl to the Model Browser (#1064)</li>
</ul>
<p><strong>Merged pull requests:</strong></p>
<ul>
<li>Add MLJBalancing to MLJ and add class imbalance docs (#1064) (@ablaom)</li>
<li>For a 0.20.1 release (#1065) (@ablaom)</li>
</ul>
<p><strong>Closed issues:</strong></p>
<ul>
<li>Oversampling and undersampling (#661)</li>
<li>[Tracking] Migration of measures MLJBase.jl -> StatisticalMeasures.jl (#1053)</li>
<li>Include MLJBalancing.jl in MLJ and re-export it's names. (#1062)</li>
<li>Update docs for new class imbalance support (#1063)</li>
</ul>
alan-turing-institute/MLJ.jl: v0.20.3
No full text<h2>MLJ v0.20.3</h2>
<p><a href="https://github.com/alan-turing-institute/MLJ.jl/compare/v0.20.2...v0.20.3">Diff since v0.20.2</a></p>
<ul>
<li>Bump compat for MLJFlow to 0.4 to buy into <code>MLJBase.save</code> method ambiguity fix (in MLJFlow 0.4.1).</li>
</ul>
<p><strong>Merged pull requests:</strong></p>
<ul>
<li>Clarify <code>input_scitype</code> for Static models (#1076) (@ablaom)</li>
<li>Documentation updates (#1077) (@ablaom)</li>
<li>Add integration tests (#1079) (@ablaom)</li>
<li>Test new integration tests. No new release. (#1080) (@ablaom)</li>
<li>Fix the integration tests (#1081) (@DilumAluthge)</li>
<li>Move EvoLinear into [extras] where it belongs (#1083) (@ablaom)</li>
<li>CI: split the integration tests into a separate job (#1086) (@DilumAluthge)</li>
<li>CI tweaks (#1087) (@ablaom)</li>
<li>Update list_of_supported_models for betaml (#1089) (@sylvaticus)</li>
<li>Update ModelDescriptors.toml for BetaML models (#1090) (@sylvaticus)</li>
<li>Update documentation to reflect recent BetaML reorganisation (#1091) (@ablaom)</li>
<li>Replace relevant sections of manual with links to the new MLJModelInterface docs. (#1095) (@ablaom)</li>
<li>Update docs. No new release (#1096) (@ablaom)</li>
<li>Update getting_started.md to avoid error from line 338 (#1098) (@caesquerre)</li>
<li>For a 0.20.3 release (#1102) (@ablaom)</li>
</ul>
<p><strong>Closed issues:</strong></p>
<ul>
<li>Meta issue: lssues for possible collaboration with UCL (#673)</li>
<li>Integration test failures: Classifiers (#939)</li>
<li>Oversample undersample (#983)</li>
<li>Add AutoEncoderMLJ model (part of BetaML) (#1074)</li>
<li>Add new model descriptors to fix doc-generation fail (#1084)</li>
<li>Update list of BetaML models (#1088)</li>
<li>Upate ROADMAP.md (#1093)</li>
<li>Deserialisation fails for wrappers like <code>TunedModel</code> when atomic model overloads <code>save/restore</code> (#1099)</li>
</ul>
Information Literacy and Librarian-Faculty Collaboration: A Model for Success:
No full textIn the age of information explosion and technological advancement, issues of information storage, organization, access, and evaluation have become necessarily important in our societies. Addressing issues of information literacy and designing how they can be best integrated in students' learning process are of critical importance. Library professionals in the United States, particularly in the academia, have realized the importance of information literacy and have attempted in various ways to address these issues. The ultimate goal is to make information literacy an integral part of the academic curriculum, thus helping students to succeed not only during their years in college but also for their lifelong career choices. This article will look at ways of how information literacy can best be incorporated into students' academic experience, and how this process can make students' learning meaningful and successful. Specifically, the author will examine the model of librarian-faculty collaboration in integrating information literacy into the curriculum, as demonstrated in the Ohio Five Colleges' Information Literacy Program.Publisher version of this article is available at: http://www.white-clouds.com/iclc/cliej/cl24.ht
Factors to Assess Self-Archiving in Institutional Repositories
No full textThis paper proposes a group of factors that may be used to assess the success of open access self-archiving. It concentrates on self-archiving in institutional repositories. The authors emphasize the importance of examining content materials, particularly the availability of full text versus abstracts and the deposits archived by authors versus by others.Peer reviewe
Applying the NISO Metasearch Initiative Scheme to Enhance E-Resources Management at Rutgers University Library
No full textThis paper discusses problems in the management of library e-resources and attempts to identify potential solutions to the problems. By describing an e-resources enhancement project taken by Rutgers University Libraries, this paper points to the importance of providing contextually-rich metadata and reorganizing the accessibility of e-resources on a library’s website. It introduces how this Rutgers project adopted the National Information Standards Organization Metasearch Initiative to support the identification of appropriate e-collections for metaseaching. The outcomes of the project have facilitated a dynamic display of relevant e-resources to library users as an effective way of automatic access to library e-collections.Peer reviewe
A Metadata Manager's Role in Collaborative Projects: The Rutgers University Libraries Experience
No full textPurpose – This article discusses the roles and responsibilities of a metadata manager in collaborative digital projects.
Methodology – It describes the general requirements for metadata management, and introduces some scenarios in the practices of digital projects by the Rutgers University Libraries to support the generalized definition. A workflow of metadata management is illustrated.
Practical implications – With an explicit definition of the roles and responsibilities of the metadata manager, many other digital libraries that need to develop a new or optimize the existing workflow may find the Rutgers experience useful as reference.
Originality – Very few articles have explored this topic although the functions of metadata in the development of digital projects have been talked extensively.Peer reviewe
- …
