Workplace Romances: Should Individuals Engage in Them or Should Individuals Try to Avoid Them?
Bibliographic record
Abstract
The objective of this paper is to explore workplace relationships and conclude whether individuals should engage in workplace romances (WRs) or whether individuals should try and avoid them. Since individuals spend so much time at the workplace, the likelihood of individuals engaging in a WR is high. Nowadays, there are not many jobs that put restrictions on whether or not you can date or have a relationship with someone you work with, however, is this a problem? Should there be restrictions in place regarding dating coworkers or bosses for example? The findings suggest that even though there are some benefits to WRs, the majority of results show that WRs are dangerous as they can cause group dysfunctions, make other workers uncomfortable, affect team performance, ruin professional relationships, result in sexual harassment claims, and so much more. This paper is going to examine the effects of WRs at different hierarchical levels and whether favoritism or a conflict of interest is present. It is going to examine the effect of WRs on job productivity, morale, and privacy, as well as explore the effects WRs have on other coworkers and what happens when WRs end. Lastly, this paper will explore the question: should management step in when it comes to WRs?
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.004 | 0.012 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.004 | 0.008 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".