text:
Category Archives: Metadata
– data driving a process
– uses of metadata
Metadata, Operations, Technology
CIP at DUL: Taking one for the Team
March 31, 2022 Marta Conde
A Cataloging in Publication record (CIP record) is a bibliographic record that the Library of Congress provides to publishers. It is included on the verso of the title page of the book, facilitating the processing of the book by libraries and book dealers. The Library of Congress also distributes these records weekly, in machine readable form, to large libraries, bibliographic services, and book vendors around the world.
Publishers submit applications to the Library of Congress (LoC), and the LoC creates the CIP records for the books, which are then sent back to the publisher. This is a service offered to publishers at no other cost than sending a complimentary copy of the books summited for CIP to the LoC. Only U.S. publishers are eligible to participate in the CIP Program. To qualify for the program, every publisher must have a list of at least three titles by three different authors, and these titles must have been acquired by a minimum of 1,000 U.S. libraries.
The program was established in 1971. A year later the LoC partnered with the National Library of Medicine (NLM) to provide CIPs. Through the years, other 32 United States libraries have joined the CIP Partnership Program of the LoC. Duke University Libraries (DUL) joined in 2008 and agreed to provide the CIPs for the books published by Duke University Press (DUP). In most cases, the partner library catalogs the books published by its own institution. For many years the CIP Program focused only on print publications. From October 2011, the program broadened its scope to include titles published in electronic and print format simultaneously. All partners libraries are NACO and BIBCO members, thus guaranteeing the quality of the cataloging.
When Duke joined the CIP Partnership Program in 2008, the Library of Congress provided a Windows based Text Capture and Electronic Conversion (TCEC) application called On the Marc. This software was developed by Library of Congress' staff to produce MARC21 records from electronic data. The manuscript files submitted by publishers provide the source of the electronic data for the CIP records. On the Marc was configured specifically for use with the OCLC Connexion cataloging client. After the cataloger completed a preliminary record using On the MARC, the record was sent to the OCLC Connexion client, where the cataloger completed the full cataloging of the ECIP. Afterwards, the record (or records) were uploaded to a Duke University server directory as an OCLC Connexion "Local Save" file and harvested by the LoC.
In May 2019 the LoC CIP Program launched a new, more user-friendly, customer service application, the PrePublication Book Link (PPBL).
Things work slightly different in PPBL. The publisher, in our case DUP, submits the CIPs applications that are then picked up by one of the two, at the moment, cataloguers at DUL in charge of creating the CIP records. In the PPBL app, "My Group's CIP" includes all active CIP applications of the institution, and "My CIP" includes all active CIP applications picked up by each individual cataloger.
The information included in the CIP application is the Library of Congress Control number (LCCN), title, status, priority (This will be used to indicate the CIP is a RUSH request by the publisher this field, 1-Critical.), subject, assignment group, assigned to, print month and year and date it was created.
The CIP Program requires that a single galley file in PDF be attached to the CIP Request in PrePub Book Link.
Once the cataloger accepts the CIP application, she changes the status to full cataloging and proceeds to open the MARC Editor in a new browser tab, where some editing is available (e.g. adding the 505 table of contents).
After that, the record is downloaded to the computer and, from there, imported to OCLC to complete the cataloging.
Once the bib record is completed following the Program for Cooperative Cataloging (PCC) guidelines, we export it to a file created specifically for that record using the LCCN, and delete the MARC field tags 001, 003, and 049.
Back in the PPBL, we upload the record using the Partner Cataloger MARC Upload feature and ingest the record in the catalogue VOYAGER of the LoC. If all works well, a success message will be displayed. At this point, we are ready for the final steps in the process: adding the Call number to the PPBL and sending that information to Dewey, the next assignment group, by changing the status from "full cataloging" to "Dewey". By clicking "save" once the status has been changed to Dewey, the CIP is automatically deleted from the side of the PPBL that we have access to.
There are significant differences in workflow between On the Marc and PPBL:
In On the Marc the cataloger sent the bib record directly to OCLC. Once they were ready, she saved them on a specific file to be harvested by LoC. By contrast, in the PPBL application, the records are downloaded to the computer and imported to OCLC; once they are completed, they are again downloaded to the computer, and uploaded by the cataloger, one by one, to the PPBL and to the VOYAGER catalog.
As far as editing is concerned, the PPBL app constitutes an improvement but there remains quite a bit of editing to be done in fields like the 505.
For example, the software allows us to remove common words like "chapter" but we still have to remove and edit the text. In addition, some diacritics don't translate well and the order of the title / author sometimes needs to be flipped manually, like in the example below.
The improvements from On the Marc to PPBL may seem unexciting. It is hard to imagine many of you bewildered by the specifics of the changes outlined above.
Questions about the usefulness of this enterprise may remain. After all, what is the point of what seems a rather convoluted process of information sharing. The answer is simple: to provide, through the coordination efforts of the Library of Congress, a public good in an efficient, decentralized fashion. Each record we upload to CIP is a high quality contribution to the rest of library world. Jointly, we cooperate, helping each other and staying true to the mission of organizing the dissemination of knowledge as presses are ready to share it with world.
Metadata, Operations, Projects
Introducing the Bindery and Monograph Maintenance (BAMM) Section, Resource Description Department
July 30, 2021 Lesley Looper
When the new fiscal year started on July 1, two departments in Technical Services reorganized, and a new section was created within Resource Description. The section known as Shelf Preparation folded, with most related workflows moving to Monograph Acquisitions. (Follow this blog for more news on these changes soon!)
Corrina Carter and Lesley Looper (Team Lead) remain in the Resource Description Department, in the newly formed Bindery and Monograph Maintenance Section. Our new section name is descriptive of our broad work, but is a mouthful to say, so you can call us BAMM for short! (Think Emeril Lagasse or Bamm-Bamm Rubble.) You can email our new section at lib-bmms@win.duke.edu, or individually, as usual.
What BAMM will be doing:
Bindery: creating bindery and preservation boxing shipments, coordinating bound volumes (including monographs, serials, music scores, and items with digi-covers) to circulation points and the Library Service Center, overseeing the annual bindery budget, working with Continuing Resource Acquisitions on periodicals binding, and serving as in-house consultants for care and handling consultations and referrals to Conservation.
Monograph maintenance: cataloging queue maintenance, ALEPH reporting, declaring monographs missing, lost, withdrawn, or reinstated, updating locations and call numbers, resolving AskTech tickets, cataloging documentation review, and special projects (including outsourcing coordination and metadata projects).
Student assistants will also be an integral part of our section, helping us move materials through the section and department workflows, and on to DUL circulation points and the Library Service Center.
Corrina has been working at Duke since 1988! She started in the Medical Center, and transferred to the Surgical Private Diagnostic Clinic (later called the Private Diagnostic Clinics) in 1990. Corrina joined Duke Libraries in 1994, spending all of that time working with the Bindery, with several changes, location moves, and position upgrades along the way! One of Corrina's favorite Duke memories is attending the DUL staff appreciation lunches (especially at the Searle Center), and getting to use work time to attend them. (Way back when, those lunches included humorous plays put on by library staff!)
Lesley has worked at Duke since 2001 (all of it in Duke Libraries), first in Receipts Management (starting as Library Assistant and later as Section Head) within the Acquisitions Department, and then in the Cataloging Department (now called Resource Description). Later, she joined Shelf Preparation Section, before becoming part of the BAMM team. One of Lesley's favorite Duke memories is attending the Rolling Stones concert in Wallace Wade Stadium in October 2005, and running into several DUL colleagues there. Lesley still enjoys visiting Wallace Wade Stadium for Duke football home games.
Activism, Metadata, Operations
Metadata for Everyone: Inclusive Description at the Duke University Libraries
November 23, 2020 Rich Murray
Duke University Libraries Technical Services Division's (DULTS) Resource Description Department has recently composed and adopted a Statement on Inclusive Description, which begins:
The Resource Description Department of Duke University Libraries Technical Services acknowledges that the creation and management of metadata are not neutral activities. We further acknowledge that the framework of national and international standards in which we work has served to uphold white supremacy, marginalization of sexual orientations and gender identities, and colonialism, among other forms of oppression. While we will continue to work within the parameters of national and international standards and organizations, we pledge as creators and managers to make metadata more inclusive …
The metadata that describes the millions of resources Duke University Libraries makes available to users dates back to the early 20th century, and as society has changed, so have cataloging practices. In 2020, we have perspectives on inclusion and representation that perhaps our predecessors did not have in previous decades. Our Statement on Inclusive Description is our pledge to do better, not just as we move forward but as we look at some of our old metadata and think of ways to improve it.
Limitations of Cataloging Standards
Most academic and public libraries in the United States—and in many other countries—use Library of Congress Subject Headings (LCSH) as their main thesaurus to provide subject access to works in their collections. Medical libraries, by contrast, typically use Medical Subject Headings—MeSH–or a combination of MeSH and LCSH. Library of Congress Subject Headings are what most Duke University Libraries catalog users are accustomed to seeing, with familiar patterns like these:
Salvador (Brazil)—Social life and customs—19th century.
Art, Japanese–Edo period, 1600-1868—Exhibitions.
X-Men (Fictitious characters)—Comic books, strips, etc.—Periodicals.
Library of Congress Subject Headings are not, however, always ideal, and can present some obstacles when trying to catalog inclusively. There is often a presumption of whiteness and maleness in LCSH; its default is frequently "straight, white, cis-gendered male," and anyone that doesn't fit into those categories can be seen as exceptional. For example, the LCSH "Chemists" is used for works about chemists of all genders and for works limited to male chemists; a work about female chemists gets the LCSH "Women chemists." (There is no heading "Male chemists.") Similarly, the assumption seems to be that "American literature" is written by straight white male authors: if a work is about any other subset of Americans as authors, the headings must be modified: "American literature—Women authors" or "Gay men's writings, American," for example.
Library of Congress Subject Headings also include some vocabulary that may be considered outdated, inaccurate, or offensive. You may have heard about the political controversy that arose when the Library of Congress considered a proposal to change the heading "Illegal aliens" to "Undocumented immigrants." The change was blocked, and "Illegal aliens" remains the authorized LCSH even though many find it offensive. There are other terms in LCSH, again often dealing with marginalized groups, that some find questionable, such as "Problem children" and "Eskimos." There is a process to propose changes and additions to LCSH, but it is extremely involved, can take a very long time, and can be blocked by external factors, lack of consensus on what a better term would be, and diminished staffing at the Library of Congress.
Finally, there are some areas in which Library of Congress Subject Headings just aren't very good, such as terminology for LGBTQ people and culture. The default LCSH heading for anyone or anything non-straight is "Sexual minorities," a term which may technically be accurate, but which certainly isn't in common usage and also presents LGBTQ folks as an anthropological Other. Meanwhile, the term "Female impersonators" for the entertainers we all know and love as "Drag queens" is, if we're being generous, quaintly outdated. And LCSH just doesn't get specific at all for LGBTQ cultures and subcultures, making it difficult to provide appropriate access for works about them.
Making Library of Congress Subject Headings Work for Us
So, if Library of Congress Subject Headings are problematic, why do we continue to use them? Well, for most subjects, LCSH is pretty good. For many disciplines, it is extremely good. More importantly, it's an internationally used standard. Most cataloging in the English-speaking world and beyond is done cooperatively—that is, libraries contribute bibliographic description for works they acquire to the WorldCat database, so when another library gets the same book (or DVD or anything else), they can just use the record that's already in WorldCat rather than creating their own. It makes everything go faster: trying to catalog every monograph, periodical, map, streaming video, and e-book we receive from scratch to our own exacting standards would be an impossible task. Terms in LCSH are the international standard, and libraries have agreed to use it as our common language when describing what works are about and then sharing description of those works.
Fortunately, that doesn't mean we are limited to out-of-the-box LCSH. There are several ways we provide enhanced access to our resources by bending LCSH or by using other vocabularies altogether. In addition to actively participating in the process of proposing additions and changes to LCSH mentioned above, Duke University Libraries staff also provide more inclusive description in other ways. Perhaps most obvious to the user is our public catalog, which we share and develop with our colleagues in the Triangle Research Libraries Network (Duke, North Carolina Central University, North Carolina State University, and UNC-Chapel Hill). DUL staff are able to customize what displays to the public, so even if the underlying metadata is standard LCSH, we can choose to make alternative terms both visible and searchable. For example, instead of the standard LCSH heading "Poor," which reduces people to a financial status, we have chosen to display "Poor people." Even though "Illegal aliens" remains in our behind-the-scenes metadata, library user see "Undocumented immigrants" when viewing the catalog. Continuing to use standard LCSH allows us to accept bibliographic records from other libraries without having to make manual changes to them locally, but our Search TRLN public catalog empowers us to display alternative terms our users say they prefer, or that we know through analyzing data, that they are more likely to search for.
Screenshot of LCSH terms from the staff view.
Screenshot of LCSH terms from the public view.
In DULTS, when we create original cataloging records, or when we enhance shared records in WorldCat, we also work intentionally to make sure our description is inclusive and accurate, especially for works by and about members of marginalized groups. For example, as we describe the Edwin & Terry Murray Comic Book Collection with our colleagues in Rubenstein Library Technical Services, we make sure to provide specific subject access to works about women, African Americans, people with disabilities, LGBTQ people, and other non-"cis white straight male" characters. "Superheroes" may be the default Library of Congress Subject Heading for caped crusaders, but we make sure users are able to go beyond Superman and Batman by adding more descriptive subject headings like "African American superheroes" and "Women detectives" so characters like Storm, Luke Cage, and Jessica Jones aren't lost in the shuffle.
We have also begun exploring specialized thesauri to supplement Library of Congress Subject Headings when LCSH just isn't specific enough to accurately describe a work's contents. One controlled vocabulary we've begun using is Homosaurus, which calls itself "an international LGBTQ linked data vocabulary." We're able to enhance access to works by and about LGBTQ folks by using specialized terms from Homosaurus that LCSH just isn't able to convey, such as "Bigender people," "LGBTQ sports clubs," "Transgender people of color," and—yes—"Drag queens."
Screenshot from our catalog showing a combination of LCSH and Homosaurus terms.
Making our cataloging more inclusive takes time, but we think it's worth it. We also realize it's a marathon, not a sprint. Until the majority of other libraries that contribute cataloging to shared databases like WorldCat start taking similar approaches, not all of our resources will be cataloged as thoroughly and thoughtfully as we might like. But the principles we lay out in our Statement on Inclusive Description are a start. As we incorporate these tenets in newly created descriptive metadata going forward, we will also explore ways to enhance and improve our old records en masse in hopes of someday providing better, fairer description of all the millions of resources Duke University Libraries make accessible to our users. It's a huge job, but we are committed to making it happen. It's the right thing to do.
Linked Data, Metadata
A Linked Data Primer
January 31, 2020 Dennis Christman
Unless you've been actively ignoring what's going on in the world of Technical Services, you've certainly heard about linked data at this point. You've heard of BIBFRAME, you've heard that it's coming, you've heard that it will change the library landscape, and you may have even taken a workshop on writing some triples. But what actually is linked data?
First, some brief (I promise) historical context on linked data. In 1989, Tim Berners-Lee had the idea of combining hypertext with existing internet transmission technology, essentially inventing the World Wide Web. Once HTML was developed shortly after, websites were able to embed links to other sites inside of them, linking documents together. The technologies have gotten a bit more sophisticated since then, but essentially this is still how most people use the Internet: they put an address into their browser, and then click the links to move between pages.
In 2006, Tim Berners-Lee began to work on what it would look like if our data on the Internet were linked together like our documents were. If your data references information about the state of North Carolina, instead of storing it you could link to an authoritative source that contains data about North Carolina, most likely much more data than you would have stored. He laid out some principles for best practices, but conceptually, that's it — instead of storing data about things, store links to authoritative sources of data about those things.
An Evolving Model
Understanding what linked data is not can be a good place to start when trying to understand what it is. To help with this, I want to look at the layers of standards we use to catalog materials. Some definitions:
Conceptual model: An abstract way of looking at the entities of the bibliographic universe. It has no direct effect on the records we create, but instead it informs the content standards we create.
Content Standard: A set of rules that dictates what data we record and the manner in which they are recorded. A content standard answers the questions of what the entities, attributes and relationships are; what is recorded and what is transcribed; and what is mandatory or optional.
Data structure: The digital format that serves as a carrier for data. Follow the rules of the content standard to fill out the data structure.
The Old Model
This is the basis of our modern cataloging structure. For our data structure, we have good ol' MARC. Created in the 1960s and adopted in the 1970s, its original purpose was to do two things: transmit catalog cards between libraries and facilitate the printing of those cards. MARC was able to be searched by 'experts,' but we're talking about the 70s here. People who used computers to do this kind of work were, by definition, experts. We've repurposed MARC to do all sorts of things, from tracking our orders to creating exports for our discovery layer. Around the same time as MARC, we had AACR, the Anglo American Cataloging Rules, created to standardize how libraries created catalogs and catalog records. MARC was our data structure, and AACR was our content standard. MARC says we have a 245 field, with two single-digit indicators and different subfields. AACR says this is what a title proper is, this is where you find it on a book, and this is where to put the information into these different subfields of the MARC 245.
MARC and AACR work well together because they were designed with a unifying product in mind: a printed catalog card. Saving space was paramount — how much can we fit onto a 3×5 card before it's too busy and unusable? As we've moved away from the print card catalog, we've started to adapt our models as well.
The Current Model
We're still on MARC, but the rest have changed. To begin with, we see the introduction of a conceptual model, Functional Requirements for Bibliographic Records (FRBR). We don't use FRBR to catalog per se, but it informed the development and understanding of our new content standard, Resource Description and Access (RDA). RDA updated how the entities, attributes, and relationships were defined and identified, and provided mappings to MARC.
MARC and RDA don't really work all that well together. MARC is a very flat record structure. It takes all of the data and shoves it into one record, while RDA is all about splitting different levels of description. Romeo and Juliet, the work, is written by William Shakespeare, regardless of the publication date of the manifestation.
The Proposed Model
And that brings us to finally mentioning linked data. The model that we expect to be coming will update FRBR with the newly released Library Reference Model (LRM) with some mostly minor changes, and replace MARC with BIBFRAME, a data structure that is stored in a linked data format built for bibliographic data.
This has all been a very roundabout way of saying that moving linked data doesn't really change RDA at all. All of those cataloging skills of identifying different types of titles (RDA has around 20 types of title), assigning subject headings, and figuring out if the book you're looking at is the same as the record you're looking at don't really change. Eventually the changes made from FRBR to the LRM will inform some updates to future versions of RDA, but that has nothing to do with BIBFRAME or linked data. The changes only flow down.
Semantic Technologies
Linked data is a combination of several technologies that work together to help execute Tim Berners-Lee's vision of a semantic web. Let's start with graph databases. In a traditional relational database, like Microsoft Access, data are stored in tables and linked together by having the primary key of one record in Table A appear as a foreign key in a record in Table B. In a graph database, data are stored as nodes and edges, where every data point is a node and the connections between them is an edge.
Graph databases are where we start to see the concept of a triple play out. They're great for when relationships are complex and not uniform.
Next we have ontologies. An ontology is a naming and definition of the categories, properties, and relations between the entities, data, and concepts that make up one domain of knowledge (taken from Wikipedia). Let's look at an example.
Say I wanted to make one ontology to describe a single volume monograph, or book, and one to describe a piece of two-dimensional visual art. Here are two small ontologies I might design:
Now, let's say I want to create an ontology for comic books. I don't need to start from scratch, I can use existing elements in my new ontology and only create new elements when they don't already exist. I can include a prefix to show which ontology a certain element is defined in.
BIBFRAME is an ontology. It lays out what the entities and attributes are and how they are all allowed to connect to each other. It's replacing the MARC layer of our existing technology.
The next technology that goes into linked data is the triplestore. A triplestore is a type of graph database designed to store RDF triples. It is a piece of software that enables all of the normal database functionality you'd expect, like complex searching and fast retrieval. That's all most of us need to know, which is very fortunate because understanding how they work on a deeper level is some pretty heavy duty PhD level computer science.
All of this brings us to our last piece, RDF, or Resource Description Framework. RDF is a metadata model that stores data in triples. As a model, it's fairly bare bones. Every piece of data is either a class or a property, and triples follow the pattern of 'class' 'property' 'class.' Here's a very basic example:
Our two classes are the name of the hotel and the address, and the property is the relationship between them. I made up an 'omni' ontology to help illustrate how you might model this.
In reality, things get a little more complex:
Here, I've split out the different elements of the address into its individual parts and grouped them all onto an empty node that represents the whole of the address. I've called it 'OWPHAddress.'
And then things get even more complex:
Here, I've broken it out a few different ways. First, I've replaced the hotel name and address nodes with URIs. In RDF, every node is either a URI or a literal, which is an actual string that represents the value. The URI is just a string that uniquely identifies the entity, just like the 001 of a bib record does. I've also replaced the literals for city and state with URI out to Geonames, a triplestore that exists on the Internet and manages geographic data.
What does this let us do? This is just how I modeled an address of a hotel. If there is a restaurant inside of that hotel, I could attach it to that same address node, meaning I don't need to duplicate the data anywhere. If you translate this to describing bibliographic resources, then multiply by a few million to scale up to our collection, you have a dataset of hundreds of millions of triples that represent all of the items Duke owns.
Linked data is a very technical concept, which can make it difficult to accurately talk about, both within our community and with other communities. I didn't really go into the question of why we want to move to linked data, because I think that discussion relies on understanding what it actually is. I hope this helps as a bit of a primer for what is going on under the hood for linked data, and please feel free to get in touch if you have any questions or thoughts you want to share.
Metadata, Projects
Metadata Moves a Library
December 20, 2019 Ros Raeford and Jacquie Samples
Library metadata does more than connect researchers to library resources. It directs users to a specific building, to a specific floor, and leads them to a specific book. With the renovation of Lilly Library fast approaching, Duke University Libraries Technical Services began exploring ways to leverage library metadata to facilitate the move of the collection from one location to multiple temporary locations.
For the Technical Services Team, preparing the Lilly Library collection for relocation translated into assessing its level of readiness, identifying and addressing gaps, remapping the collection to temporary quarters, and facilitating the return of the collection to its newly renovated spaces.
Addressing the Gaps
The good news is that the metadata, linking patrons to the Lilly Library collection, was in remarkably better shape than that of previous renovation projects. Much of the credit for this state of readiness goes to the Lilly Team. While there were a few issues that required our attention, the even better news is that much of this work could be automated.
Smart Barcoding
One of the questions to be answered was, "how many items in the collection lack a barcode?" A review of an Aleph report revealed that only 6,000 volumes were unbarcoded. Employing the use of smart barcodes would provide the most efficient means of addressing this task. Unlike the generic barcode used at the point of cataloging, a smart barcode label contains a call number and a title. The application of the barcode is done by hand and the records in our ILS (Aleph) are updated in batch using an automated process.
With an Aleph report of unbarcoded volumes as our starting point, we contracted the services of Watson Label Products to produce the labels and supply a file with smart barcode numbers matched to our system-generated ("Dummy") barcodes. Once the file was received, we worked with Library Systems and Integration Support (LSIS) to develop a script to replace the system-generated barcodes with the smart barcodes. The barcode labels arrived in sheets of 150 barcodes each, arranged in call number order, with bibliographic information to facilitate matching by the Lilly Team.
Smart Barcode Data File
Spine Label Conflicts
In the process of organizing the data file for smart barcodes, another issue emerged. A small group of Dewey call numbers appeared in the dataset for a collection that has no books labeled in Dewey. The "In-Process LC" status in these records pointed to the LC Reclassification Project as the culprit. From 2004-2008, DUL embarked on a project to convert 2.3 million volumes from Dewey to LC classification. An automated process designed to copy the vendor-supplied LC call number from the bibliographic record to the holdings record had failed.
Typically, these problems are sent to Technical Services for resolution one-by-one. At this juncture, was an automated approach even possible? Some bibliographic records can contain more than one LC call number. How could we proceed with confidence that the one selected in an automated process is an exact match to the spine label already on the book? After confirming that every record with an "In-Process LC" status also contained a vendor-supplied LC call number, we turned to the Lilly Team to check the spine labels. With their verification in hand, the next step was easy. We used an existing Aleph Service to fix these spine label conflicts.
The method employed to solve this problem serves as a proof-of-concept that can be applied to all DUL collections that may have legacy Dewey call numbers in their holding records.
Weeding the Collection
The Lilly Team identified approximately 2,000 duplicates to remove from its collection. Out of a desire to retain the copy in the best physical condition, they began the weeding process by retrieving and visually inspecting each copy. The initial review of 160 books resulted in 80 to be withdrawn. A file of the 80 titles was sent to Technical Services for records maintenance and the books were sent to Collection Strategy and Development for disposition.
Our Metadata & Discovery Strategy (MADS) team suspected that library metadata could inform decisions about which copy to withdraw. Would the number of times a book circulated correspond to its physical condition? Could the manual selections made by the Lilly Team be replicated in the data? To answer these questions, we produced a report of circulation history for the 80 pairs of duplicates reviewed by the Lilly Team. MADS found that in 90% of the cases the items with the most circulations showed the greatest level of wear.
Remapping the Collection
From our perspective, we are not only planning on how to assist in moving the collections out of Lilly; we also have to focus on how to get it back post-renovation. When we talk about the "Lilly move" we are really referring to the "Lilly moves" because not all materials are being temporarily located in the same space and they are all coming back. Some materials will be temporarily at the Library Service Center (LSC) off-site repository, some in the Perkins stacks, current periodicals, or the East Asian Collection reference shelves; while others will be in a temporary space on East Campus that we're calling the Satellite location for now. Immediately it became apparent that temporary location codes were needed for both moving the collections and controlling the display for patrons.
Cleaning-Up Collection Codes
In the process of setting up temporary codes for the Lilly collections, one of the earliest activities was defining what the Lilly Collections were, from a metadata perspective. Based on the collection codes in Aleph, we identified the number of materials in each code. We discovered some codes were unused and had no items. We also found a need to collapse multiple codes that served the same purpose, virtually transferring materials from one collection to more appropriate ones.
Part of that work was collaborating with members of the Lilly Team to collapse un-needed collection codes to the more correct codes. In our clean-up we found out that there were codes that didn't serve their intended purpose, so we removed them after updating item metadata. After that, Metadata & Discovery Strategy Department (MADS) staff created temporary codes, determined how they should appear to patrons, and began changing metadata to the temporary codes so that the materials can be shipped. We worked with the Assessment & User Experience Department to adjust some of the public displays after the Lilly Team determined what those should be. Once the building is empty, MADS staff will have updated all of the collection codes to temporary collection codes with batch processes. This initial clean-up sets the stage for a more complete inventory.
There was some dissonance between intellectual collections, like the graphic novels, and the actual collection codes in use. For example, we think of the graphic novel collection as a separate entity from the rest of the Lilly stacks, but there is no separate collection code (or shelving) for the graphic novels. We just know they are there. So, to get the metadata into shape so that patrons can see where things are during the renovation, and to be able to identify each collection later, temporary location codes were created for each sub-part of what we know as "the Lilly Collection."
Throughout Technical Services, there have been a myriad of other changes to workflows in order to support the operations of the Lilly Library as it undergoes renovation. Some of these changes are temporary, but others are a permanent reflection of our adaptability and flexibility.
Remember the first sentence in this post: "Library metadata does more than connect researchers to library resources?" The Lilly Library renovation can now proceed with confidence that patrons can still explore its rich resources with ease.
Welcome to Signal Boost!
A Different Kind of Exhibit
Introducing Collections Services
Happy National Book Month!
E-Resource Database Trial Accessibility Evaluations
A Day in the Life: Adam Hudnut-Beumler
Signal Boost: Tales From Collections Services


