Islamic Development Bank: To enhance the Islamic Development Bank's brand identity and to be equipped with the new functionalities that are envisaged, Islamic Development Bank is planning to build a new Drupal based website to replace the existing 9 year old website. Also, the Islamic Development Bank would want to effectively portray the services and activities of the IDB to its beneficiaries including IDB Member Countries, partners, Scholars, Suppliers, and the public at large. The new website should have an eye catching design with responsive layout and improved and refined content management capabilities. English: Arabic: Web URL: This project is currently on staging. Year: 2017 Broad user epic(s) : Drupal  for the development of the website Version control for content management will be used to keep track of revision of contents Workbench moderation will be there for the content publishing process The theme will be by default, responsive and will be suitable for tablet/mobile devices The site will have multilingual capabilities. There will be provision to create contents in Arabic and French along with English and ability for the admin to add more There will be option to share the contents in the site to different social media like Facebook, Google+ and twitter The site will be optimized for SEO There will be option to create landing pages for events and activities All the events can be listed in an event listing page. Implement a contact directory to add and publish contact details Contributed module available in Drupal - Poll, can be used to create Polls Survey and statistical analysis module will be implemented in Drupal Data migration from old site will be carried out RESTful services of Drupal, available in core can be used to create content APIs Memcache can be installed on the server for performance optimization SSL will be installed for the site Google analytics integration will be done to track number of hits, keywords, page views etc Backups of  files and database can be rsynced to an external server The code developed will follow Drupal coding standards The website will be WC compliant Content staging can be used to deliver content over staging and production. Why was drupal chosen? Drupal is secure, scalable and flexible by default. This is why most government websites including the whitehouse, india govt., australian govt., etc have used Drupal exclusively for their official and internal sites. This is why IDB also went with Drupal. This project is a very large and complex one requiring features like multi-lingual support, SEO, high traffic and so on and Drupal 8 provides all these features out of the box. This is why Drupal 8 was chosen. Architecture solution and delivery methodology adopted : Web Server: Acquia cloud will be used for hosting the web application which is scalable. Application: Drupal 8 Lightning distribution Search : Apache solr (Acquia connector) provided by Acquia cloud. Back-end: MySQL provided by Acquia cloud. Version control system: GIT will using as the version control system. GIT repository will be provided by Acquia cloud. IBM Notes Email Services: For sending system generated email messages. Theming: Pattern Lab will be used to ensure atomic design for all design elements. MailChimp: For managing contacts collected via Newsletter form and for sending/ scheduling Newsletters. Active Directory: SAML protocol based ADFS is proposed for authentication and sign-on  Project Data import web service/ DB Connector. Duration (calendar months) of the project : 8 Months Approximate person months in the project:   Business Analyst 3 Months Technical Architect 1 Month Project Manager  4 Months Developer 22 Months Tester 10 Months Summary of Deliverables: Responsive UI Design and Theming The design of the site reflects the corporate outlook of IDB. The new design is responsive to allow compatibility across various devices. The navigation scheme is made intuitive so that relevant and important contents can be accessed with ease by the users. The portal has a responsive frontend which will help users to view the portal in different devices - desktop, tablets, and mobile phones. The theming is done to make compatible rendering of images and texts based on different screen sizes. Multi Language Ability: The site will be multilingual with 3 languages, Arabic, English, and French. The system supports any language so that in the future we can add more language to the system. Creator has to add content for the added language. By default English will be the site language. If someone switches to Arabic, the selected page will be shown in Arabic if Arabic is present other wise it will display English content. Below is the work flow of multilingual feature. Below is the work flow of multilingual feature. Each content will be having translation adding/ editing option at creator, reviewer and approver level and all three versions go through the workflow along with the default language content. By default the language will be in English. Editor has the option to add translations of the same in French and Arabic. Custom Multilingual Search: Apache Solr is used to index the content in the website to provide faster searching. To enhance this search with filters, we use Facet API. Content: Drupal application is connected to an IDB webserver to access data via a webservice to synchronize the project data. Single Signon : Since active directory integration is implemented with the system, a single signon method Is used, where the user needs to login into one system either Active directory( via logging into their office computer) or Site. There is a central domain, through which authentication is performed, and then the session is shared with other domains requiring same user profile. Content Management – Publishing Workflow: When an authenticated user with permission to create/review/approve publications logs into the system, his backend dashboard will display the option to create a new publication item or the list of items which are assigned to him to review/approve/publish. Publication content that is published will get displayed on home page and it can be downloaded. Social Media Sharing : There will be a social media sticky in homepage with social media icons such as Facebook, Linkedin, Twitter, Instagram, Content alert( envelope icon) and RSS Feed. The published contents will have a social media widget to share contents to Facebook, Twitter, Linkedin, instagram, RSS feed and content alert. MailChimp Integration: The Drupal portal will be integrated with the MailChimp API. The interest areas and the email addresses captured will be send via the API. The interest areas will get converted as mailing groups and the email addresses will be linked to the respective mailing groups. RSS Feeds : Visitors can get updates from the subscribed feeds in Drupal portal to their RSS feed reader software/Browser plugin. These applications at the user end will be used to display and read the feeds It will be displayed as notifications on the browser plugin or in the application when new contents are added to the portal based on the subscribed RSS feed category. The instructions on the different feed readers will be displayed to the user in the RSS page Google Analytics: The wite is optimized for SEO. Webmaster will be able to track the visitors and analyse the most visited contents, Geography, Language, Browser, Operating system, Service provider. Real time analytics will also be available. Topic Egovernment

Takamol B2B Online Marketplace: Takamol is a Saudi Arabian government owned limited liability company incorporated to provide services for Small and Medium Enterprises (SME) and thereby contribute to the development of the non-oil economy in the country. Takamol was owned by Ministry of Labor (MoL), Human Resources Development Fund (HRDF) and Technical and Vocational training Corporation (TVTC) which are collectively known as MoLPlus. A key element of their strategy was creation of an On-Line Marketplace for SMEs to trade amongst themselves. The On-Line Marketplace aimed to bring in a set of efficiencies into the market by helping buyers and sellers find each other easily, enhance credibility of buyers and sellers through a registration and neutral party  verification system and an online order management system for ease of buying and selling. The website handles contents of two different languages - English and Arabic which is essential for a B2B site. English:   Arabic: Web URL: https://www.910ths.sa/ (The website has undergone further modifications since our engagement with them was completed in early 2016) Year: 2015 A detailing of the On-Line Marketplace we built is presented below. Broad user epic(s) : B2B service primarily constitutes of companies within Saudi Arabia to register on the 9/10ths portal in order to help them Buy and Sell products or Services. There are two main user roles to take into consideration in this service; Buyers and sellers. Buyers are companies trying to find product/services in Saudi Arabia and Sellers are companies trying to find customers in Saudi Arabia. The following are brief outlines of the epics of features implemented for this service. 1. For a Buyer Creating a Request Browse products Contact potential suppliers Receive interest from potential suppliers Watch list Rate products 2. For a Seller Creating a product/service catalogue Browse requests for quotation Contact potential customers Receive request from potential customers See similar opportunities Check competition Display related products to main products CRM 3. Common features for both Buyers and Sellers Social media Sharing Create a team profile Auto-matching Tag companies Rate companies Why was Drupal chosen? An ecommerce solution must incorporate a robust content management system if it is to provide a platform for ongoing success.  Drupal is secure, scalable and flexible by default. This is why most government websites including the whitehouse, india govt., australian govt., etc have used Drupal exclusively for their official and internal sites. This is why TakaMoL also went with Drupal.  This project is a very large and complex one requiring features like multi-lingual support, multi-domain, SEO, high traffic and so on. Also, Drupal is a CMS with framework like features and it is easy to build anything over it by extending it’s core features. This is why Drupal 7 was chosen.  There is no other CMS framework providing all these features out of the box. Architecture solution and delivery methodology adopted Platform and tools: Drupal 7 Modules Used: Entity, ECK, Drupal Chat, Media, Rules, Apache Solr, Facet API, Voting, Fivestar Third Party Integration: Apache Solr. Development Infrastructure: LAMP stack (Linux, Apache, MySQL and PHP); 2 webservers and 2 database servers were used for load balancing. Delivery Methodology: Continuous integration with Jenkins build server Development Model: We had used Agile methodology in this project as there were high degrees of complexity due to which requirements could not have been elaborated upfront and aggressive deadlines were to be met. Here the Product Owner was the Client Engagement Manager from Takamol who was responsible for maintaining the Product backlog which initially contained the prioritised, high level user stories. These high level user stories were broken down into smaller well defined user stories in a series of workshops, onsite at Saudi. The unclear requirements were pushed to the back of the backlog and developed into smaller user stories in an iterative manner throughout the project. A scrum team consisting of 1 business analyst, 7 developers and 2 testers was constituted and was led by Zyxware project manager/Scrum Master. The sprint cycle was 3 weeks. The cycle started with the sprint planning session and ended with a client walkthrough/demo and a sprint retrospective meeting. During the sprint planning session, story points were assigned based on the relative complexity of the user stories. During the build, while the developers worked on the build, the testers designed the test cases. As and when user stories were completed, testing was done and defects were addressed. Daily scrum meetings were conducted. After the first sprint the team capacity was determined via velocity which helped in sizing the future sprints. After each sprint, an incremental piece of the product was demonstrated to the customer for feedback. Any new requirements were added to the product backlog and prioritised. Duration (calendar months) of the project : 5 Months Approximate person months in the project: Project Manager 5 Months Assistant Project Manager 3 Months Business Analyst 2.5 Months Solutions Architect 2.5 Months Technical Architect 5 Months Developer 50 Months Tester 20 Months Summary of Deliverables: Responsive Theme : The portal has a responsive frontend which will help users to view the portal in different devices - desktop, tablets and mobile phones Content Management: Ability to create and manage product catalogues. Option to create and display information regarding trade enquiries, events, exhibitions, trade fairs in different products in India and abroad.  Option to send business enquiries for a product/catalogue and ability to view the enquiries.  Ability for rating of products and companies. Multilingual Content: The website handles contents of two different languages - English and Arabic which is essential for a B2B site. CRM: B2B Portal Admin can, view Requests they have posted.  view the request detail page which shows the ‘Request Details’ and ‘Responses’ from different companies as separate tabs. It also shows the ‘Similar Requests’ and ‘Qualified for this Requests’ as separate tabs. B2B Portal user can view similar opportunities details and competitor details,on opportunities detail page. flag opportunities as leads view their own leads manage leads by changing its status, stage and adding remarks. generate quotes for customers from the leads view statistics like number of opportunities, leads, closed leads. manage watch list by viewing all items in the list and can remove items from it. view contact list of companies and customers contacted to them as separate tabs. manage approval of pending requests. Custom Multilingual Search: Apache Solr is used to index the content in the website to provide faster searching. To enhance this search with filters, we use Facet API. Social Media Sharing: The company profiles, products/services and requests can be shared to social media – Facebook, twitter and so on.   Topic Egovernment

