Papers › Joint Multisided Exposure Fairness for Recommendation

Joint Multisided Exposure Fairness for Recommendation

29 Apr 2022arXiv:2205.00048archive 2025-07-28

Haolun Wu, Bhaskar Mitra, Chen Ma, Fernando Diaz, Xue Liu

Prior research on exposure fairness in the context of recommender systems has focused mostly on disparities in the exposure of individual or groups of items to individual users of the system. The problem of how individual or groups of items may be systemically under or over exposed to groups of users, or even all users, has received relatively less attention. However, such systemic disparities in information exposure can result in observable social harms, such as withholding economic opportunities from historically marginalized groups (allocative harm) or amplifying gendered and racialized stereotypes (representational harm). Previously, Diaz et al. developed the expected exposure metric -- that incorporates existing user browsing models that have previously been developed for information retrieval -- to study fairness of content exposure to individual users. We extend their proposed framework to formalize a family of exposure fairness metrics that model the problem jointly from the perspective of both the consumers and producers. Specifically, we consider group attributes for both types of stakeholders to identify and mitigate fairness concerns that go beyond individual users and items towards more systemic biases in recommendation. Furthermore, we study and discuss the relationships between the different exposure fairness dimensions proposed in this paper, as well as demonstrate how stochastic ranking policies can be optimized towards said fairness goals.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 4 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 7 ran (5 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

haolun-wu/jmefairness officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 7 ran (2 instrument-failed) · 2 unverified report
olineranum/jme-fairness_reproduction_study mentioned on GitHubpytorchSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 4 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

4ran · honoured contract
1ran · violated contract
1ran · our draft was wrong
1ran; the contract check could not run
2unverified

Licence: 9 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from haolun-wu/jmefairness. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

haolun-wu/jmefairness official repository 9 samples, 7 ran (2 instrument-failed) · 2 unverified
GI_F_mask Disparity_Metrics.py ran · honoured contract no licence file found · pointer only · ceaf2ae65c4f712b · report fixture: signature E_system:Tensor/2/float, E_target:Tensor/2/float, E_collect:Tensor/2/float, user_label:Tensor/2/float, batch_indicator:Tensor/2/float · returned list · level recorded 2026-09-22
IG_F_mask Disparity_Metrics.py ran · honoured contract no licence file found · pointer only · dcf370dcfa9898b4 · report fixture: signature E_system:Tensor/2/float, E_target:Tensor/2/float, E_collect:Tensor/2/float, item_label:Tensor/2/float, batch_indicator:Tensor/2/float · returned list · level recorded 2026-09-22
II_F Disparity_Metrics.py ran · honoured contract no licence file found · pointer only · e38817813b1effd7 · report fixture: signature E_system:Tensor/2/float, E_target:Tensor/2/float, E_collect:Tensor/2/float, batch_indicator:Tensor/2/float · returned list · level recorded 2026-09-22
age_mapping read_data.py ran · honoured contract fingerprinted no licence file found · pointer only · d6e7c25fe0ea316d · report fixture: signature age:int/0/int · returned int · level recorded 2026-09-22
convert_unique_idx read_data.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · 8620a395f0a3a8ad · report fixture: signature df:DataFrame/0/?, column_name:str/0/str · returned tuple · level recorded 2026-09-22
gender_index read_data.py ran · our draft was wrong no licence file found · pointer only · 34560a56b171093a · report fixture: signature df:DataFrame/0/? · returned tuple · level recorded 2026-09-22
normalize_matrix_by_row run_metric.py ran · violated contract fingerprinted no licence file found · pointer only · 652f85bb48b6bdaa · report fixture: signature matrix:ndarray/2/float · returned ndarray · level recorded 2026-09-22
eval_function_static run_metric.py unverified no licence file found · pointer only · a96e6df3d3d312e9 · report
eval_function_stochas run_metric.py unverified no licence file found · pointer only · 9797ef335b8a478d · report

Tasks

Exposure FairnessFairnessInformation RetrievalRecommendation SystemsRetrieval

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections