Hello, I am not too sure I fully understand what you want to achieve but if you want to keep track of Students ID number why not use that as the cardnumber instead of bothering with attributes. Out of the box installation cardnumber is unique and can not be null.
Hope this helps. Olugbenga Adara Skype: gbengaadara Blog: http://gbengaadara.blogspot.com Twitter: http://twitter.com/gbengaadara Profile: http://www.linkedin.com/in/gbengaadara >________________________________ > From: Achamie Aynalem <aynac...@gmail.com> >To: koha@lists.katipo.co.nz >Sent: Tuesday, October 1, 2013 11:57:47 AM >Subject: [Koha] How in koha > > >I automated a library using koha 3.12. In my system, I created an -extended >patron attribute- called <ID> that holds students' ID Number and checked to >be Unique identifier. >But while I insert or import patrons from a .csv file; >**when I assign value for The <patron attribute> field in the .Csv (like >ID:xxxx), it works well so prevents entering different patrons with similar >ID (well). >**when entering a patron with no value for the ID, it simply enters the >patron so entering of so many patrons with null value for their ID (failed). >so, how to make koha prevent the entrance of null value for a "unique patron >attribute" like ID in my case? > >_______________________________________________ >Koha mailing list http://koha-community.org >Koha@lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
