Descriptive metadata Sample Clauses

Descriptive metadata. The package must include a simple EAD file which uses the mandatory elements as defined for the general DIP format. In short, EAD metadata must use the tags set out in the E-ARK DIP Pilot Specification D5.3, among others the following mandatory elements need to be used: • The title for each descriptive unit within the package (element did/unittitle); • The creation date of the record or descriptive unit (one of the elements did/unitdate or did/unitdatestructured); • The relative path to the file or folder within the \representations\[repID]\Data folder of the DIP (element did/dao with the href attribute referring to the relative location of the file, other attributes used according to the official EAD3 standard). If the record includes multiple computer files the additional use of the element did/daoset is needed102. The use of all other elements is optional. Example: … <c02 level="record"> <did> <unittitle>Circular no 25</unittitle> <unitdate type="single" normal="20010324">March 24, 2001</unitdate> … <daoset label="Computer Files" coverage="whole"> <dao daotype="borndigital" linktitle="Circular no 25 body" href="/representations/ID0023dfc33/Circular_no_25/C25_main.pdf"> </dao> <dao daotype="borndigital" linktitle="Circular no 25 Annex I" href="/representations/ID0023dfc33/Circular_no_25/AnnexI.pdf"> </dao> </daoset> </did> </c02> … 102 Like mentioned before, the final linking method is yet to be established. For scenario b) above the package is also expected to include further metadata taken from the extended EAD set as described in Appendix 1 of the E-ARK SMURF Profile (D3.3). The mandatory elements which need to be included: • archival aggregation level(s) to which the records belong (using the @level attribute on the archdesc, c, c01 etc element); • and archival history of the record (using the custodhist element); • if applicable, EAD metadata must also include information about any access restrictions to the records (using the accessrestrict element).
Sample 1
AutoNDA by SimpleDocs
Descriptive metadata. The METS descriptive metadata element <dmdSec> references to archival description metadata (EAD, EAC- CPF, etc.) as seen in Figure 6. May contain <dmdSec> EAD EAC-CPF Other descriptive metadata Figure 6: METS descriptive metadata Archival information can be included in the METS package. For the core interest groups in E-ARK – archival institutions – this information is delivered to the recipient in EAD and EAC-CPF formats. To include EAD and EAC-CPF in a METS profile the use of <dmdSec> is to be preferred according to the METS implementation guide referenced above. The complete rules for all elements and attributes in the <dmdSec> are stated in the profile, the specific elements used when referencing and embedding is shown below. Other metadata standards for description and administrative purposes can be used and referencing or embedding32 them must adhere to the <amdSec> and <dmdSec> rules stated in the profile. Table 3: EAD metadata Element Definition Explanation Card. METS EAD metadata file Metadata file in EAD format referenced in the METS document Metadata file in EAD format when it is referenced in the METS document. Its needs to be stated in the submission agreement if referencing or embedding are used. 0..* <dmdSec> <mdRef: MDTYPE=”EAD” xlink:href=”file:/// 33[EAD-metadata file]” xlink:type=”simple ”> EAD metadata Metadata in EAD format embedded in the METS document Metadata in EAD format when it is embedded34 in the METS document. Its needs to be stated in the submission agreement if referencing or embedding are used. 0..* <dmdSec> <mdWrap: MDTYPE=”EAD”> <xmlData> [EAD metadata in XML-format] EAC-CPF metadata file Metadata file in EAC-CPF format referenced in the METS document Metadata file in EAC-CPF format when it is referenced in the METS document. Its needs to be stated in the submission agreement if referencing or embedding are used. 0..* <mdSec> <mdRef: MDTYPE= ”EAC-CPF” xlink:href=”file:///[ EAC-CPF metadata file]” xlink:type=”simple 32 The Common Specification recommends to avoid embedding. 33 The coice of using ”///” or ”//” depends on implementations. For example, a Windows file path could be file://C:/somefile.txt and file:///somefile.txt would be the corresponding Unix path in case of absolute paths. 34Usually if EAD metadata has been embedded in the METS document once, it will be not referenced as EAD file again.
Sample 1
Descriptive metadata. The descriptive metadata section (<dmdSec>) references descriptive metadata contained in the AIP. Mul- tiple <dmdSec> elements are allowed so that descriptive metadata can be referenced for each separate item within the METS object. Descriptive metadata is referenced by means of the <mdRef> element as part of the descriptive metadata element <dmdSec>. Listing 4 shows an example linking to an EAD XML metadata file. <dmdSec ID="ID550e8400-e29b-41d4-a716-44665544000a"> <mdRef LOCTYPE="URL" MDTYPE="EAD" MIMETYPE="text/xml" CREATED="2015-04-26T12:00:00+01:00" xlink:type="simple" xlink:href="file://./metadata/EAD.xml" CHECKSUMTYPE="SHA-256" CHECKSUM="..." SIZE="2321"/> </dmdSec> Listing 4: Linking to an EAD XML descriptive metadata file
Sample 1

