Book details, member details, and borrowing records are not well linked.<\/li>\n<\/ul>\nBusiness Scenario<\/h2>\n
Let\u2019s say an organization maintains an internal library for its members. The librarian is responsible for recording new books, issuing them to members, and tracking returns. Members borrow books and may sometimes return them late, resulting in fines. The librarian also needs to maintain a history of each book\u2019s usage, including how long a member kept it.<\/p>\n
With Forms 2.0, the library\u2019s data is captured in four main forms: Book, Member, Book Loan, and Librarian<\/strong>. Each form serves a specific purpose but remains connected through lookups and formulas. For example, the Book form<\/strong> shows the details and availability of each book along with its borrowing history, while the Member form<\/strong> tracks a member\u2019s active and past loans. The Book Loan form<\/strong> handles issue, return, and due dates with automated validations and fine calculations. The Librarian form<\/strong> records staff details for accountability in book issue\/return activities.<\/p>\nKey Participant<\/h2>\n
The Library Administrator (Configurator) is responsible for creating different type of forms, blocks, defining field types, applying validation rules, and maintaining the form\u2019s integrity.<\/p>\n
Form Structure<\/h2>\n
The Library Administrator configures the Library Management forms using Nimblework\u2019s Forms\u202f2.0. The following forms (Book, Member, Book Loan, Librarian, and Book Stock Adjustment) were added to manage the full lifecycle of a book\u2014from entry to return.<\/p>\n
Form 1: Book<\/h3>\n
This form captures all the basic details about each book in the library. It also provides a complete log of the book\u2019s borrowing history.<\/p>\n
\n\n\n| Field<\/th>\n | Field Type<\/th>\n | Reason<\/th>\n<\/tr>\n |
\n| Book ID<\/td>\n | ID (Auto-generated)<\/td>\n | A unique system ID to identify and track each catalog entry.<\/td>\n<\/tr>\n |
\n| Book Name<\/td>\n | Single Line Text<\/td>\n | Captures the title of the book.<\/td>\n<\/tr>\n |
\n| Author<\/td>\n | Single Line Text<\/td>\n | Captures the author name to support search and categorization.<\/td>\n<\/tr>\n |
\n| Category \/ Genre<\/td>\n | Lookup (from Lists 2.0)<\/em><\/td>\n| Groups books under categories (e.g., Fiction, Technology) for filtering and reporting.<\/td>\n<\/tr>\n | \n| Published Year<\/td>\n | Number<\/td>\n | Captures the year of publication, useful for filtering recent titles.<\/td>\n<\/tr>\n | \n| Number of Copies<\/td>\n | Text Label & Number<\/td>\n | Displays available inventory for issuing decisions.<\/td>\n<\/tr>\n | \n| Language<\/td>\n | Lookup (Lists 2.0)<\/em><\/td>\nIndicates the language of the book (e.g., English, Hindi)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"Book](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/09\/Book-Custom-Form.png\") <\/h3>\nForm 2: Member<\/h3>\n
This form manages information about all organization members, including their department and other required details, along with their borrowing activity.<\/p>\n \n\n\n| Field<\/td>\n | Field Type<\/td>\n | Reason<\/td>\n<\/tr>\n | \n| Member ID<\/td>\n | ID (Auto-generated)<\/td>\n | A unique system ID to identify and track each library member.<\/td>\n<\/tr>\n | \n| Name<\/td>\n | Single Line Text<\/td>\n | Captures the member\u2019s full name.<\/td>\n<\/tr>\n | \n| Department<\/td>\n | Lookup (from Lists 2.0)<\/em><\/td>\n| Records the department or team the member belongs to.<\/td>\n<\/tr>\n | \n| Contact Info<\/td>\n | Single Line Text<\/td>\n | Stores the member\u2019s email or phone number for communication.<\/td>\n<\/tr>\n | \n| Active Borrowed Books<\/td>\n | Formula<\/td>\n | Shows the number of books currently borrowed and not returned.<\/td>\n<\/tr>\n | \n| Total Books Borrowed<\/td>\n | Formula<\/td>\n | Tracks the total number of books borrowed by the member over time.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"Member](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/09\/Member-Form-Custom-Form.png\") <\/h3>\nForm 3: Book Loan<\/h3>\n
This is the central form that connects books and members during the borrowing process. It manages book issue, return, due dates, and fines.<\/p>\n \n\n\nField<\/strong><\/td>\nField Type<\/strong><\/td>\nReason<\/strong><\/td>\n<\/tr>\n\n| Loan ID<\/td>\n | ID (Auto-generated)<\/td>\n | A unique system ID to identify and track each loan transaction.<\/td>\n<\/tr>\n | \n| Book Name<\/td>\n | Lookup<\/td>\n | Fetches book details from the Book Form to avoid duplicate entries.<\/td>\n<\/tr>\n | \n| Member Name<\/td>\n | Lookup<\/td>\n | Fetches member details from the Member Form.<\/td>\n<\/tr>\n | \n| Issued Librarian<\/td>\n | Lookup<\/td>\n | Records which librarian issued the book, fetched from Librarian Form.<\/td>\n<\/tr>\n | \n| Issue Date<\/td>\n | Date<\/td>\n | Captures the date when the book is issued.<\/td>\n<\/tr>\n | \n| Due Date<\/td>\n | Date<\/td>\n | Captures the expected return date.<\/td>\n<\/tr>\n | \n| Return Date<\/td>\n | Date<\/td>\n | Captures the actual return date.<\/td>\n<\/tr>\n | \n| Book Status<\/td>\n | Radio Group<\/td>\n | Indicates the current status of the book (Issued, Returned, Overdue).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"Book](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/09\/Book-Loan-Custom-Form.png\") <\/h3>\nForm 4: Library Member<\/h3>\n
This form captures librarian details and also tracks the books issued and fines collected against the books by each librarian.<\/p>\n \n\n\nField<\/strong><\/td>\nField Type<\/strong><\/td>\nReason<\/strong><\/td>\n<\/tr>\n\n| Librarian ID<\/td>\n | ID (Auto-generated)<\/td>\n | A unique system ID to identify and track each librarian.<\/td>\n<\/tr>\n | \n| Name<\/td>\n | Single Line Text<\/td>\n | Captures the librarian\u2019s full name.<\/td>\n<\/tr>\n | \n| Contact Info<\/td>\n | Single Line Text<\/td>\n | Stores the librarian\u2019s email or phone number.<\/td>\n<\/tr>\n | \n| Department<\/td>\n | Lookup (from Lists 2.0)<\/em><\/td>\nRecords the department or section the librarian is responsible for.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"Library](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/09\/Screenshot-2025-09-05-at-3.27.46-PM.png\") <\/h3>\nForm 5: Book Stock<\/h3>\n
This form is used to manage adjustments in book stock, such as new acquisitions, damaged or lost books, and manual corrections.<\/p>\n \n\n\nField<\/strong><\/td>\nField Type<\/strong><\/td>\nReason<\/strong><\/td>\n<\/tr>\n\n| Book Stock ID<\/td>\n | ID (Auto-generated)<\/td>\n | A unique system ID to track each stock adjustment transaction.<\/td>\n<\/tr>\n | \n| Book Name<\/td>\n | Lookup<\/td>\n | Fetches book details from the Book Form.<\/td>\n<\/tr>\n | \n| Book ID<\/td>\n | Associate field from Lookup field<\/td>\n | A unique system ID to track each stock adjustment transaction.<\/td>\n<\/tr>\n | \n| Quantity Available<\/td>\n | Number<\/td>\n | Specifies the number of copies available<\/td>\n<\/tr>\n | \n| Comments<\/td>\n | Multiline Text<\/td>\n | \n You can add comments or remarks related to stock levels, such as points to consider, management tips, or information for the librarian.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n ![\"Book](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2025\/09\/Screenshot-2025-09-05-at-3.29.11-PM.png\") <\/p>\n
\n \n- Was this helpful?<\/span><\/li>\n
- Yes<\/a> No<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"author":4,"featured_media":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","multi-rating":{"mr_rating_results":[]},"_links":{"self":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21802"}],"collection":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/comments?post=21802"}],"version-history":[{"count":23,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21802\/revisions"}],"predecessor-version":[{"id":22048,"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/article\/21802\/revisions\/22048"}],"wp:attachment":[{"href":"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-json\/wp\/v2\/media?parent=21802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
| | | | | | | | | | | | | | | | | |