Introduction The platform, National Virtual Library of India (NVLI) envision to bring together several archival and other electronic resources held with public libraries, museums, Central and State Governments, private collections, etc., on to a single knowledge hub interface. All software programs developed and modified for this project were released in public domain under a GPL license in drupal.org and other repositories such as Github. Being a company specialising in Drupal development services, Zyxware joined hands to compliment IIT-B’s efforts in the solution architecture, design, development, and delivery in this mission of national importance. Zyxware Technologies developed a series of projects in partnership with NVLI (National Virtual Library of India) and IIT-Bombay (Indian Institute of Technology Bombay). The major ones are given below:   1. Biolog Drupal Distribution Biolog is Drupal distribution developed and maintained by Zyxware Technologies to build biography portals of eminent leaders in Drupal 8. Web URL: https://www.drupal.org/project/biolog  Year: 2016 Sardar Patel Web Portal: http://sardarpatel.nvli.in/ Sardar Patel Web Portal is the first website developed using the Biolog Drupal Distribution. The website is a comprehensive study in the life of Sardar Vallabhai Patel, a key figure in the Indian freedom struggle.  Built on Drupal 8, the website has the ability to translate to different languages. It showcases information about Sardar Patel collected from various libraries. A timeline in the site along with interesting titbits, quotes and a quiz tells us who the man is and how he came to be known as the ‘Iron Man of India.’ The digital assets of over 2000 content records can also be viewed based on the theme or main events in his life.    Web URL: http://sardarpatel.nvli.in/  Broad user epic(s) :  Design and develop a web portal that showcases archival records (over 1000 images, 800 documents, several audio and video recordings) about Sardar Patel collected from various libraries Search tool to locate archival records Arrange the content in sections such as Biography, Thematic Collections or Timelines. Should have ability to translate it to different languages in future Define and implement the data flows, standards, technologies and architecture that will underpin the solution Why Drupal was chosen:  Drupal was chosen due to the content rich nature of the site, the security associated with rich content workflow along with its ability to translate to multiple languages.    Architecture solution and delivery methodology adopted:  Platform and tools: Drupal 8 Modules Used:  Why these modules/theme/distribution were chosen: Contributed modules AudioField Adds audio widget for uploading and playing audio files Blazy Provides basic Blazy integration for lazy loading and multi-serving images CAPTCHA Provides the CAPTCHA API for adding challenges to arbitrary forms Dropzonejs Embed Provides a framework for different types of embeds in text editors Entity Provides expanded entity APIs Entity Browser Provides a generic entity browser/picker/selector Entity Embed Allows entities to be embedded using a text editor Entityqueue Allows users to collect entities in arbitrarily ordered lists Entity Reference Revisions Adds Entity Reference field type with revision support Facets Faceted search interfaces that can be used on Search API searchers Field collection Provides a field collection field, to which any number of fields can be attached File Browser Provides a default Entity Browser for files, using Masonry and Imagesloaded Language Switcher Dropdown Provides a dropdown select to switch between available languages Media entity Media entity API Media entity audio Media entity for audio files Media Entity Browser This module provides an Entity Browser for Media Entity Media entity document Media entity local documents provider Media entity image Media entity local images provider Paragraphs Enables the creation of paragraphs entities reCAPTCHA Protects your website from spam and abuse while letting real people pass through with ease Search API Provides a generic framework for modules offering search capabilities Search API attachments Extract and index file fields content Solr search Offers an implementation of the Search API that uses an Apache Solr server for indexing content Slick Slick carousel, the last carousel you'll ever need Slick Media Provides Slick carousel integration with Media entity Slick Views Provides Slick carousel integration with Views SMTP Authentication Support Allow for site emails to be sent through an SMTP server of your choice Translation Management Core Core functionality for the Translation Management Suite Video.js Player Video.js is an HTML5 Video Player ViewerJS Inspired to gmail's attachment preview, using Viewerjs.org library Third Party Integration: Apache Solr Development Infrastructure: LAMP stack (Linux, Apache, MySQL and PHP) Development Model: Waterfall Methodology Duration (calendar months) of the project : 3 Months Approximate person months in the project:   Project Manager .5 Months UI/UX Designer .5 Months Technical Architect .5 Months Developer 3 Months Tester 1 Months   Summary of Deliverables: Responsive Theme : The site was custom designed and built from scratch taking into consideration the requirement specifications of the client. The site being in Drupal 8 was designed to be responsive and user friendly. Content Migration: A key part of the project was migrating the 1 TB of data which included videos, images and textual information to be added as content for the site while keeping the site workflow simple and easy to navigate. We have experience in using the migrate module extensively for multiple projects. In this project we used migrate module to import data that is available in a disk. There was around 1TB of data, including images and PDF documents. We used the Drupal migrate system to import that to the Drupal 8 system we have developed. We have implemented Drush scripts and queue system to do the migration automatically. Digital Asset Management : To provide users with easily accessible information, the content on the site is sorted and arranged by the main events or themes as well as the chronological order of events based on the timeline of Sardar Vallabhai Patel.  Custom Search : Being able to search on a given topic or name was also a requirement, as this site was part of National Virtual Library of India(NVLI).  Watermarking media files Make Eminent portal as a Drupal distribution: Biolog is the Drupal distribution developed and maintained by Zyxware Technologies to build biography portals in Drupal 8 (https://www.drupal.org/project/biolog). Features: Media Entity Image Document Audio< Video RECAPTCHA Apache Solr Facets Google Analytics tracking Paragraph support Multilingual support Media bulk migrate from CSV Inline PDF viewer Translation management workflow 2. Mirador Drupal Module Zyxware Technologies developed a module to integrate Mirador with Drupal for the NVLI (National Virtual Library of India) project. Mirador is a multi-repository, configurable, extensible, and easy-to-integrate viewer and annotation creation and comparison environment for IIIF resources, ranging from deep-zooming artwork, to complex manuscript objects. It provides a tiling windowed environment for comparing multiple image-based resources, synchronised structural and visual navigation of content using openSeadragon, Open Annotation compliant annotation creation and viewing on deep-zoomable canvases, metadata display, bookreading, and bookmarking. Web URL: https://www.drupal.org/project/mirador Year: 2016 Broad user epic(s) : The Mirador module: Works as a Field Formatter in entities. Provides annotation capabilities in the images. Mirador module provides a image field formatter and a text field formatter named as mirador. You can set the field formatter in the "Manage display" of your entity. Eg: /admin/structure/types/manage/article/display. In the field formatter a setting option is available to map the field values. These field values will be used to generate the metadata of the mirador viewer. The Mirador plugin: Mirador implements the full client functionality of the IIIF Image and Presentation APIs. It provides tools for bringing in metadata, images, structures, and can create, edit, delete, and view annotations in Open Annotation Format. Appearance is controlled through CSS so it can be restyled. Mobile friendly. Why Drupal was chosen: Drupal was chosen due to the content rich nature of the site, the security associated with rich content workflow along with its ability to translate to multiple languages. The main project was planned to be built predominantly on Drupal 8, Bigpipe, CDN, and RESTful architecture that is elastically scalable. Architecture solution and delivery methodology adopted : Platform and tools: Drupal 8 Development Model: Agile Methodology Project Management System: JIRA Duration (calendar months) of the project : 1 Month Approximate person months in the project:   Project Manager .5 Months Developer 2 Months Tester .5 Months Summary of Deliverables: The Mirador Drupal module: Works as a Image Formatter in entities. Working: Image Field Formatter: Set the field formatter as mirador for the image field, for the entity type you wish to display mirador viewer. This setting will be available in the "Manage Display" of the fields for that entity type. Set the field mapping for the metadata in the settings form near to the "Format" option. Once a entity against this entity type is viewed, the mirador-load.js will initiate, a manifest file will be generated by the system, with the provided image and metadata. This manifest file will be passed to mirador.js, The image then will then be loaded via IIIF server provided in the configuration. These images will be cached by the IIIF Server. The cache directory location can be specified in the IIIF Server configuration.   Text Field Formatter Set the field formatter as mirador for the text field, for the entity type you wish to display mirador viewer. This setting will be available in the "Manage Display" of the fields for that entity type. Set the field mapping for the metadata in the settings form near to the "Format" option. On creating the entity against this entity type, specify the image path in the mirador field. the image path, should be the path from that is set in IIIF Server. On viewing the entity, The mirador-load.js will initiate, a manifest file will be generated by the system, with the provided image and metadata. This manifest file will be passed to mirador.js, The image then will be loaded via IIIF server provided in the configuration. These images will be cached by the IIIF Server. The cache directory location can be specified in the IIIF Server configuration. Annotation Custom End Point Go to /admin/config/media/mirador Set the Annotation Endpoint as "Custom End Point" Create Endpoint a. Set the endpoint url. b. Set the Create Method. c. For create endpoint, Mirador provides the following data in request object. i. uri -> The resource uri. That is the uri of the image entity, which is being annotated. ii. text -> The annotation text. iii. data -> The annotation data in json format. iv. media -> The media type. In this case image. d. The create endpoint expects the complete created entity back as json response. With id in the entity. Update/Delete Endpoint a. Set the endpoint url. b. Use token {annotation_id}, for specifying the annotation ID, in url. Mirador will replace it with annotation id. b. Set the update method. c. For update endpoint, Mirador provides the following data in request object. i. uri -> The resource uri. That is the uri of the image entity, which is being annotated. ii. text -> The annotation text. iii. data -> The annotation data in json format. iv. media -> The media type. In this case image. d. The delete endpoint provides nothing the id in request object. e. The update/delete endpoint expects nothing back as response. Set the permission "Perform annotation operation". This will disable the annotate buttons in the viewer for those without permission to annotate.   REST Endpoint. Create a entity type to store the annotation data. Create necessary fields in the entity type to store the annotation data. Enable "rest" module available in core. /admin/config/media/mirador enable "Rest endpoint". Add the entity type data in settings available at /admin/config/media/mirador. Add field mappings, so that system knows where all to store the data in the provided entity type. Add proper permissions for content creation/update/view/delete of the created entity type Add proper permissions for REST Webservice. Set the permission "Perform annotation operation". This will disable the annotate buttons in the viewer for those without permission to annotate.   The Mirador Viewer: Open-source, Web based, multi-window image viewing platform with the ability to zoom, display, compare and annotate images from around the world. See project home : http://projectmirador.org/ Installation: Install the module as normal, see link for instructions. Download compiled Mirador javascript library into Drupal's libraries directory, usually in`/libraries`. Verify the file permission is web servable. Make sure the path to the plugin is libraries/mirador/mirador.js (Mirador JS library uses jQuery 1.9.1 which is conflicting with Drupal. So we have uploaded a version of mirador at https://github.com/NVLI/mirador-js-drupal) We cannot distribute Mirador Javascript library along with the Drupal module due to incompatibility with GPL v2 and Apache 2 licenses. Set the IIIF image server in path /admin/config/media/mirador. In the image server specify the path upto files directory, in simple resolver config. Topic Egovernment