gistfile1.java

Session session = this.sessionFactory.getSessionFactory().openSession();
c = session.createCriteria(Connection.class);
connection = new Connection(this.publicPatientSimilarityViewFactory.convert(patientPair));
c.add(Example.create(connection).excludeProperty("id"));

Session session = this.sessionFactory.getSessionFactory().openSession();
return (Connection) session.load(Connection.class, id);
  
/**
* So after a little bit of research into Hibernate and Entities,
* I don't really understand what Entities are,
* but my hunch is I don't need to.
* 
* What I understand so far is that Hibernate saves Java objects onto disk.
* The class to be saved by Hibernate should be an Entity, and the parameters of that class
* need to be annotated with @Type.
* The above code is used to create a new instance of the class and save it.
* Then later on it can be recalled by using the second bit of code,
* where id is the field with @Id in the original class. 
* 
*/

//Questions:
//=========

//What is happening on this line? Where is Example coming from? Why excludeProperty(id)?
c.add(Example.create(connection).excludeProperty("id"));

//If we are creating a custom object for match/search requests,
//is it not logical to also create a custom object for the list
//of configured external search "applications"/servers?

//Which part of the UI should the interface be appended to?
//Should it go into the "Modify permissions" pop up?
//Should it appear only if the permissions are set to "matchable"+ or
//should it be always displayed (grayed out)?

limps/ui

branch not merged
https://github.com/phenotips/phenotips/tree/feature-push-to-phenomecentral/components/patient-data-sharing

patient network similar cases [similarity search]