From the chair
Bibliographic record
Abstract
The ACM-SIGMIS CPR (Computer Personnel Research) 2009 Conference and Doctoral Student Consortium is almost upon us! The University of Limerick campus in beautiful Limerick, Ireland is the location of this year's conference from May 28-30, 2009. Please check out our 2009 SIGMIS CPR BLOG at: http://sigmiscpr2009.blogspot.com to obtain travel, housing, and other information! Ask a question or post something you found! Please plan to attend the annual SIGMIS Business Meeting to be held right at the close of the conference on Saturday, May 30, 2009. All are welcome! Plans for next year's CPR 2010 Conference, to be held in Vancouver, BC, Canada, are now underway. The Conference Chair is Mike Gallivan, Georgia State University, mikegallivan@yahoo.com or mgallivan@gsu.edu. Please consider joining the program committee, participating in conference planning, and, of course, submitting your research by the October 2009 deadline. Encourage your colleagues to participate! Remember to consult the ACM Digital Library at: http://portal.acm.org/dl.cfm to for this year's forthcoming CPR conference proceedings and Data Base articles. Referring to these publication outlets will keep you up-to-date and in touch with your colleagues' most recent research! I encourage you to continue to submit your best work to Data Base. This publication is the primary vehicle of communication to our membership, presenting articles of practical research significance and relating experiences in the area of business uses of information systems. Data Base provides an accessible, flexible, and timely forum for information on both well-researched topics and those less common, perhaps leading-edge topics which may not yet have found their way into the literature. Controversial or untested research topics are welcome. Submission information is available at the Data Base website at: http://the-database.org. As always, thanks for your continued support of SIGMIS. Please do contact any one of us with comments, ideas, and suggestions for improvement. Have a nice summer! We look forward to seeing you at CPR'09!
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.003 | 0.012 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.005 | 0.001 |
| Scholarly communication | 0.015 | 0.008 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.005 | 0.007 |
| Insufficient payload (model declined to judge) | 0.633 | 0.561 |
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".