Collision _ids

[jlgelpi]

there is clear possibility of collision of _id's (esp in Datasets, events, etc). To avoid them, I would recommend either a) Use community acronym as prefix: comm_id:some_id resolved using Community data b) Use a combined _id '_id': { "type": "object", "properties": { "id": "some_id", "community": "comm_id" } } a) is probably simpler, but more difficult to validate.

[jmfernandez]

I agree with you on case a) . But, if we follow b), then we should use a different name for the compound key attribute, so it does not collide with possible underlying assumptions in NoSQL databases like MongoDB or Elasticsearch

[jlgelpi]

The compound _id is perfect for MongoDB, but I agree than a) is more general.

JL

Dr. Josep Ll. Gelpí Dept. Biochemistry and Molecular Biomedicine University of Barcelona INB / BSC-CNS

De: José María Fernández [mailto:notifications@github.com] Enviado el: lunes, 20 de febrero de 2017 14:38 Para: inab/benchmarking-data-model benchmarking-data-model@noreply.github.com CC: Josep Lluis Gelpi Buchaca gelpi@ub.edu; Author author@noreply.github.com Asunto: Re: [inab/benchmarking-data-model] Collision _ids (#1)

I agree with you on case a) . But, if we follow b), then we should use a different name for the compound key attribute, so it does not collide with possible underlying assumptions in NoSQL databases like MongoDB or Elasticsearch

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/inab/benchmarking-data-model/issues/1#issuecomment-281081318, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APVhnd_eGUyGWtLs5mS9AlSpJ57bqMZ2ks5reZdIgaJpZM4MGLAb.

Aquest correu electrònic i els annexos poden contenir informació confidencial o protegida legalment i està adreçat exclusivament a la persona o entitat destinatària. Si no sou el destinatari final o la persona encarregada de rebre’l, no esteu autoritzat a llegir-lo, retenir-lo, modificar-lo, distribuir-lo, copiar-lo ni a revelar-ne el contingut. Si heu rebut aquest correu electrònic per error, us preguem que n’informeu al remitent i que elimineu del sistema el missatge i el material annex que pugui contenir. Gràcies per la vostra col·laboració.

Este correo electrónico y sus anexos pueden contener información confidencial o legalmente protegida y está exclusivamente dirigido a la persona o entidad destinataria. Si usted no es el destinatario final o la persona encargada de recibirlo, no está autorizado a leerlo, retenerlo, modificarlo, distribuirlo, copiarlo ni a revelar su contenido. Si ha recibido este mensaje electrónico por error, le rogamos que informe al remitente y elimine del sistema el mensaje y el material anexo que pueda contener. Gracias por su colaboración.

This email message and any documents attached to it may contain confidential or legally protected material and are intended solely for the use of the individual or organization to whom they are addressed. We remind you that if you are not the intended recipient of this email message or the person responsible for processing it, then you are not authorized to read, save, modify, send, copy or disclose any of its contents. If you have received this email message by mistake, we kindly ask you to inform the sender of this and to eliminate both the message and any attachments it carries from your account. Thank you for your collaboration.

[diglesia]

Option a ("Use community acronym as prefix") is already being used in the prototypes (e.g. CAMEO, QfO) available at the benchmarking platform. Issue solved.