human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "online policies for efficient volunteer crowdsourcing"
  Abstract: Nonprofit crowdsourcing platforms such as food recovery organizations rely on volunteers to perform time-sensitive tasks. To encourage volunteers to complete a task, platforms use nudging mechanisms to notify a subset of volunteers with the hope that at least one of them responds positively. However, since excessive notifications may reduce volunteer engagement, the platform faces a trade-off between notifying more volunteers for the current task and saving them for future ones. Motivated by these applications, we introduce the online volunteer notification problem, a generalization of online stochastic bipartite matching where tasks arrive following a known time-varying distribution over task types. Upon arrival of a task, the platform notifies a subset of volunteers with the objective of minimizing the number of missed tasks. To capture each volunteer's adverse reaction to excessive notifications, we assume that a notification triggers a random period of inactivity, during which she will ignore all notifications. However, if a volunteer is active and notified, she will perform the task with a given pair-specific match probability that captures her preference for the task. We develop two online randomized policies that achieve constant-factor guarantees close to the upper bounds we establish for the performance of any online policy. Our policies as well as hardness results are parameterized by the minimum discrete hazard rate of the inter-activity time distribution. The design of our policies relies on two modifications of an ex-ante feasible solution: properly scaling down the notification probability prescribed by the ex-ante solution, and sparsifying that solution. Further, in collaboration with Food Rescue U.S., a volunteer-based food recovery platform, we demonstrate the effectiveness of our policies by testing them on the platform's data from various locations across the U.S.

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.DS(Data Structures and Algorithms)