text:
title: "Frequently asked questions"
shortTitle: "FAQ"
date: 2014-12-03
template: article.jade
showInMenu: "true"
linkUrl: "/faq/"
menuOrder: 4
meta:
    keywords: "respoke, webrtc, javascript, FAQs, endpoint, precense, connection, media relay, TURN"
    description: "Frequently asked questions: Respoke documentation for developers."
---

redpajama_set_name: RedPajamaGithub


text:
As COVID-19 cases spike, we need more than PPE
Rich Bluni
Nurses - and the rest of us - must also protect our inspiration in these tough times
Across the U.S., coronavirus infection rates are surging, with no end in sight. If you're a nurse, you may feel like you're sinking, and all the PPE in the world can't protect your spirit.
It's that sense of purpose and meaning, of calling, that keeps nurses — and the rest of us — going in incredibly traumatic times. If we lose touch with that, we can quickly find ourselves in deep trouble.
There are no easy solutions to what we are facing right now. But reconnecting to the sense of mission that has always driven nurses — and others — on a heart-and-soul level can give them the strength to keep going.
That doesn't "just happen" even in good times; it's a choice we must make every day. If we don't, we will quickly get overwhelmed by pain, fear, and negativity.
Hard times can deeply inspire us if we make a point of staying open to them, but we have to get intentional about doing so. Here are a few tips for reconnecting with your inspiration when you're struggling:
Take 10 minutes to relive a moment when you made a real difference. At any moment when you're feeling crushed and exhausted, close your eyes and be right back there when you did something incredible. Relive your greatest moment. Your mind doesn't know the difference between it really happening and the memory.
Write down your gratitude. Even in a pandemic, there are things to be grateful for. Maybe a coworker paid for your lunch. Maybe the cafeteria had that carrot cake you love. Charting moments of gratitude (however big or small) helps.
Write down three things about your work that you are thankful for. Each day, look it over and add to your list. You almost cannot be in a state of gratitude and negativity at the same time, but you can choose.
Then, share it with others. Chances are, some of the "things" you find yourself writing on your gratitude list are actually people. Maybe it's the coworker who always jumps in to help, the secretary who steps up when you're swamped, or the food service employee who always remembers your lunch order.
Extend your gratitude to someone every day. Give them a thank-you note or tell them face-to-face — even if it has to be from 6 feet away while wearing full PPE. Not only will you feel better, you'll help others feel better at a time when most likely they really need it.
Make a self-care plan. Get out a journal and write the following labels on five separate pages: Mind, Body, Spirit, Love and Prosperity. Under each title, come up with just two things that you can do every day that would impact that part of your being. In the "Body" category, you may write, "walk a mile," "eat more green veggies," and "drink eight glasses of water." It may feel strange to focus on improving your life when the world seems to be falling apart, but now is when we need to be at our best.
Get intentional about who you spend time with. Who do you chat with on breaks? Who do you vent to when times are tough? Often, we don't make these decisions consciously. The problem is, we might be hanging out with psychic vampires who drain our life force and break us down with their negativity.
Your two most valuable resources are your love and your time. So if you're spending them on people who spread fear, or hold grudges, or don't act in ways that are kind and compassionate, I encourage you to become more intentional about your relationships. The company you keep has a big impact on your attitude and well-being.
Realize that you don't rent your life, you own it. Do you let bad situations and other people's negativity dictate how you feel about your work life? If you do, then you're renting.
You can't wait around for someone to rescue you or to fix how you feel. Start by practicing gratitude and improving yourself. Connect with other people every chance you get. Opportunities to do so exist around each corner in healthcare. Look for inspiration today. Look for ways to give. Own your life — especially right now.
It's when times are toughest that we learn the most valuable lessons and experience the biggest leaps in our personal growth.
Rich Bluni has been a registered nurse since 1993
NEW Small Business Cash Relief!
The Columbia County Economic Team has small business grants available to qualifying businesses.
New! Small Business Cash Relief!
The Columbia County Economic Team, Columbia Pacific Economic Development District and Business Oregon just announced a fresh, new grant fund to…
Dynamite Times
Brought to you by Eric Dahlgren - Dahlgren's Do-It-Best - BUILDING SUPPLY INSIDER
Dahlgren's: Thank you, customers!
We're here for you and your spring projects, and we've still got chicks!
Dahlgren's is open

redpajama_set_name: RedPajamaCommonCrawl


text:
The Next Corvette
Our fearless predictions for the upcoming C6.
Csaba Csere Published: Jul 1, 2002
Prying information about future Corvettes from chief engineer and vehicle line executive Dave Hill is tougher than persuading Rush Limbaugh to endorse Al Sharpton for president. But during the presentation of a 10Best award to Chevrolet a few months ago, we chatted about the current car and the areas in which it might be improved. Coupled with a few rumors leaking from various suppliers, as well as some design details gleaned from our moles deep within the GM maze, we're ready to take a whack at predicting the form and focus of the upcoming C6.
For starters, the C6 is coming soon. Although the C3 dragged on from 1968 through 1982 and the C4 lasted for nearly as long, the C5 will live less than 10 years. In fact, with the Cadillac XLR sports car due to arrive as a 2004 model early next year, we would expect the C6, which will share a platform with the XLR, to arrive no more than 12 months later.
If Hill is anything, he's thoroughly practical, so we do not expect him to change anything on the C5 for the sake of novelty. Therefore, we are confident that the C6's skin will be constructed from fiberglass composite, and we also expect that the C6's chassis and powertrain will not stray terribly far from those of the successful C5 model. After all, the C5's structure, which combines hydroformed steel side rails, cast aluminum subframes, steel rollover hoops, and a stamped steel backbone, is both rigid and light. Similarly, we expect only evolutionary changes in the control-arm front and multilink rear suspensions. Both will likely remain aluminum and continue to use compact and light transverse leaf springs. Naturally, we expect widespread use of the Magnetic Selective Ride Control shock absorbers found in the 50th-anniversary car.
Since the C5 has garnered tremendous praise for its excellent luggage capacity, we would also expect the new car to continue without a spare. But it remains to be seen whether this will be achieved with a Goodyear EMT run-flat tire or a different approach, such as the Michelin-developed Pax System that employs special rims and a separate internal liner.
When queried about future Corvette engines, Hill clams up like Hillary when asked about Monica, but other sources confirm that the C6 energizer will remain-what else?-a small-block Chevy V-8 with pushrods. But we keep hearing about a displacement increase from the present 5.7 liters to about 6.3. Of necessity, this will be achieved via a longer stroke, although if GM Powertrain can find a cost-effective way to eliminate the aluminum V-8's iron cylinder liners, a small bore increase could also contribute.
To enhance the bigger engine's deeper breathing, we hear persistent rumors about separate intake and exhaust camshafts-both in the block. This concept, which debuted in the Opel Signum2 concept at last year's Frankfurt show, allows the use of variable valve timing. The Signum2's V-8 also sported dual intake valves per cylinder and selective cylinder deactivation. If all this technology makes it into the C6, expect no less than 450 horsepower and 450 pound-feet of torque with fuel economy equal to, or better than, the C5's.
Hill won't talk about the next generation's styling, either. But by jumping to conclusions based on his veiled references, in addition to incorporating information gleaned from our spies, we've conjured up the illustration shown here.
Hill would dearly like to sell more Corvettes in Europe, where the car has been criticized for being too bulky. Therefore, the sketch responds with a slightly shorter and narrower car than the C5. And although he bridles when he hears it, Hill has acknowledged some criticism that the C5 looks a bit subdued when compared with its more bodacious predecessors. Assuming he plans to address this issue, we've endowed our sketch with a more curvaceous and sharply defined fender line. We've also grafted on fixed headlights that will save weight and simplify the car-both being Hill priorities-even though they would make the C6 the first Corvette without hideaway lights since the '62 model. We reckon the money saved by eliminating the folding mechanisms would easily pay for sophisticated high-intensity-discharge projector-beam lights.
In addition to achieving the predictions we've mapped out for him here, Hill also has to maintain the C5's excellent drag coefficient, plentiful interior space for passengers, and reasonable price, and try to upgrade the Rubbermaid interior. In a couple years, we'll see how well he's done.


15.04.010 Standards applicable to building.
15.04.020 Adoption of state codes.
15.04.030 City administration of codes.
A. The City hereby adopts and enforces the most current edition of the State of Oregon Specialty Codes per ORS 455 and the rules and statutes adopted thereunder.
B. The City adopts and enforces all Appendices of the Oregon Structural Specialty Code.
C. Building and related activities shall comply with the most recently adopted State of Oregon Specialty Codes, including the Building, Mechanical, Plumbing and Electrical Codes, adopted by the Director of the Oregon Department of Commerce and the Fire and Life Safety Code Standards adopted by the State Fire Marshal, as these codes apply at the time of the building or related activity. No person may undertake building or related activities without compliance with these codes.
15.08.030 Design Review Board established.
15.12.040 Application—Statement of agreement not to damage property.
15.12.050 Notification of nearby property owners—Public hearing when.
15.12.060 Notification of public hearing—Decision of Council.
15.12.080 Bond or insurance policy.
15.12.090 Approval of permit by chief of police, building inspector and City Council.
15.12.100 City engineer—Approval of equipment and route.
15.12.110 Moving to be continuous—Exceptions.
15.12.120 Special requirements for hours of darkness.
15.12.130 Permit contents—Mode, route, expiration date, restrictions.
15.12.150 Failure to remove building—Separate violation.
Such other information as the City Recorder, city building inspector or city engineer may deem necessary.
For buildings in floor area of one thousand (1,000) square feet or more, fifty dollars ($50.00) plus five cents ($.05) for each additional square foot in excess of one thousand (1,000).
A. No permit shall be issued until the application shall be approved by the chief of police, the building inspector, and in case of a structure other than wood frame or in excess of two thousand five hundred (2,500) square feet, the City Council.
B. The chief of police shall consider the probable effect of the proposed moving on the public safety and he shall approve the application for moving only where such moving will not jeopardize the public safety and the route proposed or finally adopted is the one least dangerous to the citizens of the city and the general public.
The building to be moved shall be located and used in a manner consistent with all zoning and land use ordinances of the city, together with any other applicable ordinances, laws or governmental regulations.
The buildings shall be similar to the other buildings in the immediate vicinity in size, age, architectural style and structural condition so as to be compatible with other buildings in the areas and so as not to cause property in the areas to decrease in value.
15.16.060 Parking of recreational vehicle outside RV park prohibited—Exception.
15.16.070 Compliance with city, county and state regulations required.
"Manager" means the City Manager or his/her designee.
"Manufactured home" means a structure constructed for movement on public highways that has sleeping, cooking, and plumbing facilities, that is intended for human occupancy, that is being used for residential purposes and that was constructed in accordance with federal manufactured housing construction and safety standards and regulations in effect at the time of construction. "Manufactured home" does not mean any building or structure constructed to conform to the State of Oregon Structural Specialty Code or the One and Two Family Dwelling Code adopted pursuant to ORS 455.100 to 455.450 and 455.61 to 455.630 or any unit identified as a recreational vehicle by the manufacturer.
"Manufactured home or RV space" means a plot of ground within a manufactured home or RV park designed for the accommodation of one living unit.
"Manufactured home park" also "recreational vehicle park" referred to as "park" herein, means any lot or parcel of land upon which one or more mobile homes, used for dwelling or sleeping purposes are located for generally more than a 30 day period, regardless of whether or not a charge is made for such accommodation.
"Person" means any natural individual, firm, co-partnership, association or corporation.
Sufficient information to indicate compliance with all other requirements of this chapter and the State Board of Health.
15.20.030 Determination of areas of special flood hazard and application.
15.20.040 Designation of program Manager.
15.20.050 Duties and responsibilities of the program Manager.
15.20.060 Development permit, application procedure and establishment.
"Area of special flood hazard" means the land in the floodplain within the city of Wood Village subject to a one percent or greater chance of flooding in any given year.
"Base flood" means the flood having a one percent chance of being equaled or exceeded in any given year.
"Development" means any man-made change to improved or unimproved real estate, including but not limited to buildings or other structures, mining, dredging, filling, paving, excavation or drilling operations located within the area of special flood hazard.
"Flood Hazard Boundary Map (FHBM)" means the official map issued by the Federal Insurance Administration where the areas of special flood hazard have been designated Zone A.
"Habitable floor" means any floor usable for living purposes, which includes working, sleeping, eating, cooking or recreation, or a combination thereof. A floor used only for storage purposes is not a habitable floor.
"Mobile home" means a structure that is transportable in one or more sections, built on a permanent chassis, and designed to be used with or without a permanent foundation when connected to the required utilities. It does not include recreational vehicles or travel trailers.
"Structure" means a walled and roofed building, a mobile home, or a gas or liquid storage tank, that is principally above ground.
A. The provisions of this chapter shall apply to all areas designated as areas of special flood hazard by the Federal Insurance Administration on its current Flood Hazard Boundary Map (FHBM), applicable to and including all areas within the boundaries of the city.
B. The current Federal Insurance Administration (FHBM) No. 410185, dated October 31, 1975, marked Exhibit "A" and attached to the ordinance codified in this chapter and on file in the City Recorder's office, is by this reference made a part hereof as if fully set forth herein at this point.
C. In recognition of the fact that the Federal Insurance Administration may from time to time revise the FHBM applicable to the city or that additional map or maps may be required for identification of flood hazard areas due to annexations or other land acquisitions by the city, the City Council shall have authority upon receipt of due notice by appropriate agency of the United States Government, to substitute, add and/or subtract appropriate FHBM maps by appropriate resolution, making the same applicable hereto.
A. The program Manager shall administer, implement and enforce the rules and regulations, intent and purposes of this chapter, which shall include the preparation and approval of appropriate forms and applications, and information and materials necessary to carry out the same.
B. The PA or his duly designated assistant shall review and consider, and in appropriate instances, approve all applications for development permit as herein provided.
Determine if the proposed development adversely affects the flood carrying capacity of the area of special flood hazard. (For the purposes of this chapter, "adversely affects" means damage to adjacent properties because of rises in flood stages attributed to physical changes of the channel and the adjacent overbank areas).
a. If by such review, the PA shall determine that there is no adverse affect or no adverse affect of consequence as addressed by this chapter, then a development permit may be granted consistent with the provisions of this chapter.
b. If the PA determines that there is an adverse affect, of a material nature, then flood damage mitigation measures shall be made a condition of the permit.
Maintain for public inspection all the records pertaining to the provisions of this chapter.
E. The PA shall notify adjacent communities (and the state coordinating agency, if any) prior to any alteration or relocation of a watercourse, and submit evidence of such notification to the Federal Insurance Administration.
F. The PA shall require that maintenance is provided within the altered or relocated portion of said watercourse so that the flood carrying capacity is not diminished.
A. A development permit shall be obtained before construction or development begins within any area of special flood hazard as established in Section 15.20.030.
All new construction and substantial improvements shall be anchored to prevent floatation, collapse, or lateral movement of the structure.
d. Any additions to the mobile home be similarly anchored.
B. Construction Materials and Methods.
Base flood elevation data shall be provided for subdivision proposals and other proposed development which contain at least fifty (50) lots or five acres, whichever is less.
A. Residential Construction. New construction and substantial improvement of any residential structure shall have the lowest floor, including basement, elevated to or above the base flood elevation.
In the event any building or structure is, or is proposed to be erected, constructed, altered, maintained or used, or any land is, or is proposed to be used in violation of any provision of this chapter, the proper city officials or their duly authorized representatives or any person whose interest in real property in the city is or may be affected by the violation, may, in addition to other remedies provided by law, institute injunction, mandamus, abatement or any other appropriate proceeding to prevent temporarily or permanently enjoin, abate or remove such unlawful erection, construction, reconstruction, alteration, maintenance or use.
This stormwater runoff contributes to increased quantities of water-borne pollutants, and; stormwater runoff, soil erosion and nonpoint source pollution can be controlled and minimized through the regulation of stormwater runoff from development sites.
Therefore, the City establishes this set of water quality and quantity policies applicable to all surface waters to provide reasonable guidance for the regulation of stormwater runoff for the purpose of protecting local water resources from degradation. It is determined that the regulation of stormwater runoff discharges from land development projects and other construction activities in order to control and minimize increases in stormwater runoff rates and volumes, soil erosion, stream channel erosion, and nonpoint source pollution associated with stormwater runoff is in the public interest and will prevent threats to public health and safety.
reduce stormwater runoff rates and volumes, soil erosion and nonpoint source pollution, wherever possible, through stormwater management controls and to ensure that these management controls are properly maintained and pose no threat to public safety.
This ordinance shall be applicable to all subdivision or site plan applications, unless eligible for an exemption or granted a waiver by the City under the specifications of Section 4 of this ordinance. The ordinance also applies to land development activities that are smaller than the minimum applicability criteria if such activities are part of a larger common plan of development that meets the following applicability criteria, even though multiple separate and distinct land development activities may take place at different times on different schedules. In addition, all plans must also be reviewed by local environmental protection officials to ensure that established water quality standards will be maintained during and after development of the site and that post construction runoff levels are consistent with any local and regional watershed plans.
Repairs to any stormwater treatment practice deemed necessary by the City.
When a site development plan is submitted that qualifies as a redevelopment project as defined in Section 2 of this ordinance, decisions on permitting and on-site stormwater requirements shall be governed by special stormwater sizing criteria found in the current stormwater design manual. This criteria is dependent on the amount of impervious area created by the redevelopment and its impact on water quality. Final authorization of all redevelopment projects will be determined after a review by the City.
This ordinance is not intended to interfere with, abrogate, or annul any other ordinance, rule or regulation, stature, or other provision of law. The requirements of this ordinance should be considered minimum requirements, and where any provision of this ordinance imposes restrictions different from those imposed by any other ordinance, rule or regulation, or other provision of law, whichever provisions are more restrictive or impose higher protective standards for human health or the environment shall be considered to take precedence.
If the provisions of any article, section, subsection, paragraph, subdivision or clause of this ordinance shall be judged invalid by a court of competent jurisdiction, such order of judgment shall not affect or invalidate the remainder of any article, section, subsection, paragraph, subdivision or clause of this ordinance.
The City has adopted the City of Portland's Stormwater Design Manual yet may furnish additional policy, criteria and information including specifications and standards, for the proper implementation of the requirements of this ordinance and may provide other such information. This manual will include a list of acceptable stormwater treatment practices, including the specific design criteria and operation and maintenance requirements for each stormwater practice. The manual may be updated and expanded from time to time, at the discretion of the local review authority, based on improvements in engineering, science, monitoring and local maintenance experience. Stormwater treatment practices that are designed and constructed in accordance with these design and sizing criteria will be presumed to meet the minimum water quality performance standards. Where the City's policies and the Stormwater Design Manual are in conflict, the City's policies will take precedence.
"Accelerated Erosion" means erosion caused by development activities that exceeds the natural processes by which the surface of the land is worn away by the action of water, wind, or chemical action.
"Applicant" means a property owner or agent of a property owner who has filed an application for a stormwater management permit.
"Building" means any structure, either temporary or permanent, having walls and a roof, designed for the shelter of any person, animal, or property, and occupying more than 100 square feet of area.
"Channel" means a natural or artificial watercourse with a definite bed and banks that conducts continuously or periodically flowing water.
"City" means the City of Wood Village, Oregon.
"City Manager" means the City Manager of Wood Village, Oregon, or the City Manager's Designee.
"Dedication" means the deliberate appropriation of property by its owner for general public use.
"Detention" means the temporary storage of storm runoff in a stormwater management practice with the goals of controlling peak discharge rates and providing gravity settling of pollutants.
"Detention Facility" means a detention basin or alternative structure designed for the purpose of temporary storage of stream flow or surface runoff and gradual release of stored water at controlled rates.
"Developer" means a person who undertakes land disturbance activities.
"Drainage Easement" means a legal right granted by a landowner to a grantee allowing the use of private land for stormwater management purposes.
"Erosion and Sediment Control Plan" means a plan that is designed to minimize the accelerated erosion and sediment runoff at a site during construction activities.
"Fee in Lieu" means a payment of money in place of meeting all or part of the storm water performance standards required by this ordinance.
"Hotspot" means an area where land use or activities generate highly contaminated runoff, with concentrations of pollutants in excess of those typically found in stormwater.
"Hydrologic Soil Group (HSG)" means a Natural Resource Conservation Service classification system in which soils are categorized into four runoff potential groups. The groups range from A soils, with high permeability and little runoff production, to D soils, which have low permeability rates and produce much more runoff.
"Impervious Cover" means those surfaces that cannot effectively infiltrate rainfall (e.g., building rooftops, pavement, sidewalks, driveways, etc).
"Industrial Stormwater Permit" means an National Pollutant Discharge Elimination System permit issued to a commercial industry or group of industries which regulates the pollutant levels associated with industrial stormwater discharges or specifies on-site pollution control strategies.
"Infiltration" means the process of percolating stormwater into the subsoil.
"Infiltration Facility" means any structure or device designed to infiltrate retained water to the subsurface. These facilities may be above grade or below grade.
"Jurisdictional Wetland" means an area that is inundated or saturated by surface water or groundwater at a frequency and duration sufficient to support a prevalence of vegetation typically adapted for life in saturated soil conditions, commonly known as hydrophytic vegetation.
"Land Disturbance Activity" means any activity which changes the volume or peak flow discharge rate of rainfall runoff from the land surface. This may include the grading, digging, cutting, scraping, or excavating of soil, placement of fill materials, paving, construction, substantial removal of vegetation,, or any activity which bares soil or rock or involves the diversion or piping of any natural or man-made watercourse.
"Landowner" means the legal or beneficial owner of land, including those holding the right to purchase or lease the land, or any other person holding proprietary rights in the land.
"Maintenance Agreement" means a legally recorded document that acts as a property deed restriction, and which provides for long-term maintenance of storm water management practices.
"Nonpoint Source Pollution" means pollution from any source other than from any discernible, confined, and discrete conveyances, and shall include, but not be limited to, pollutants from agricultural, silvicultural, mining, construction, subsurface disposal and urban runoff sources.
"Offset Fee" means a monetary compensation paid to a local government for failure to meet pollutant load reduction targets.
"Off-Site Facility" means a stormwater management measure located outside the subject property boundary described in the permit application for land development activity.
"On-Site Facility" means a stormwater management measure located within the subject property boundary described in the permit application for land development activity.
"Recharge" means the replenishment of underground water reserves. "Redevelopment" means any construction, alteration or improvement exceeding square feet in areas where existing land use is high density commercial, industrial, institutional or multi-family residential.
"Redevelopment" means any construction, alteration or improvement exceeding square feet in areas where existing land use is high density commercial, industrial, institutional or multi-family residential.
"Stop Work Order" means an order issued which requires that all construction activity on a site be stopped.
"Storm Water Management" means the use of structural or non-structural practices that are designed to reduce storm water runoff pollutant loads, discharge volumes, and/or peak flow discharge rates.
"Storm Water Retrofit" means a stormwater management practice designed for an existing development site that previously had either no stormwater management practice in place or a practice inadequate to meet the stormwater management requirements of the site.
"Stormwater Runoff" means flow on the surface of the ground, resulting from precipitation.
"Stormwater Treatment Practices (STPs)" means measures, either structural or nonstructural, that are determined to be the most effective, practical means of preventing or reducing point source or nonpoint source pollution inputs to stormwater runoff and water bodies.
"Water Quality Volume (WQv)" means the storage needed to capture and treat 90% of the average annual stormwater runoff volume. Numerically (WQv) will vary as a function of long term rainfall statistical data.
"Watercourse" means a permanent or intermittent stream or other body of water, either natural or man-made, which gathers or carries surface water.
No land owner or land operator shall receive any of the building, grading or other land development permits required for land disturbance activities without first meeting the requirements of this ordinance prior to commencing the proposed activity.
Unless specifically excluded by this ordinance, any land owner or operator desiring a permit for a land disturbance activity shall submit development a permit application on a form provided for that purpose.
Unless otherwise excepted by this ordinance, a permit application must be accompanied by the following in order that the permit application be considered: a stormwater management concept plan; a maintenance agreement; and a non-refundable permit review fee.
The stormwater management plan shall be prepared to meet the requirements of Sec. 5 of this ordinance, the maintenance agreement shall be prepared to meet the requirements of Sec. 9 of this ordinance, and fees shall be those established by the City.
The fee for review of any land development application shall be based on the amount of land to be disturbed at the site, and the fee structure shall be established by the City. All of the monetary contributions shall be credited to a local budgetary category to support local plan review, inspection and program administration, and shall be made prior to the issuance of any building permit for the development.
Applications for land disturbance activity permits must be filed with the City on any regular business day.
Within business days of the receipt of a complete permit application, including all documents as required by this ordinance, the City shall inform the applicant whether the application, plan and maintenance agreement are approved or disapproved.
If the permit application, stormwater management plan or maintenance agreement are disapproved, the applicant may revise the stormwater management plan or agreement. If additional information is submitted, the City shall have seven (7) business days from the date the additional information is received to inform the applicant that the plan and maintenance agreement are either approved or disapproved.
If the permit application, final stormwater management plan and maintenance agreement are approved by the City, all appropriate land disturbance activity permits shall be issued.
Permits issued under this section shall be valid from the date of issuance through the date the City notifies the permit holder that all stormwater management practices have passed the final inspection required under permit condition.
Every applicant shall provide for stormwater management as required by this ordinance, unless a written request is approved to waive this requirement. Requests to waive the stormwater management plan requirements shall be submitted to the ODEQ and the City for approval.
It can be demonstrated that the proposed development is not likely to impair attainment of the objectives of this ordinance.
Alternative minimum requirements for on-site management of stormwater discharges have been established in a stormwater management plan that has been approved by the ODEQ and the City and the implementation of the plan is required by local ordinance.
The ODEQ and the City finds that meeting the minimum on-site management requirements is not feasible due to the natural or existing physical characteristics of a site.
Non-structural practices will be used on sites that reduce: a) the generation of stormwater from the site, b) the size and cost of stormwater storage and c) the pollutants generated at the site. These non-structural practices are explained in detail in the current design manual and the amount of credit available for using such practices shall be determined by the ODEQ and the City.
Where the City waives all or part of the minimum stormwater management requirements, or where the waiver is based on the provision of adequate stormwater facilities provided downstream of the proposed development, the applicant shall be required to pay a fee in an amount as determined by the City. When an applicant obtains a waiver of the required stormwater management, the monetary contribution required shall be in accordance with a fee schedule (unless the developer and the stormwater authority agree on a greater alternate contribution) established by the City, and based on the cubic feet of storage required for stormwater management of the development in question. All of the monetary contributions shall be credited to an appropriate capital improvements program project, and shall be made by the developer prior to the issuance of any building permit for the development.
In lieu of a monetary contribution, an applicant may obtain a waiver of the required stormwater management by entering into an agreement with the City for the granting of an easement or the dedication of land by the applicant, to be used for the construction of an off-site stormwater management facility. The agreement shall be entered into by the applicant and the City prior to the recording of plats or, if no record plat is required, prior to the issuance of the building permit.
A. All site designs shall establish stormwater management practices to control the peak flow rates of stormwater discharge associated with specified design storms and reduce the generation of stormwater. These practices should seek to utilize pervious areas for stormwater treatment and to infiltrate stormwater runoff from driveways, sidewalks, rooftops, parking lots, and landscaped areas to the maximum extent practical to provide treatment for both water quality and quantity.
B. All stormwater runoff generated from new development shall not discharge untreated stormwater directly into a jurisdictional wetland or local water body without adequate treatment. Where such discharges are proposed, the impact of the proposal on wetland functional values shall be assessed using a method acceptable to the ODEQ and the City. In no case shall the impact on functional values be any less than allowed by the Army Corp of Engineers (ACE) or ODEQ responsible for natural resources.
C. Annual groundwater recharge rates shall be maintained, by promoting infiltration through the use of structural and non-structural methods. At a minimum, annual recharge from the post development site shall mimic the annual recharge from pre-development site conditions.
sized to capture the prescribed water quality volume (WQv).
E. Stormwater discharges to critical areas with sensitive resources (i.e., cold water fisheries, shellfish beds, swimming beaches, recharge areas, water supply reservoirs) may be subject to additional performance criteria, or may need to utilize or restrict certain stormwater management practices.
F. Certain industrial sites are required to prepare and implement a stormwater pollution prevention plan, and shall file a notice of intent (NOI) under the provisions of the National Pollutant Discharge Elimination System (NPDES) general permit. The stormwater pollution prevention plan requirement applies to both existing and new industrial sites.
G. Stormwater discharges from land uses or activities with higher potential pollutant loadings, known as "hotspots", may require the use of specific structural STPs and pollution prevention practices.
H. Prior to design, applicants are required to consult with the ODEQ and the City to determine if they are subject to additional stormwater design requirements.
I. The calculations for determining peak flows as found in the Stormwater Design Manual shall be used for sizing all stormwater management practices.
All stormwater management practices will be designed so that the specific storm frequency storage volumes (e.g., recharge, water quality, channel protection, 10 year, 100 year) as identified in the current stormwater design manual are met, unless the City grants the applicant a waiver or the applicant is exempt from such requirements.
In addition, if hydrologic or topographic conditions warrant greater control than that provided by the minimum control requirements, the City reserves the right to impose any and all additional requirements deemed necessary to control the volume, timing, and rate of runoff.
All stormwater management practices shall be designed to capture and treat stormwater runoff according to the specifications outlined in the Stormwater Design Manual. These specifications will designate the water quantity and quality treatment criteria that apply to an approved stormwater management practice.
All stormwater management practices must have a landscaping plan detailing both the vegetation to be in the practice and how and who will manage and maintain this vegetation. This plan must be prepared by a registered landscape architect or soil conservation district.
All stormwater treatment practices shall have an enforceable operation and maintenance agreement to ensure the system functions as designed. This agreement will include any and all maintenance easements required to access and inspect the stormwater treatment practices, and to perform routine maintenance as necessary to ensure proper functioning of the stormwater treatment practice. In addition, a legally binding covenant specifying the parties responsible for the proper maintenance of all stormwater treatment practices shall be secured prior to issuance of any permits for land disturbance activities.
The use of non-structural stormwater treatment practices is encouraged in order to minimize the reliance on structural practices. Credit in the form of reductions in the amount of stormwater that must be managed can be earned through the use of non-structural practices that reduce the generation of stormwater from the site. These non-structural practices are explained in detail in the current design manual and applicants wishing to obtain credit for use of non-structural practices must ensure that these practices are documented and remain unaltered by subsequent property owners.
No application for development will be approved unless it includes a stormwater management plan detailing in concept how runoff and associated water quality impacts resulting from the development will be controlled or managed. This plan must be prepared by an individual approved by the City and must indicate whether stormwater will be managed on-site or off-site and, if on-site, the general location and type of practices. The stormwater management plan(s) shall be referred for comment to all other interested agencies, and any comments must be addressed in a final stormwater management plan. This final plan must be signed by a licensed professional engineer (PE), who will verify that the design of all stormwater management practices meet the submittal requirements outlined in the Submittal Checklist found in the stormwater design manual. No building, grading, or sediment control permit shall be issued until a satisfactory final stormwater management plan, or a waiver thereof, shall have undergone a review and been approved by the City after determining that the plan or waiver is consistent with the requirements of this ordinance.
A map (or maps) indicating the location of existing and proposed buildings, roads, parking areas, utilities, structural stormwater management and sediment control facilities. The map(s) will also clearly show proposed land use with tabulation of the percentage of surface area to be adapted to various uses; drainage patterns; locations of utilities, roads and easements; the limits of clearing and grading; a written description of the site plan and justification of proposed changes in natural conditions may also be required.
Sufficient engineering analysis to show that the proposed stormwater management measures are capable of controlling runoff from the site in compliance with this ordinance and the specifications of the Stormwater Design Manual.
A written description of the required maintenance burden for any proposed stormwater management facility.
The City may also require a concept plan to consider the maximum development potential of a site under existing zoning, regardless of whether the applicant presently intends to develop the site to its maximum potential.
For development or redevelopment occurring on a previously developed site, an applicant shall be required to include within the stormwater concept plan measures for controlling existing stormwater runoff discharges from the site in accordance with the standards of this Ordinance to the maximum extent practicable.
The name, address, and telephone number of all persons having a legal interest in the property and the tax reference number and parcel number of the property or properties affected.
A 1″ = 200′ topographic base map of the site which extends a minimum of 100 feet beyond the limits of the proposed development and indicates existing surface water drainage including streams, ponds, culverts, ditches, and wetlands; current land use including all existing structures; locations of utilities, roads, and easements; and significant natural and manmade features not otherwise shown.
Hydrologic and hydraulic design calculations for the pre-development and post-development conditions for the design storms specified in this ordinance. Such calculations shall include (i) description of the design storm frequency, intensity and duration, (ii) time of concentration, (iii) Soil Curve Numbers or runoff coefficients, (iv) peak runoff rates and total runoff volumes for each watershed area, (v) infiltration rates, where applicable, (vi) culvert capacities, (vii) flow velocities, (viii) data on the increase in rate and volume of runoff for the design storms referenced in the Stormwater Design Manual, and (ix) documentation of sources for all computation methods and field test results.
If a stormwater management control measure depends on the hydrologic properties of soils (e.g., infiltration basins), then a soils report shall be submitted. The soils report shall be based on on-site boring logs or soil pit profiles. The number and location of required soil borings or soil sits shall be determined based on what is needed to determine the suitability and distribution of soil types present at the location of the control measure.
The design and planning of all stormwater management facilities shall include detailed maintenance and repair procedures to ensure their continued function. These plans will identify the parts or components of a stormwater management facility that need to be maintained and the equipment and skills or training necessary. Provisions for the periodic review and evaluation of the effectiveness of the maintenance program and the need for revisions or additional maintenance procedures shall be included in the plan.
The applicant must present a detailed plan for management of vegetation at the site after construction is finished, including who will be responsible for the maintenance of vegetation at the site and what practices will be employed to ensure that adequate vegetative cover is preserved. This plan must be prepared by a registered landscape architect or by the soil conservation district.
The applicant must ensure access to all stormwater treatment practices at the site for the purpose of inspection and repair by securing all the maintenance easements needed on a permanent basis. These easements will be recorded with the plan and will remain in effect even with transfer of title to the property.
The applicant must execute an easement and an inspection and maintenance agreement binding on all subsequent owners of land served by an on-site stormwater management measure in accordance with the specifications of this ordinance.
The applicant must prepare an erosion and sediment control plan for all construction activities related to implementing any on-site stormwater management practices.
The City may, at its discretion, require the submittal of a performance security or bond prior to issuance of a permit in order to insure that the stormwater practices are installed by the permit holder as required by the approved stormwater management plan. The amount of the installation performance security shall be the total estimated construction cost of the stormwater management practices approved under the permit, plus 25%. The performance security shall contain forfeiture provisions for failure to complete work specified in the stormwater management plan. The installation performance security shall be released in full only upon submission of "as built plans" and written certification by a registered professional engineer that the stormwater practice has been installed in accordance with the approved plan and other applicable provisions of this ordinance. The City will make a final inspection of the stormwater practice to ensure that it is in compliance with the approved plan and the provisions of this ordinance. Provisions for a partial pro-rata release of the performance security based on the completion of various development stages can be done at the discretion of the City.
All applicants are required to submit actual "as built" plans for any stormwater management practices located on-site after final construction is completed. The plan must show the final design specifications for all stormwater management facilities and must be certified by a professional engineer. A final inspection by the City is required before the release of any performance securities can occur.
Reseeding must be done with an annual or perennial cover crop accompanied by placement of straw mulch or its equivalent of sufficient coverage to control erosion until such time as the cover crop is established over ninety percent (90%) of the seeded area.
Any area of revegetation must exhibit survival of a minimum of seventy-five percent (75%) of the cover crop throughout the year immediately following revegetation. Revegetation must be repeated in successive years until the minimum seventy-five percent (75%) survival for one (1) year is achieved.
In addition to the above requirements, a landscaping plan must be submitted with the final design describing the vegetative stabilization and management techniques to be used at a site after construction is completed. This plan will explain not only how the site will be stabilized after construction, but who will be responsible for the maintenance of vegetation at the site and what practices will be employed to ensure that adequate vegetative cover is preserved. This plan must be prepared by a registered landscape architect or by the soil conservation district, and must be approved prior to receiving a permit.
Prior to the issuance of any permit that has an stormwater management facility as one of the requirements of the permit, the applicant or owner of the site must execute a maintenance easement agreement that shall be binding on all subsequent owners of land served by the stormwater management facility. The agreement shall provide for access to the facility at reasonable times for periodic inspection by the City, or their contractor or agent, and for regular or special assessments of property owners to ensure that the facility is maintained in proper working condition to meet design standards and any other provisions established by this ordinance. The easement agreement shall be recorded by the City in the land records.
Maintenance of all stormwater management facilities shall be ensured through the creation of a formal maintenance covenant that must be approved by the City and recorded into the land record prior to final plan approval. As part of the covenant, a schedule shall be developed for when and how often maintenance will occur to ensure proper function of the stormwater management facility. The covenant shall also include plans for periodic inspections to ensure proper performance of the facility between scheduled cleanouts. The City, in lieu of an maintenance covenant, may accept dedication of any existing or future stormwater management facility for maintenance, provided such facility meets all the requirements of this chapter and includes adequate and perpetual access and sufficient area, by easement or otherwise, for inspection and regular maintenance.
All stormwater management facilities must undergo, at the minimum, an annual inspection to document maintenance and repair needs and ensure compliance with the requirements of this ordinance and accomplishment of its purposes. These needs may include; removal of silt, litter and other debris from all catch basins, inlets and drainage pipes, grass cutting and vegetation removal, and necessary replacement of landscape vegetation. Any maintenance needs found must be addressed in a timely manner, as determined by the City, and the inspection and maintenance requirement may be increased as deemed necessary to ensure proper functioning of the stormwater management facility.
Inspection programs may be established on any reasonable basis, including but not limited to: routine inspections; random inspections; inspections based upon complaints or other notice of possible violations; inspection of drainage basins or areas identified as higher than typical sources of sediment or other contaminants or pollutants; inspections of businesses or industries of a type associated with higher than usual discharges of contaminants or pollutants or with discharges of a type which are more likely than the typical discharge to cause violations of state or federal water or sediment quality standards or the NPDES stormwater permit; and joint inspections with other agencies inspecting under environmental or safety laws. Inspections may include, but are not limited to: reviewing maintenance and repair records; sampling discharges, surface water, groundwater, and material or water in drainage control facilities; and evaluating the condition of drainage control facilities and other stormwater treatment practices.
When any new drainage control facility is installed on private property, or when any new connection is made between private property and a public drainage control system, sanitary sewer or combined sewer, the property owner shall grant to the City the right to enter the property at reasonable times and in a reasonable manner for the purpose of inspection. This includes the right to enter a property when it has a reasonable basis to believe that a violation of this ordinance is occurring or has occurred, and to enter when necessary for abatement of a public nuisance or correction of a violation of this ordinance.
Parties responsible for the operation and maintenance of a stormwater management facility shall make records of the installation and of all maintenance and repairs, and shall retain the records for at least ten (10) years. These records shall be made available to the City during inspection of the facility and at other reasonable times upon request.
If a responsible party fails or refuses to meet the requirements of the maintenance covenant, the City, after reasonable notice, may correct a violation of the design standards or maintenance needs by performing all necessary work to place the facility in proper working condition. In the event that the stormwater management facility becomes a danger to public safety or public health, the City shall notify the party responsible for maintenance of the stormwater management facility in writing. Upon receipt of that notice, the responsible person shall have days to effect maintenance and repair of the facility in an approved manner. After proper notice, the City may assess the owner(s) of the facility for the cost of repair work and any penalties; and the cost of the work shall be a lien on the property, or prorated against the beneficial users of the property, and may be placed on the tax bill and collected as ordinary taxes by the county.
Any development activity that is commenced or is conducted contrary to this Ordinance, may be restrained by injunction or otherwise abated in a manner provided by law.
a statement that the determination of violation may be appealed to the municipality by filing a written notice of appeal within fifteen (15) days of service of notice of violation.
Persons receiving a notice of violation will be required to halt all construction activities. This "stop work order" will be in effect until the City confirms that the development activity is in compliance and the violation has been satisfactorily addressed. Failure to address a notice of violation in a timely manner can result in civil, criminal, or monetary penalties in accordance with the enforcement measures authorized in this ordinance.
In addition to or as an alternative to any penalty provided herein or by law, any person who violates the provisions of this Ordinance shall be punished by a fine of not less than 1,000 Dollars pursuant to Chapter 1.06 of the Wood Village Municipal Code. Such person shall be guilty of a separate offense for each day during which the violation occurs or continues.
Any violator may be required to restore land to its undisturbed condition. In the event that restoration is not undertaken within a reasonable time after notice, the City may take necessary corrective action, the cost of which shall become a lien upon the property until paid.


