Hi Kotrappa, Couple of the fields are designed for the potential needs in the future, so couple of the fields are not used right now.
license_ref table ---------------------- rf_pk, - License id primary key rf_shortname, - short name of license -like GPL rf_text, - complete license text rf_url, - URL of where license text is got from rf_add_date, - when this type of license is added rf_copyleft, - open source(copyleft) or not(proprietary license) rf_OSIapproved, - flag of OSI approval rf_fullname, - full name of license e.g. General Public License rf_FSFfree, - lincense is published by FSF or not rf_GPLv2compatible, -- License is GPLv2 compatible or not rf_GPLv3compatible, --License is GPLv3 compatible or not rf_notes, --notes for this license rf_Fedora, --fedora project related license or not marydone, --that guy review all the license, after review, will mark it is checked rf_active, --this license is active(available) or not rf_text_updatable, --this license is editable or not, see license admin page for one specific license rf_md5, - MD5 checksum of license text rf_detector_type - how this license is added, by nomos , or added manually - reference license. guys, I am not the designer, anything wrong on my explanation, please help to point out. You can refer to the page and try to add/update one license to understand this table http://yourhostname/repo?mod=Admin_Lic ense<http://yourhostname/repo?mod=Admin_Lic%20ense> you will find fields below are not used. rf_add_date, rf_add_date, rf_OSIapproved, rf_FSFfree, rf_GPLv2compatible, rf_GPLv3compatible, rf_Fedora, marydone also find that rf_active, marydone(checked) are used, however, not effective. Why we did not get rid of/changed those deprecated<https://www.google.com/search?es_sm=122&q=deprecated&spell=1&sa=X&ei=YR5cVPfGBPiHsQSx44KwAg&ved=0CBwQvwUoAA> fields. The reason is : 1) we want to collect all the requirements and then refactor this table and related functionalities in the future together. 2) some unused fields can be reused by special needs as placeholder. Anything please let me know. -Larry From: fossology [mailto:[email protected]] On Behalf Of Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech) Sent: Thursday, November 06, 2014 6:43 PM To: '[email protected]' Cc: Ravishankar T.S (WT01 - Manufacturing & Hi Tech) Subject: Re: [FOSSology] license_ref table column information Hello Bob, We would like to understand the meaning of column with "??" in license_ref table below If you can explain here or give us link of information, we would be grateful to you. This is required because we want to store similar information in our database of in-house tool we are developing. license_ref table ---------------------- rf_pk, - License id primary key rf_shortname, - short name of license -like GPL rf_text, -complete license text rf_url, - URL of where license text is got from rf_add_date, - ?? rf_copyleft, - ?? rf_OSIapproved, - flag of OSI approval rf_fullname, - full name of license e.g. General Public License rf_FSFfree, - ?? rf_GPLv2compatible, --?? rf_GPLv3compatible, --?? rf_notes, --?? rf_Fedora, --?? marydone, --?? rf_active, --?? rf_text_updatable, --?? rf_md5, - MD5 checksum of license text rf_detector_type --?? Regards Kotrappa. From: Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech) Sent: 03 November 2014 19:11 To: '[email protected]' Cc: '[email protected]'; Ravishankar T.S (WT01 - Manufacturing & Hi Tech) Subject: license_ref table column information Hello Bob, We would like to understand the meaning of column with "??" in license_ref table below If you can explain here or give us link of information, we would be grateful to you. This is required because we want to store similar information in our database of in-house tool we are developing. license_ref table ---------------------- rf_pk, - License id primary key rf_shortname, - short name of license -like GPL rf_text, -complete license text rf_url, - URL of where license text is got from rf_add_date, - ?? rf_copyleft, - ?? rf_OSIapproved, - flag of OSI approval rf_fullname, - full name of license e.g. General Public License rf_FSFfree, - ?? rf_GPLv2compatible, --?? rf_GPLv3compatible, --?? rf_notes, --?? rf_Fedora, --?? marydone, --?? rf_active, --?? rf_text_updatable, --?? rf_md5, - MD5 checksum of license text rf_detector_type --?? Regards Kotrappa. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
