Definition of Functions Sample Clauses

Definition of Functions. Consultant shall document the proposed functions in the web-based application. The proposed system will have online and offline functions under main four sections such as  User Management Information System (UMIS) functions – mainly to handle the users (administrative part of system) and static & dynamic data in the systemGeographical Information System (GIS) functions – to enable spatial analysis from MIS data and map based representations for better and rapid interpretations.  Financial Management Information System (FMIS) functions – to handle data related to payments to SPCBs and / or third party agencies that generate and submit water quality data.  Remote Sensing Data Processing (RSDP) functions – to handle raster7 data analysis Online functions will be made available to all users / group of selective users as per CPCB’s requirements. These include mainly data entry, preliminary or screening level data assessment, querying and publishing of the data/results. Offline functions shall be made available to selective users at CPCB and SPCBs as required. These are intended to enable advanced assessment of data which is not possible online. Offline tools may include integration with third party applications. RSDP and advanced statistical analyses are examples of such off-line functions.Figure 1 illustrate online and offline functions for above mentioned four systems within application. These four sections will be interlinked. For example, RSDP will support GIS based Web Portal on Water Quality to update the land use map in base maps. GIS based Web Portal on Water Quality and UMIS data will be linked to the monitoring station locations. UMIS and FMIS will be linked as the payments under FMIS will be dependent on quality of monitoring data.
Sample 1
AutoNDA by SimpleDocs
Definition of Functions. Functions Levels of Need Description Metadata input formats Support for a metadata format as source format of the mapping process Dublin Core Mandatory ESE Desirable EDM Desirable EBU Core Mandatory (for broadcasting related CoPs) / Recommended MPEG-7 Recommended (for CoPs using automatic content analysis) LIDO Mandatory (for museum/gallery related) / Recommended EAD Mandatory (for non-a/v archive related) / Recommended Metadata output formats Support for a metadata format as target format of the mapping process Dublin Core Mandatory ESE Recommended EDM Recommended EBU Core Mandatory (for broadcasting related CoPs) / Recommended MPEG-7 Recommended (for CoPs using automatic content analysis) LIDO Mandatory (for museum/gallery related) / Recommended EAD Mandatory (for non-a/v archive related) / Recommended option to add custom formats Recommended Support for adding new metadata formats XML representation support Mandatory Support for metadata documents in XML format RDF representation support Recommended Support for metadata documents in RDF format Metadata model constructs single -> multiple elements Recommended Support mapping a single element into a set of elements (e.g., string into structured) multiple -> single elements Mandatory Support mapping a set of elements into a single elements (e.g., structured into string) structure using context elements Mandatory Define mapping of content structure constructs using contextual elements conditional mapping based on element/attribute values Mandatory Define mapping rules that are conditioned on values of elements or attributes map collections Recommended Support for mapping of collections of metadata records rather than single metadata records only merge string values Mandatory Support merging values of separate string values into one string value split string values Recommended Support splitting a string value into a set of separate string values number of levels in data structure Mandatory: 2 / Recommended: 2+ Support for number of hierarchy levels in the document structure start from example(s) Recommended Support initiating mapping from example documents start from schema Recommended Support initiating mapping from a schema instance configuration user interface Mandatory Provision of a configuration user interface (instead of/in addition to configuration files) user interface drag & drop mappings Recommended Support of drag&drop for configuring the mappings preview Mandatory Provide preview of configured m...
Sample 1
Definition of Functions. The functions typically expected to be provided by storage tools, services, or systems are listed in Table 6, associated to a level of need defined as follows: • Mandatory - Must have • Recommended - Could deal also without, but it would be better to have • Desirable - May be appreciated in some cases, but in most cases it doesn’t make the difference Function Level of need Description M1- store File mandatory the function of receiving the file in input for writing on storage and hold it persistently (in a non volatile way). The stored File must be exactly the same (at bit level) than the one in input. The function must return to the client/producer the information which will be required for requesting a subsequent restore. M2 - restore File mandatory the function of copying the File from its storage location and make a perfect copy of it on an external location suitable to client/consumer. The restored File must be exactly the same (at bit level) than the one on Storage. R1 - store Folder recommended the function of executing “store File” function recursively for a Folder, including the whole Folder hierarchy which must be reflected on the Storage R2 - restore Folder recommended the function of executing “restore File” function recursively for a stored Folder including the whole Folder hierarchy. In order to be complete the function must provide: - possibility to restore a sub-Folder of the originally stored Folder - possibility to restore a single File from the originally stored Folder hierarchy. R3 - list Files and Folders recommended the function of returning the list of stored Files and Folders, with all the available details, if requested.
Sample 1
Definition of Functions. We assume that the platform is compliant to OAIS model and that its architecture is driven by OAIS functional entities. For each function we provide a short description and also the associated OAIS functional entities. Each function could affect more than one OAIS entity, we simply highlighted the parts of the OAIS model which are more strongly related. For each function we provide a level (mandatory, recommended or desirable). The list below is not complete because evaluating a platform is a complex activity and several criteria can be defined. We decided, for the first year evaluation, to stress high level aspects which provide a clear understanding of the level or maturity (the TRL) of the solution, disregarding those which require more extensive tests using the Presto4U dataset, such as the performance. Function OAIS functional entity Level of requirement Description M1 - GUI ingestion Ingest Mandatory Ingestion using guided procedure offered by the GUI M2 - Preservation of original content properties Xxxxxx Xxxxxxxxx The original file received by the producer is stored in the archive M3 - Support for AV formats Ingest, Data Management Mandatory Support for AV formats selected for the Presto4U dataset M4 - Preservation Workflows Management Ingest, Preservation Planning Mandatory The platform implements workflows including tasks for content curation M5 - Export of DIP Access Mandatory Allow creation of Dissemination Packages for access M6 - Periodic integrity checks of the material and storing information in the AIP Preservation Planning Mandatory Periodic checks for file corruption (related also to availability of multiple copies for restore) M7 - Format migration Data Management Mandatory when format is at risk of obsolescence (a few tools working on it) M8 - Ability to deal with large files Archival Storage Mandatory Integrate storage technologies suitable even for huge files, for example larger than 10 GB (=20 min of MXF/D10) M9 - Content quality control Data Management Mandatory Integrate tools for QC M10 - Virus check Ingest, Data Management Mandatory Integrate tools for virus check of ingested content R1 - Batch ingestion Ingest Recommended Capability to ingest list of SIP files from CLI, managing ingestion queue R2 - Support for METS Ingest, Data Management, Access Recommended METS is used as a wrapper for SIP, AIP, DIP R3- Support for PREMIS Data Management Recommended PREMIS is used for preservation metadata and for logging preservation events...
Sample 1

