pilot_features
Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University
32 rows where app_id = "F4-P02" and verification = "pending"
This data as json, CSV (advanced)
| feature_id ▼ | app_id | statement | excerpt | source_url | extracted_by | verification |
|---|---|---|---|---|---|---|
| F4-P02-001 | F4-P02 | The system lets a data-entry clerk choose values from drop-down lists instead of typing them | all transaction screens to have drop down selection menus to minimize data entry errors. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-002 | F4-P02 | The system lets an administrator set access levels per user, organisational level and screen | Access level controls, various organizational level user setting by including granular model setting. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-003 | F4-P02 | The system lets a user capture voucher numbers, claim forms and voucher usage by scanning a barcode | the system will interface with the bar-code reader to interface all transaction details. E.g. voucher number verifications, claim form entry and selection of voucher usage by the clients. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-004 | F4-P02 | The system lets a user verify a claim by the client's thumbprint | the system will interface with the thumb-print reader for verifying claims form used by the clients. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-005 | F4-P02 | The system lets an authorised user generate vouchers with unique numbers | the voucher numbers are system generated and created with unique identification numbers with security protocols in-built. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-006 | F4-P02 | The system lets a user print voucher numbers as barcodes | The created unique numbers are then printed out in the form of bar-codes | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-007 | F4-P02 | The system lets a user track a voucher through distribution, sale, treatment, claim and payment | Then at every level on the voucher cycle this number is captured, on distribution, retail sales, point of treatment, enclosed along with claim forms, at the claims processing and finally for the payment. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-008 | F4-P02 | The system lets a voucher carry hierarchical codes for project, batch group, batch and voucher | Project code – Group batch code – Batch number – Voucher number – Security code. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-009 | F4-P02 | The system lets an authorised user amend a voucher's validity date | This validity date can be amended or altered at the system level ONLY by the authorized user. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-010 | F4-P02 | The system lets a user record a maximum retail price on each voucher | Voucher will also have MRP (maximum retail price) | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-011 | F4-P02 | The system lets only authorised people create vouchers | The voucher will be created ONLY by the authorized person. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-012 | F4-P02 | The system lets management set a minimum quantity of vouchers created at one time | The will be a provision to create a minimum quantity of vouchers at one time | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-013 | F4-P02 | The system lets an administrator withhold a voucher, while created vouchers can never be edited or deleted | Once created vouchers will not be edited or deleted but there will be a provision to with-hold any voucher number if the admin team decides to do for any reason. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-014 | F4-P02 | The system lets a user record distributors with a unique code, business type, proprietor, address and status | Each distributor will have unique code and detailed descriptions such as name, address, locations and type of business etc. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-015 | F4-P02 | The system lets a user record addresses down to district, county and village levels kept as reference lists | The address field will capture the geographical location of the distributor, such as District, Sub-District, County, Sub-County or Village / Town, road or street. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-016 | F4-P02 | The system lets a user be prevented from entering a duplicate distributor ID | The system will check the duplicated ID for the distributors. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-017 | F4-P02 | The system lets a user be warned when entering a duplicate distributor name, and keep or change it | On capture of any duplicate name the system will give a warning message to have the duplicate name or to change the name. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-018 | F4-P02 | The system lets a user print a distributor's master details | System will have a provision to print the distributor master details. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-019 | F4-P02 | The system lets a user see a distributor's sales history by batch with purchased, sold, returned and balance quantities | The distributor screen will have a provision to view the Sales History of a particular distributor | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-020 | F4-P02 | The system lets a user print the sales-history report only if their login permits it | Print option of above report is based on User Login Permission only. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-021 | F4-P02 | The system lets a user add, edit, delete or deactivate records on every screen | New (adding new records) | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-022 | F4-P02 | The system lets a user delete a record only if it has no child records | Delete (deleting will be allowed only if no child records are created) | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-023 | F4-P02 | The system lets a user deactivate a distributor | Active/Deactivate (if the distributor has to be deactivated or terminated) | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-024 | F4-P02 | The system lets a user record salespeople and their sales teams | The system will capture the details of MSIU Salesman | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-025 | F4-P02 | The system lets a user record a voucher sale to a distributor with salesperson, date and quantity | The system will capture the details of voucher sales between MISU sales team and Distributors. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-026 | F4-P02 | The system lets a user see sales reports by distributor, salesperson and batch | the user can get the details of Distributor-wise and Salesman-wise and Batch No wise sales details as reports. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-027 | F4-P02 | The system lets the system allocate specific vouchers from stock to a sale by quantity | the system should allocate the relevant vouchers with their numbers and batch numbers based on the stock. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-028 | F4-P02 | The system lets the invoice amount be calculated as quantity times the wholesale price in force on the sale date | Invoice Amount = Whole Sale Rate (should taken from settings master based on sale date) * Qty Sold. (Automatic Calculation) | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-029 | F4-P02 | The system lets each distribution invoice receive an automatically generated number | The system will generate an auto-generated number as Distribution Invoice No. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-030 | F4-P02 | The system lets a user create a missing distributor or salesperson without leaving the current screen | the system has a provision to navigate quickly to its master screen and enter the new Distributor and Salesman details, without closing the present screen. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-031 | F4-P02 | The system lets a user record a sale with a past date but not a future date | But the date of sale can be the past dates. There will be a future date sale validation check available. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
| F4-P02-032 | F4-P02 | The system lets every claim entry be validated when it is saved | every capture of data will be validated and checked on saving into the database. | https://zenodo.org/records/1414117 | llm:claude-opus-5-5@2026-10-17 | pending |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [pilot_features] ([feature_id] TEXT PRIMARY KEY, [app_id] TEXT, [statement] TEXT, [excerpt] TEXT, [source_url] TEXT, [extracted_by] TEXT, [verification] TEXT);