However, productivity—while a possible byproduct—is not in fact the main benefit of mindfulness in the workplace. According to a metastudy by Daniel Goleman, co-director of the Consortium for Research on Emotional Intelligence in Organizations at Rutgers University, and University of Wisconsin neuroscientist Richard Davidson, there are four tangible and proven benefits from mindfulness training as it applies in the workplace. These include stronger focus, staying calmer under stress, better memory, and good corporate citizenship.
Kosheek Sewchurran is an associate professor and acting director of the University of Cape Town's Graduate School of Business in South Africa.


text:
Gun Nut Shoots Himself In Groin — Not A Great Argument For Concealed Carry
Ursula Faw
From 2015, a man in line in grocery store with gun in waistband. (AP Photo/Cliff Owen)
Blogger Stonekettle has distilled this story down to its essence. Here's his take on it.
"The bullet entered just above his penis and exited his scrotum."
Responsible Gun Owner removes himself from the gene pool. Carrying concealed, no license, no holster, no brains. https://t.co/7x3s3hTvMB
— Stonekettle (@Stonekettle) March 3, 2019
Mark Anthony Jones of Marion, Indiana, did not have a license for the gun he was carrying, nor did he have even a basic idea about safe gun ownership. Apparently, the safety wasn't on, or maybe he turned it off when fumbling with it, because here's what happened.
Marion Police Department issued a news release via Facebook that said Mark Anthony Jones did not have a license for the Hi-Point 9mm gun he was carrying.
Jones, in the emergency room of Marion General Hospital, told police he was walking about 6:44 a.m. Thursday on a riverside trail near the Marion Girl Scout Cabin. That's west of the Washington Street bridge over the Mississinewa River. He said when the gun began to slip from his waistband, he reached to adjust the firearm and it discharged.
"The bullet entered just above his penis and exited his scrotum," the release said.
Hopefully Jones, 46, doesn't want to have any more kids. This is what happens when you watch Clint Eastwood and Tom Cruize and the rest of them effortlessly tuck a gun into a waistband and jump out of a moving car, helicopter, what have you.
Why Jones felt he had to carry a gun to go grocery shopping in a small town in Indiana has not been disclosed at this time. One would think that in a mid-Western town of 28,000, a man could go shopping for Doritos and Bud and be unmolested, but perhaps not.
Liked it? Take a second to support Ursula Faw and PolitiZoom on Patreon!
4 Comments on "Gun Nut Shoots Himself In Groin — Not A Great Argument For Concealed Carry"
Pogoatty
Share On TwitterShare On Google
Aww nuts!
I know. Somebody said a good title would be, gun nut shoots himself in the nuts.
sj a
*From the report, it looks like he was walking on a riverside trail, not grocery shopping–the photo in the grocery store is an example of someone (in 2015) carrying a gun in his waistband, like our hero in your article above. (FYI)
You are correct. I read in another account of this story, that our hero, as you call him, was coming back from a convenience store and walking along the trail. I can see where not citing from that piece and the photo would make for confusion.
Even Lindsey Graham couldn't pull this one off. (With video)


