Transformation Procedure Clause Samples

Transformation Procedure. The Common HOPE Metadata Structure is conceived as a pivot or switchboard between local and discovery service structures. Hence it acts as turning point in a series of transformations. These transformations are roughly divided in two phases: The first phase in the transformation process seeks to gather the wide variety of metadata coming from approximately 150 HOPE collections into one single metadata structure. This transformation is facing two major thresholds. ● The Content Provider’s Metadata has a distinct cross-domain character. The CPs’ Metadata contains elements that are specific for the domain the metadata belongs to. Archival records have specific elements for recording the provenance of the material. Library records have an extensive set of title statements. Visual records have specific fields for recording information about material and technique used for creating the item. The challenge is to map this metadata in a consistent way into one single, generic metadata structure. ● Moreover, the Content Provider’s metadata has a distinct idiosyncratic character. Even within metadata records belonging to one domain, there is a wide variety of metadata structures. Half of the HOPE metadata is encoded using published encoding standards, but another half is encoded using XML Schemas that are specific to the CPs’ local system. The second phase in the transformation process will take care of the transformation of the metadata records from the HOPE format to a target format which allows a series of discovery services to disseminate the HOPE Metadata. Currently, three services have been identified as targets for this transformation phase: ● The Europeana Data Model format will service the Europeana Portal. ● The different Social Sites formats will be used by a series of Social Sites, such as Flickr, Youtube, Scribd. ● A specific case is the IALHI Portal, which will be serviced by the HOPE format. In order to overcome the two thresholds identified in the first part of the transformation procedure, an intermediate stage has been defined, which consists of a transformation of the local metadata structures into 5 domain profiles. This implies that CPs will map their metadata first to a domain profile. Then the Aggregator will transform the Content Providers metadata to the Common HOPE Metadata Structure. A domain profile is a structured set of domain-specific metadata elements, which are derived from an agreed-on, domain-specific metadata standard. The domain p...

Transformation Procedure. Resident shall be given thirty (30) days’ advance written notice of the rent increase and of the availability of a suitably sized unit or Section 8 voucher prior to the effective date of any rent increase or obligation to move. The Resident must deliver a response to Management, in writing, within ten (10) days of receiving the Notice of Rent Increase/Offer of Unit Availability, and must state the Resident’s intention to pay the additional rent or to move to an appropriately sized unit within thirty (30) days. Resident’s failure to respond to a notice/offer within ten (10) days will be considered a rejection and grounds for lease termination, as will be any subsequent failure to pay the increased rent of complete move.