Related to Descriptive metadata

  • Descriptive Data A. The contractor shall deliver data in accordance with and as specified in Section J, Exhibit A (Contract Data Requirements List (CDRL)) and as cited in each individual task order.

  • Descriptive Headings Descriptive headings of the several Sections of this Agreement are inserted for convenience only and shall not control or affect the meaning or construction of any of the provisions hereof.

  • Labels The Contractor shall provide fuel content labels/signs for each pumping station. These labels shall identify significant amounts of alcohols in the fuel and satisfy the requirements of 1NYCRR, Part 224 and 6NYCRR, Part

  • Highlights WI-HER and RTI collaborated with NTDCP to conduct a GESI Pause and Reflect (P&R) meeting in Arusha from October 17-19, 2022. The meeting brought together the six councils (Ulanga DC, Mlimba DC, Longido DC, Monduli DC, Simanjiro DC and Kiteto DC) where the GESI behavior change activity was implemented in FY22 to document lessons learned and plan for GESI implementation in FY23. The meeting highlighted the importance of health education in addressing barriers to MDA uptake and involving government and traditional community leaders in MDA. Participants also discussed how to integrate GESI lessons learned into the CDD training package and potential activities for CCHPs. • Act | East supported the NTDCP to conduct a preparation meeting for the upcoming CCHP Pause and Reflect meeting in November. The preparation meeting was conducted in Singida from October 21-23, 2022. The technical team involved officers from PORALG, Directorate of Policy and Planning (DPP) office of the MOH, R4D, and WI-HER who collaboratively reviewed the meeting agenda, presentations, and documentation tools. During this preparation meeting, NTDCP and XXXXXX strongly recommended a high-level advocacy following the CCHP P&R meeting. This will be important for more resource mobilization at national and sub-national levels. Upcoming activities requiring COVID protocols: • Act | East will collaborate with NTDCP, DPP office of the MOH, and PORALG to conduct the CCHP P&R meeting from November 15-18 in Dodoma. The meeting will bring together district NTD coordinators and health secretaries from the 15 districts that implemented the CCHP activity in FY22 to gather feedback on the CCHP process, successes, challenges and way forward. • In collaboration with NTDCP and PORALG, Act | East will organize review and planning meetings for the districts and regions conducting trachoma and OV MDAs in FY23. The activity will be conducted in Morogoro from November 7-10, 2022 and will be followed by the training of trainers for trachoma and OV MDAs on November 11th. • Act | East will support the NTDCP to conduct SCH and STH MDA in 41 districts in November 2022. This MDA was postponed from FY22 Q4. • In collaboration with NTDCP, Act | East will conduct an LF disease-specific assessment (DSA) outcome investigation in Pangani DC and Kilwa DC in November. • Act | East Tanzania XXXXX staff will attend the NTD Information System (NIS) training in Mozambique from November 28 – December 3rd. • Act | East will support NTDCP and the National Institute for Medical Research (NIMR) Tanga lab to conduct analysis of Dried Blood Spot (DBS) samples collected in FY22 for OV using OV16 rapid diagnostic tests. COVID-19 data monitoring sources: WHO: xxxxx://xxxxx00.xxx.xxx/region/afro/country/tz October 2022 UGANDA Act | East Partner: RTI, The Xxxxxx Center, WI-HER, R4D, Save the Children Total population: 46,205,893 (2022) COP: [Redacted] Districts: 136 RTI HQ Team: [Redacted] Endemic diseases: LF (66), TRA (41), OV (43), SCH (91), STH (136) TABLE: Activities supported by USAID in FY23 LF OV Trachoma MDA N/A 8/11 districts (R1) 0/11 districts (R2) 0/2 districts (Dec 2022) 0/5 districts (June 2023) DSAs (#EUs) TAS 2: 0/8 EUs TAS 3: 0/3 EUs N/A TSS+: 2 EUs Confirmatory mapping: 2 districts XXXXX Targeted follow-up investigation in two districts of Nabilatuk and Buliisa Data quality assessment (DQA) in Buliisa district HSS High-level meeting on mainstreaming NTD drugs Building domestic resource mobilization capacity workshops National advocacy meeting Finalize and institutionalize GESI MDA training curriculum Finalize integration of GESI into MOH-led social and behavior change packages GESI behavior change activity scale up in two districts. Summary and explanation of changes made to table above since last month: N/A • Table is updated with planned FY23 activities. • OV MDA was completed in 8 districts by TCC. Ebola Update: • On 15 September, an index case of Ebola virus disease (EVD) was identified in Mubende District, Uganda. The Ministry of Health declared an outbreak of Sudan EVD on 20 September. As of 6 November, 135 cases have been confirmed throughout 7 districts. The CoP has weekly update meetings with HQ and HO and is actively monitoring the situation. We are developing SOPs and monitoring closely how the virus evolves within Uganda to be ready to change plans should Ebola be confirmed in our implementing districts. Highlights: RTI • Cross border Joint MDA Review Meeting. Act | East supported the RTI team to attend the Joint MDA review meeting in Kisumu, Kenya from 26–27 October. The objective of the meeting was to review progress and document learnings and gains from the previous joint MDA and to disseminate the MDA results. The meeting was attended by Senior MOH officials from both countries, district officials from border districts, Secretary for Health West Pokot County and partners. Some of the key recommendations were (1) to delay trachoma impact survey in West Pokot for 1 more round of MDA to have a joint impact survey with Uganda to realize intended outcomes; (2) Kenya adopting house to house approach of MDA implementation with VHTs; and

  • Images If applicable, the CONSULTANT is prohibited from capturing on any visual medium images of any property, logo, student, or employee of the DISTRICT, or any image that represents the DISTRICT without express written consent from the DISTRICT.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Metadata Bibliographical, structural & descriptive data of the Licensed Material as defined in Schedule 5.

  • Headings The headings contained in this Agreement are for reference purposes only and shall not affect in any way the meaning or interpretation of this Agreement.

  • CAPTIONS & HEADINGS The captions and headings in this Master Contract are for convenience only and are not intended to, and shall not be construed to, limit, enlarge, or affect the scope or intent of this Master Contract nor the meaning of any provisions hereof.

  • Examples (i) The taxpayer has received a statutory notice of deficiency, under I.R.C. Sec. 6212, which entitles the taxpayer to seek Tax Court review of a proposed tax deficiency. This is not a delinquent tax because it is not a final tax liability. Should the taxpayer seek Tax Court review, this will not be a final tax liability until the taxpayer has exercised all judicial appeal rights.

Time is Money Join Law Insider Premium to draft better contracts faster.