Reads as authentic to me. And I've seen an ad for such services here in the Kansai, resisting the temptation, at least temporarily.
Thought of you b/c I got a can LinkedIn spam in my inbox this a.m. Whoa boy! Alabama slammer!? Good to see you've landed on your feet. Guess having come and gone once before, that reverse culture shock stings a bit less the second time. Good luck and let me know if you're ever in this area.


Press the 'PrtScn' key – this copies the image to the clipboard. You can now paste it into a program.
To copy only the front window, press and hold down 'Alt' then 'PrtScn' – – this copies the image to the clipboard. You can now paste it into a program.
To save the image – press and hold down the 'Windows logo key' then 'PrtScn'. The image will be placed in a 'Screenshots' folder within your 'Pictures' folder.
You can also use 'Snipping Too'. Click here for instructions.
'Right click' on the desktop.
'Log off' and then sign back in.
There is also a 'slider' for selecting a size in between or larger those options.
I, and perhaps you, started using DOS and Windows a LONG time ago and seen a lot of change. The earliest version of DOS (in this DOS timeline) that I remember is 3.1. You?
In Windows 8, the familiar 'Control Panel' was replaced with the 'Settings App', a more limited and graphical tool. For unleashing more power, see 'GodMode' below.
Windows 10 Shortcut Hints & Intro to GodMode from DigitalTrends.com.