Related to Definition of Functions

  • DELEGATION OF FUNCTIONS 5.1 The functions that must be delegated by the Health Board to the Integration Joint Board are set out in Part 1 of Annex 1. The services to which these functions relate, which are currently provided by the Health Board and which are to be integrated, are set out in Part 2 of Annex 1.

  • GENERAL DEFINITION OF PRODUCTS Item 1: Cafeteria Furniture • Mobile tables on rollers with or without benches or stools. • Round and rectangular cafeteria tables without benches or stools. Item 2: Dormitory Furniture • Metal, wood, or wood clad metal wardrobes, beds and mattresses, night stands, chest of drawers, and single pedestal dormitory student desks with keyboard or center drawers.

  • Definition of Family Members of the employee's immediate family are defined as the employee's spouse, mother, father, brothers, sisters, sons, daughters, stepchildren, mother-in-law, father-in-law, sons-in-law, daughters-in-law, stepparents, grandparents and grandchildren.

  • Transfer of Function Where the Employer has agreed to a transfer of function, it will be the responsibility of the Employer to provide in-service programs/training to all nurses required to perform the function. Employees required to attend such programs will be paid at the applicable rate of pay.

  • Definition of Grievance A grievance shall be defined as any difference arising out of the interpretation, application, administration, or alleged violation of the Collective Agreement.

  • General Definitions 1. For the purposes of this Agreement, unless the context otherwise requires:

  • 020 Definitions The following definitions shall be applicable to this chapter:

  • 050 Definitions 3.48.060 Filing of FEPC and EEOC complaints not prohibited. 3.48.070 Informal and formal procedures. 3.48.080 Costs of hearing. 3.48.090 Representation. 3.48.100 Freedom from reprisal.

  • Specific Definitions The following terms used in this Agreement shall have the following meanings:

  • Definition of Layoff A layoff shall be defined as a reduction in the work force or a reduction in the regular hours of work as defined in this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!