Bibliographic record
Abstract
2.1 In order to initiate a credit sale the Faculty or Unit (“Unit”) must first be an approved billing unit within Aurora Finance with on-line access to the University approved invoicing system. Approval and on-line access is granted through Aurora Finance Customer Service. 2.2 Based on Unit business requirements, Units may choose additional invoice approval functionality. Profiles are set up by request to Aurora Finance Customer Service. 2.3 Affiliated organizations are not permitted to issue University of Manitoba invoices. 2.4 The Unit is responsible for determining the credit risk of the external party. Financial Services is responsible for opening customer accounts upon receipt of a request from a Unit. In order to request a new customer account or account modification, the Unit must complete the Request to Add/Change Customer form and submit to Revenue, Capital and General Accounting (RCGA). 2.5 Units are responsible to issue invoices in a timely manner after a good and/or service has been rendered to the customer. 2.6 Units shall receive the revenue recorded for the invoiced amount (excluding taxes) in the appropriate FOAP (Fund Organization Account Program) once the invoice has been processed and posted to Aurora Finance. 2.7 The Unit creating the invoice is responsible to charge appropriate Federal and Provincial taxes. RCGA is responsible to assist the Unit with clarification and/or research any areas of tax application uncertainty. 2.8 All invoice terms are issued as due upon receipt. 2.9 Units shall direct customers to submit all payments directly to RCGA payable to “The University of Manitoba”. The setup of Electronic Fund Payments (EFT) arrangements will be handled by RCGA. Collection
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.008 | 0.037 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.006 | 0.004 |
| Open science | 0.003 | 0.005 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.431 | 0.318 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".