Amtrak's 30th Street Station was slated to lose its iconic "split-flap" display. But Philadelphians had other ideas.
One of my most distinct memories from my college years in Philadelphia is sitting in the sanctum of 30th Street Station, the city's stately train station at the eastern edge of University City. I'd be there, waiting for a train, listening for the flutters of clickety-clacks that punctuated the hollow silence. The sound told me that the iconic split-flap display board showing the train arrivals and departures of Amtrak trains was being updated. It was a comforting sound, and as the tiles flipped-out the new letters and numbers, it felt as if a reset button had been pushed and the next moment was somehow newer and shinier.
This happy news comes from Representative Brendan Boyle, a Democratic Congressman from Pennsylvania, who advocated for the preservation of the sign in a phone call to Amtrak's CEO Monday.
Boyle recounted his phone conversation on WHYY's Radio Times yesterday. "Three different times, he said he was optimistic to preserve the sign there and relook at this and figure out a way that they can keep a sign and at the same time achieve their goal of an upgrade," Boyle said.
To be fair, the sign is not in great condition. As the Philadelphia Inquirer's Inga Saffron notes, it runs on a Windows 95 (!) and desperately needs to be integrated with more current software. Its parts are aging—its manufacturer, the Italian company Solari, no longer makes replacements. Amtrak has understandably argued that it's a headache to maintain.
But Philadelphians appear unswayed by the practical arguments. Lovers of the sign have brandished pleas, petitions, and hashtags. But the knock-out blow perhaps came from Saffron herself, the Inquirer's Pulitzer-winning architecture critic, who argued in favor of preserving the sign in a recent op-ed. Her big points: aesthetics and function don't have to be at odds, and keeping the sign as is or replacing it with an ugly blue TV screen aren't the only two options. There are alternatives! If the American office of Solari can't spruce it up—and they told her they can—there's also a local company that makes easy-to-read, laptop-controlled split-flap signs. And if you're still wanting for reasons: It's also more energy-efficient.
The split-flap board is part of Amtrak's heritage, but it belongs to Philadelphia, too. The very first train under Amtrak's control left 30th Street Station at 12:05 a.m. on May 1, 1971, bound for New York. The board in 30th Street Station doesn't just provide updates on arrivals and departures; its survival is crucial to telling the story of rail travel in America.
Philly has changed a lot since I went to college there; new buildings have popped up, old haunts have closed down; Gritty is now a thing. It would be nice to know that at least one small beloved feature may be held in place, for a little while longer.


I have been very blessed to have the support of many great writers, artists, producers and friends. You can find my music on all the major outlets.
Music sooths the soul and excites the mind. While country music is my main focus, I enjoy all genres and learning from many different artists.
I have been a member of ReverbNation for many years. Because of fans like you, my band has been ranked number one in two different States.
Sign up to here to for news and information.


I have a 1998 Mercedes C240 W202 Elegance sedan. Yesterday I took it on a freeway for the first time in some 4 months. The engine was at operating temperature, and no warning lights etc. were showing. When I was travelling at 100kph or more, there was a light vibration being felt in the front floor pan (both driver and passenger sides). Reduce speed to under 100kph and the vibration disappears. The car has done 215K's and I am the second owner at 212K's. The service book seems to have been kept up to date, but I wonder about the driveshaft flex joints. Or is there some thing else causing this vibration. There is no vibration felt through the steering wheel. Any help would be greatly appreciated. Many thanks.
Submitted by robertwhitting on Dec 5, 2018.
Hi RobertWhitting, Did you check your tire pressure?
Thanks, yes I did. All new tyres with 35psi showing on all four.
These symptoms are often caused by an issue with a rear wheel. I would check for a bent wheel balance them and see if that helps before replacing more expensive parts.
Thank you. Actually I did think about that, because when I checked all wheels for tyre pressure, I did notice that one of the rear wheels did not have any lead balance weight on the rim. I thought that was unusual. They're pretty new tyres, so I'll take the car back to the dealer.
But if that is not the case, you can consider getting your half shaft / drive axle checked too. Contrary to most beliefs,they can cause vibration at high speed too. You can refer to the top 3 drive shaft problems article.


text:
SOCIAL IMPACTS
CSUITEMUSIC seeks to create content that not only entertains, but that also impacts communities and promotes awareness around important issues of our time. CSUITEMUSIC will continue expanding to create partnerships that leverage media and culture to have a social impact.
In 2017, Stockton, CA Mayor Michael Tubbs' office partnered with Michael J. Payton & CSUITEMUSIC to create a visual presentation to explain the details of his bold plan to tackle income inequality in his community, by initiating a basic income pilot program titled SEED (Stockton Economic Empowerment Demonstration).
The video was widely circulated and featured in local and national news coverage, which helped to kickstart a national conversation around the idea of basic income floor for every American. A version of the concept that the mayor propose of $500 per month for working families has been adopted by Senator Kamala Harris as part of the proposed LIFT Act.
In the United States and around the world, women and girls still face incredible challenges when it comes to being treated equally. Here in the United States, we are currently engaged in a cultural shift in which courageous women and men are actively stepping up. Here's some of the content CSUITEMUSIC has produced to help advance the cause:
1. Reproductive Rights
2. Mayor Michael Tubbs on Equal Pay
3. NBA Champion J.R. Smith tweets out CSUITEMUSIC's article on Equal Pay for Black Women
4. CSUITEMUSIC produced the first in-depth documentary on Kamala Harris
In 2017 CSUITEMUSIC's Michael J. Payton worked with the Office of Mayor Michael Tubbs and Senator Kamala Harris to create a video about the San Joaquin Valley Leadership Conference in Stockton, California.
The summit gathered leaders to create an unified agenda to address health outcomes, education, public safety, and the economy in underprivileged communities
In the wake of the California wildfires that destroyed the city of Paradise in 2018, CSUITEMUSIC teamed with the Office of Mayor Michael Tubbs, NBA G-League team Stockton Kings, and the community leaders to build StocktonHelpsParadise.org - a one-stop destination for Stockton citizens to donate money to support their neighbors in Northern California with the goal.
In 2019, it was revealed that the CSUITEMUSIC-developed website helped to raise more than $100,000 for the victims of the wildfires.
CSUITEMUSIC was tapped to help produce the 2018 Governor's Volunteer and Service Awards in California which recognizes individuals and entities doing outstanding volunteer work in the State of California. Founder Michael J. Payton worked with the Governor's Office and Disney to produce a video recognizing Disneyland Resorts as Business Volunteer Program of the Year.
CSUITEMUSIC worked with the California Governor's Office to produce a video campaign called "Why I Serve CA" to promote volunteerism and encourage citizens to join AmeriCorps. The videos are a part of Governor Gavin Newom's CA for All initiative.
In his in-dpeth conversation with Stockton Mayor Michael Tubbs, founder Michael J. Payton and the mayor discuss the issue of immigration and DACA.
In the wake of the tragic police-murder of Sacramento man Stephon Clark, CSUITEMUSIC produced a short viral video of Clark's relative giving a powerful and moving speech about the horrific incident.
In 2018, Michael J. Payton and his CSUITEMUSIC project partnered with Mayor Michael Tubbs of Stockton, CA and the Stockton Unified School District to develop and design the initial rendition of StocktonScholars.org, a $20 million scholarship fund. The scholarship, funded by private dollars, provides funds to every graduating high school student in Stockton, CA to attend a 4 year college or vocational school.

redpajama_set_name: RedPajamaCommonCrawl


There are a few things to check. First look in the camera properties in Blue Iris, on the Video tab. Make sure "Anamorphic" is not checked. Make sure "Area of interest" is not checked.
It could also be that Blue Iris is pulling a different stream than you are seeing when you view in the camera's web interface. Double-check the resolution of the camera reported by BI (should be on the camera properties > Video tab just above the Anamorphic checkbox) and make sure it matches the main stream of the camera. The main stream should be set to the camera's largest resolution choice.
@bp2008 Anamorphic and Area of Interest are not checked. However in regards to your second observation, the web log in for the camera shows the main stream set to the highest resolution of 2688 * 1520 and BI console shows 1920 * 1080 and it is grayed out and not sure how I would change it. So it appears BI is not pulling the main stream from the camera settings for whatever reason?
I figured it out. Stupid me just assumed that since it was basically a rebranded Hik cube that I could use Hik as the manufacturer. Once I changed the brand from Hik to LTS it pulled the correct Main stream and looks like it should in BI now.
Thanks for helping me troubleshoot. Appreciate it!
bp2008, awsum140 and looney2ns like this.
This is a bug in ui3, and I have it fixed in my fork. Do you accept pull requests?
Sure. Thanks for going to the trouble of ironing that out.
I've discovered an issue with UI3 in Safari from my iPad (iOS 12.1.3). This issue occurs only when I start UI3 from a desktop icon created via Share>Add to Home Screen. When I take a snapshot, the image appears in full screen from which there is no way to get back to the UI3 interface. I must close UI3 entirely.
If I use Chrome on my Android device, whether started from an in-browser bookmark, or from a desktop icon, the snapshot jpg is immediately downloaded with a flash message.
Apple has crippled web browsers on iOS for reasons known only to them. So it doesn't really surprise me that it reacts to an image download like that. Nothing I can do, really.
I can do it via tinyCam Pro on my phone... but soon as I move the camera via UI3 (or wherever) the Iris resets. So on cloudy days, I have to load up tinyCam to change iris settings to that details are better whenever I want to move the camera. (also found that the camera auto resets the Iris, so would love to be able to control it via BI/UI3).
UI3 can only do a subset of the things Blue Iris can do. You'll have to ask the Blue Iris developer for iris controls, or reconfigure some of the presets to send Dahua API commands to adjust the iris.
I can't figure out how to open UI3 without the need for a user/password.
If i set "Require from: No connections" it works.
But "Non-LAN only" does not work.
Go to "options", "users", check box for user "anonymous", then click on "OK".
I then suggest you then edit user "anonymous" by checking "LAN only" box, then click on "OK", and set your "require from" authentication back to "Non-LAN Only" and that "insure secure session keys" is checked.
http://10.1.0.10:81 works on the BI machine in Edge.
But on my workstation in every browser i get the login page.
No, it's not the same LAN unless there's a typo.
10.1.0.10/16 and 10.1.1.1/16 are on different subnets.
EDIT: we went over the anonymous user thing back in December 2018; did that not work out?
10.0.0.0/16 is 10.0.0.1 up to 10.255.255.254.
My network works. All devices communicate without problems.
I wouldn't be surprised if Blue Iris doesn't check the subnet mask properly. That is what it sounds like.
You can work around this using the "Limit IP addresses" box in Blue Iris Options >Web server > Advanced.
-58.*.*.* deny any address beginning with 58.
The final modifier character (^) will allow the addresses to skip authentication.
We went over the anonymous user thing back in December 2018; did that not work out?
Exporting clips to AVI is not supported.
^10.*.* does work but i guess its something i don't want?
It also would mean i also have to add ^192.168.*.* because the OpenVPN tunnel network is assigning 192.168.44.1 - 192.168.44.254 to the clients?
It did not work and that's the reason i'm now looking at it again.


Nakhai Furniture is an established business that has enjoyed years of creating unique handcrafted furniture of the highest quality.
Our professional team of designers, skilled cabinet makers and quality joiners use a combination of traditional and modern techniques.
Please view the website for more details.


Going from Civitavecchia to Fiumicino airport is not a mission impossible: thanks to Cab Roma you can easily get off the ship at the port of Rome and reach the airport to continue your journey.
If you are organizing a complex journey that includes car travel, and special connections, you should know that it's better to rely on experienced native people that have all the knowledge to make your trip easier. Thanks to Cab Roma you can easily go from Civitavecchia port to Fiumicino and organize the best trip of your life.
The trip from Civitavecchia to Fiumicino can be very tiresome in fact you will not find a direct train or bus that takes you from the port to the Rome airport and so you would need to get to Rome first and from there finally to Fiumicino. So if you need to get to the airport to continue you Journey to other European or Italian destinations the best way is to use a private car service that will take you there on time and comfortably.
So what are you waiting for? Book now and one of our cars will take you from Civitavecchia to Fiumicino airport with no fuss.


WASHINGTON, DC -- Trading in his glittery tank top and striped shorts for a suit and tie, famed fitness guru Richard Simmons spoke at a hearing before Congress on Thursday, urging the House Education and Labor Committee to expand physical education in public schools.
When he graduated from high school in New Orleans, Simmons tipped the scales at 268 pounds. He said he was later "bitten by the sweat bug" and became a fitness advocate, producing 50 fitness videos that have sold more than 20 million copies. He also is the author of nine books and three cookbooks.
During the hearing, Simmons spoke about the obesity epidemic in children.
Everybody needs to perform three forms of exercise: cardio, strength training and stretching, Simmons told Congress, and everybody can use exercise to feel better about themselves.
"When you're feeling great about yourself, when you have self-esteem and self-respect for yourself, there isn't nothing you can't do," he said at the hearing.
After the hearing, Simmons traded in his suit and tie for his normal workout attire and led Congressional staff members in a workout on the terrace of the Cannon House Office Building.


Perfectly located and meticulouly maintained 2 bed room, 2 full bath condo within walking distance to Gloucester's quaint shops, studios, impressive restaurant scene and old style Italian cafes. Spacious and bright, there is in-unit laundry, gas cooking, deeded off street parking and a private storage room for your beach chairs and bikes after a day at beautiful Good Harbor Beach. Maple cabinetry, granite countertops, and trash compactor enhance the kitchen. A loft provides additional space for your guests, office, or art studio. High ceilings, sky lights, and huge windows compliment the dramatic architecture of this special unit. Stroll to the harbor and watch the boats catch the open breeze. Access the commuter rail near by to come and go without ever getting in your car. A wonderful opportunity to have a lock-and-go home in a vibrant seaside community and take advantage of all that Gloucester has to offer!


Saudi Arabia's vision to create jobs for locals by pushing expat workers out has left the country's economy in disarray as the foreigners leave but there is no one to replace them.
Nearly 1.5 million expatriate jobs have gone since the end of 2016, squeezed out by Saudisation reforms and economic slowdown. Over the same period, however, the number of Saudis employed outside the security and military sector grew by less than 50,000, according to the General Authority for Statistics, Bloomberg reports.
Some argue that having firms hire Saudi nationals to reach a quota set by authorities and avoid penalties could result in the hiring of unqualified employees.
What is important now is that a Saudi national finds a job, without considering the aftermath"
A Saudi expert in Riyadh, who spoke on condition of anonymity, said that criticism of the kingdom's saudisation programme is out of hand.
"What is important now is that a Saudi national finds a job, without considering the aftermath," said the expert, who stressed that, due to public pressure, some specialised jobs could go to Saudi nationals who are not up to the task.
Others pointed out that average expatriate workers who are essential to the kingdom's economy could feel under attack because of the political climate. One Jordanian resident said he felt he was no longer wanted in Saudi Arabia and that claims of outsized expatriate salaries were exaggerated.
"Let's put experience and efficiency aside, did we come to Saudi Arabia to work for less pay than in our countries?" asked the resident. "Without financial incentives, what would make a man leave his home country and people?"
However, one government official who asked not to be named thinks this move is being deployed in the more visible sectors only.
"Saudisation has been going on for a long time, all that's happening now is that there is more focus on sectors that are easy to find the local talent," says the official.
Many sectors in the Saudi economy increased Saudisation quotas under strict deadlines, resulting in many expatriate workers being phased out. This affected some sectors, such as the mobile phone industry and gold sector, in which many expatriates have traditionally worked.
Many shops in Saudi Arabia have been forced to close down during the ongoing Saudisation campaign since they were found to be running under the illegal "tasattur" arrangements, according to media reports.
The 'tasattur' practice sees expatriates run the retail businesses in the name of Saudi nationals after paying them a fixed amount.
Around 30% of the shops in sectors where Saudisation is now mandatory have been forced to shut down in the past six months owing to this practice, local daily Al-Madina reported.
"I give them very high salary ... but the problem is they don't like [the work]," Abu Saud, an owner of a mobile accessory shop complained. He gets the impression Saudis would rather be working in a government office. "Each one he like to have a table, he's a boss. Even if just to graduate he just want to be a boss, direct," he says.
The Vision 2030 national transformation plan aims to create 450,000 private sector jobs by 2020 and reduce unemployment to 7% by 2030.


Give your bridesmaids shoes that keep their feet happy until the last dance. This combination is one of two styles available in Metallic Lilac, so you can let your ladies choose which style looks best on them while still matching. Best of all, they can change out their looks (straps) and keep wearing these shoes again and again.
2pc Kit Includes: Jackie in Metallic Lilac + Black Suede Mule + Travel Pouch.


text:
The Cebidae are one of the five families of New World monkeys now recognised. Extant members are the capuchin and squirrel monkeys. These species are found throughout tropical and subtropical South and Central America.

Characteristics
Cebid monkeys are arboreal animals that only rarely travel on the ground. They are generally small monkeys, ranging in size  up to that of the brown capuchin, with a body length of 33 to 56 cm, and a weight of 2.5 to 3.9 kilograms. They are somewhat variable in form and coloration, but all have the wide, flat, noses typical of New World monkeys.

They are omnivorous, mostly eating fruit and insects, although the proportions of these foods vary greatly between species. They have the dental formula:

Females give birth to one or two young after a gestation period of between 130 and 170 days, depending on species. They are social animals, living in groups of between five and forty individuals, with the smaller species typically forming larger groups. They are generally diurnal in habit.

Classification
Previously, New World monkeys were divided between Callitrichidae and this family. For a few recent years, marmosets, tamarins, and lion tamarins were placed as a subfamily (Callitrichinae) in Cebidae, while moving other genera from Cebidae into the families Aotidae, Pitheciidae and Atelidae. The most recent classification of New World monkeys again splits the callitrichids off, leaving only the capuchins and squirrel monkeys in this family.

 Subfamily Cebinae (capuchin monkeys)
 Genus Cebus (gracile capuchin monkeys)
 Colombian white-faced capuchin or Colombian white-headed capuchin, Cebus capucinus
 Panamanian white-faced capuchin or Panamanian white-headed capuchin, Cebus imitator
 Marañón white-fronted capuchin, Cebus yuracus
 Shock-headed capuchin, Cebus cuscinus
 Spix's white-fronted capuchin, Cebus unicolor
 Humboldt's white-fronted capuchin, Cebus albifrons
 Guianan weeper capuchin, Cebus olivaceus
 Chestnut capuchin, Cebus castaneus
 Ka'apor capuchin, Cebus kaapori
 Venezuelan brown capuchin, Cebus brunneus
 Sierra de Perijá white-fronted capuchin, Cebus leucocephalus
 Río Cesar white-fronted capuchin, Cebus cesare
 Varied white-fronted capuchin, Cebus versicolor
 Santa Marta white-fronted capuchin, Cebus malitiosus
 Ecuadorian white-fronted capuchin, Cebus aequatorialis
 Genus Sapajus (robust capuchin monkeys)
 Tufted capuchin, Sapajus apella
 Blond capuchin, Sapajus flavius
 Black-striped capuchin, Sapajus libidinosus
 Azaras's capuchin, Sapajus cay
 Black capuchin, Sapajus nigritus
 Crested capuchin, Sapajus robustus
 Golden-bellied capuchin, Sapajus xanthosternos
 Subfamily Saimiriinae (squirrel monkeys)
 Genus Saimiri
 Bare-eared squirrel monkey, Saimiri ustus
 Black squirrel monkey, Saimiri vanzolinii
 Black-capped squirrel monkey, Saimiri boliviensis
 Central American squirrel monkey, Saimiri oerstedi
 Guianan squirrel monkey, Saimiri sciureus
 Humboldt's squirrel monkey, Saimiri cassiquiarensis
 Collins' squirrel monkey, Saimiri collinsi

Extinct taxa
Genus Panamacebus
Panamacebus transitus
Subfamily Cebinae
Genus Acrecebus
Acrecebus fraileyi
Genus Killikaike
Killikaike blakei
Genus Dolichocebus
Dolichocebus gaimanensis
Subfamily Saimiriinae
Genus Saimiri
Saimiri fieldsi
Saimiri annectens
Genus Patasola
Patasola magdalenae

References

New World monkeys
Primate families
Taxa named by Charles Lucien Bonaparte
Taxa described in 1831

redpajama_set_name: RedPajamaWikipedia


Dr. El Remessy is the director of the Program in Clinical & Experimental Therapeutics at the College of Pharmacy in the University of Georgia. Her visit to MIU will extend from October 4 to October 15.
During her visit, Dr. Azza El Remessy will contribute to teaching the fourth year pharmacy students the endocrine disorders and their therapeutics. She will also be holding a presentation for the faculty.


We're going to break down everything you need to know about leveling your RV appropriately. First, we'll discuss the top five leveling blocks and why we've made our selection. Everything you need to know about leveling your RV is right here.
Why Will A Refrigerator Stop Working If My RV Isn't Level?
No matter where you look, Andersen's name is floating around somewhere.
That's because they pioneered one of the most advanced systems for leveling your RV, which was quickly mimicked by the competition (even though, to their credit, some of they did a great job).
Andersen holds up to 30,000 lbs so long as you remain within the 4" diameter allotment. Ride up to the blocks, roll up, inject the other pieces into place, and you're ready to go.
Andersen includes circular inch measurements so you can know exactly how high off the ground your RV is, making the next time even easier.
This is designed for a single person to use it with under five minutes of setup. Stabilizing with cinder blocks and manual jacks are in the past. With this simple system, you get into place, and stay that way.
These RV leveling blocks accommodate up to a 32" wheel size as well.
Riding on the Andersen design, Beech went ahead with the sliding block ideal.
They came very close to mimicking the same take as Andersen, and in some regards, they even had more success.
They added a traction pad to this polymer construction, and equipped it to handle an additional 5,000 lbs more than the Andersen model.
You'll notice similarities in the circular measurements along the side, and the simplicity of locking the two pieces together.
You'll be able to set this up single-handedly in about five minutes or less, with a few simple maneuvers.
The other way they actually rose above Andersen is with their lifetime warranty. They even vow that if you modify the levelers in a small way, (which most warranties on products would never allow), it's still under warranty.
They want you to be happy with the product above all else.
Super simple and lightweight to store in your RV during travel.
That's why Bunkerwall made the list, apart from their original design elements.
You get three different ways to level your RV, giving you the option to off-center your axle, should it need it, with two blocks. These only hold a combined weight of 10,000 lbs per axle.
Versatility was a big factor. The red components separate from the black, unveiling a way for you to use them with tandem axles.
These are super lightweight at just under 10 lbs, and inexpensive enough that getting one set per axle is an option.
Just keep in mind that they didn't peak the top of the list for two reasons: lower weight capacity, but also the lack of UV resistance on the polyethylene construction. Don't worry; our next product on the docket took care of that last flaw.
Camco ranks highly on a lot of products for your RV, and we were surprised to find them lacking where others picked up the pace.
They did, however, make these out of UV-resistant ABS plastic.
After long exposure to sunlight, plastic can get brittle, but the primer on these blocks prevents that from happening for years.
You get ten of these to a stack, allowing you to create small pyramids and effectively hoist your RV up onto them to get the height you want.
You'll be able to stash these in the included zippered storage bag when not in use, keeping them free from harm.
The last major point of these is the manufactured bottoms that prevent them from being pushed into the dirt.
They fell short on the maximum weight though, because they didn't even list it anywhere, including the package that arrived when we ordered it.
Our speculation on the weight here is from personal testing, and the community documenting their experiences.
Last but not least, Tri-Lynx made a system that is very simple to use.
Ten blocks to a pack allow you to maneuver multiple wheels to position your RV in a number of ways.
Tri-Lynx really blew us away with the highest max weight on the list, a staggering 40,000 lbs of resistance.
Tri-Lynx also included a ten-year warranty on every block, giving you absolute certainty that even if they don't hold up to your expectations, you'll be justly taken care of for trying their product.
After contacting customer support to test the waters, they were more than happy to oblige.
Because you can stack these in small pyramids to mount, you can use these in multiple ways. This gives you a little more wiggle room than standard block models, though the bottoms aren't as equipped for handling soft dirt or mud.
Let your trailer rest for ten minutes before deciding that your leveling job is finished.
Your RV's position is far more important than you might think. Not having a level RV can interfere with refrigerator operations, toilet flush function, and your comfort while camping out.If your unit didn't come with an expensive hydraulic lift, you're among the majority of folk that take their RV out on the road.
Any RVer can lug their fifth wheel to a camping spot, they can drop it anywhere and hook up the RV power cord, but only a true RV master can get that perfect level in a short amount of time.
We've shown you the top leveling blocks to make your RV trip even easier, but now it's time to show you why it's important to level your RV.
Some issues are technical, while others may seem arbitrary (depending on your RV style).
Just know this: leveling your RV makes for a better time, and shows your prowess at providing your passengers with a good time, from an experienced RVer.
Maintain Your Center of Gravity: When you're used to walking around your home throughout the week, and then you're on consistently uneven ground, it throws off your center of gravity. This makes you more prone to bumping into things, tripping and knocking your feet/knees on the stairs as you travel up. Don't confuse the family with an unlevel RV.
Better Sleeping: We sleep laying flat. Well, at least when we're at home we do. It should be the same when you're out on the road. If you have little ones sleeping in the bunk beds in the back of the RV, this benefit also rolls into their center of gravity. You don't want anyone rolling off and hitting the floor in the middle of the night just because the RV isn't level.
Reduced Storage Issues: We know you have everything secured, but that doesn't change the fact that opening your cabinets or drawers can lead to them sliding open fast, or items ejecting if your RV isn't level. They can still get tossed around in the cabinet while you're driving. When your RV is level, so are your belongings.
Your refrigerator uses a very specific coolant that needs to settle.
If you've ever read up on buying a deep freezer or ordering a refrigerator offline, you'll notice that it comes with information requesting that you don't plug anything in until it has been set on level ground for at least 24 hours.
That's because turning it on too soon can damage your refrigerator's motor, all because the coolant hasn't set.
It's the same with your RV.
If you spend the entire night with an unlevel RV and go to turn the fridge on, you could damage your unit.
If you filled up before heading to the campground and your fridge has been running throughout the entire ride, spending the night on unlevel ground is only going to damage it.
While that sounds a bit daunting, do note that a few degrees off-kilter will not ruin your fridge. We're not trying to startle you, it mostly applies to severe tils at about 7 to 10 degrees or higher.
If your RV is off-kilter by this much, you'll be able to tell while walking through it.
Manual leveling blocks are the way to go.
We're not personally fans of using X-chocks, which are additional stabilization systems. They help the wheels stay in place, but offer increased risks when trying to set them up.
At Kempoo we're always after the safest (and quickest) way to handle RV setup and maintenance.
With manual blocks, you're getting the full-fledged power of the maximum weight capacity without taking variables into account.
Most RV leveling blocks come with far more weight hold than necessary.
When you take into account that the average RV is under 6,000 lbs, and the standard RV leveling block can hold upwards of 30,000 lbs, you have a solution staring back at you.
You can use cinder blocks, you can use pressure-treated wood, but it's not recommended.
Whether it's just you setting up the RV or you have another set of hands with you, there's always danger in doing these things.
Your best bet is using something that's been industry-tested to withstand pressure and massive weight.
Don't get us wrong, there are plenty of folks who have made extremely effective RV leveling blocks themselves.
However, most of these gentleman come with plenty of experience in carpentry or woodworking, and understand the engineering that goes into making these.
DIY blocks are poised to fail far before a purchased, manufactured leveling block will.
If your DIY leveling blocks break, you have to purchase the goods to make new ones. On average, that can cost as much or a little more than an RV leveling block from a trusted manufacturer, not to mention the time spent.
We have known some RVers who make their own leveling blocks, but still purchase a backup set of manufactured blocks in case they needed to use them.
We wanted to explain the proper way to set up your RV with its leveling blocks.
Once you run through this process once, it will become muscle memory. Every time after the first will get easier to get the perfect level on your RV.
Pick your spot appropriately. If you rent a spot at the same RV park every single year, you'll have a good working knowledge of its layout. Don't be afraid to get out of your RV and walk across a patch where you might be dropping anchor for a few days. The more level the ground is to start with, the simpler your job will be. If it's a recurring spot, use a shovel to level out the ground before returning next time. Be sure to turn off the engine, and don't forget to set your parking brake.
Consider your rooftop solar panels. If you're trying to grab a bit of energy from Mother Nature, we can respect that. It just has to be done the right way. Position your panels appropriately before leaving to go the spot, so they'll still be absorbing the maximum amount of energy after you level your RV.
We've covered a guide on proper RV jacks. Using the right jack, position your RV to give you a good starting point. If you can back up your fifth wheel to the right spot, get out and inspect the unit. Level it with your jack, and then move your RV leveling blocks into place accordingly. This is the most effective method as ther jack will do most of the work for you. You'll only really run into problems if one entire side of the RV is leaning (if you accidentally parked on a slight incline without noticing first).
Position your blocks into place and unhitch your trailer. You'll have to consult the exact system you found on this list, and move the block(s) into place following the instructions. If you're using an automatic jack, you should be able to set up shop without requiring a second set of hands to help you out.
They seem like a simple object, but there's always more than meets the eye.
We've gone over the main things you should keep in mind when purchasing.
We can all get flustered when we've gone through numerous Amazon pages and read a ton of information. Review these simple steps below to get in the right headspace, and purchase an RV leveling block you can use for years to come.
This will determine if it's even going to fit your vehicle.
We've heard of other RVers buying slightly smaller wheel frame leveling blocks, figuring they'll be able to wedge it under the tire.
Same goes for oversized blocks that are too big for your tires.
Don't go with what's cheapest, go with what's right for your RV wheel size, or you'll essentially be wasting your money.
There are only so many RV wheel sizes, and there are definitely leveling blocks available to accommodate your RV.
This is going to define durability and dictate your use. So long as the material (usually steel or ABS plastic) can hold your RV, you should be good to go.
Manufacturers have to measure to to certain standards, not just for competing with their rival companies, but to ensure they're selling safe products.
If you're camping with passengers, just account for the total weight of everybody, plus 50 lbs for luggage and belongings.
Plan ahead to stay under 80% of the total leveling block weight capacity.
Are you usually spending nights in a campground?
Sometimes we just have to drop the hitch and relax wherever we're at, but if you can plan ahead, you'll have a more enjoyable experience in your RV.
Regularly camping on dirt or other non-level spots come with their challenges, so look for an RV leveling block that contours to your usual sites.
You'll have to take into consideration the associated materials, overall weight of your RV, and how much the RV leveling block is rated to hold.
In most scenarios, we recommend not exceeding 80% of your RV leveling block maximum load capacity.
If you can stay at under 80% utilization of the max weight, your leveling block will last for three years longer on average.
Between time, stress and the pressure of your RV, these blocks slowly meld and bend. If you level your RV for five or more days at a time (full-timer with frequent stops), you're putting even more damage into the block.
That's okay. They're inexpensive and designed to handle this, but we still need to keep an eye on how durable our RV leveling blocks are, and what we're putting them through.
If you're currently using a DIY leveling block, it's an option you can go with, but it's not recommended.
We've shown you the top five leveling blocks and explained everything that comes into play when using them.
It's time to enjoy your trips instead of fiddling around with the challenges of an unlevel RV.


text:
Tag: rights
Sandoz, A Novartis Division
So just firstly, with Kisqali, you previously recommended that adjuvant is a $6 billion chance. Simply because when you look at the epidemiology, it would recommend a substantially bigger opportunity in intermediate pension pool. So, I am just curious what assumptions you happen to be generating in terms of which — basically get the drug in this population since genuinely, if you see a decent penetration, the marketplace prospective need to be significantly larger. Just on sabatolimab, offered the delay in filing due to needing Phase three OS data and the higher hopes that physicians look to have for VENCLEXTA and MDS in the VERONA trial, I'm just curious how you are considering about the prospective for the item in MDS at this point. Does it now turn into somewhat of a decrease priority, or do you still believe that higher than $1 billion chance you discussed previously in MDS is still feasible?
Novartis will spin-off its generics division Sandoz, which incorporates a portfolio of eight biosimilar goods. Tuesday's announcement of a strategic overview for Sandoz, meanwhile, follows a failed bid by Novartis to sell about 300 of its goods to India's Aurobindo Pharma, a deal that was terminated immediately after U.S. regulators refused to sign off. The strategic evaluation, announced Tuesday alongside earnings for the third quarter, could nevertheless outcome in retention of the Sandoz division, which earned Novartis $7.1 billion in revenue this hyperlink by means of the first nine months of the year. Last month, Novartis said Sandoz's earnings would probably hold steady this year, mostly thanks to development in Europe. Sandoz sales have been hurt by pricing stress that has impacted the broader generics market for years, particularly in the United States, even though the country accounts for significantly less than a quarter of the unit's total sales.
And Pluvicto in its very first full quarter in the launch, also performing quite well in its early days. That was driven each by strong functionality in IM at four% as properly as in Sandoz. U.S. IM sales had been up 8%, consistent with our technique to continue to improve our position in the U.S. marketplace. Thank you, Samir, and thanks, everyone, for joining on today's conference contact. Novartis delivered strong Quarter three overall performance really across all of our core value drivers.
On the next slide, I would like to drill down a bit into the overall performance by division. So, for quarter two, you can see that Revolutionary Medicines top rated line grew five% and the bottom line, 6%, resulting in an improvement in the core margin of 15 basis points to 37.2%. Sandoz net sales also grew five% despite the fact that core operating revenue decreased 4%, mostly due to increased M&S investments and greater other expenses. This was reflected in the core margin, which decreased to 20.four%. All round, for the first half, we saw a sturdy overall performance for Revolutionary Medicines and Sandoz, Revolutionary Medicines sales increasing 5% and core operating revenue 6% in half one. Nowadays around 40 % of all investment is going into the area of immuno-oncology.
Just a few weeks following announcing a controversial strategy to take over ophthalmic giant Alcon Laboratories, Novartis announced its chief executive officer is stepping down and the chief financial officer will retire. On Leqvio, I believe there is an element of expertise and also understanding the Aspect B and the payer dynamic. There is 30% to 40% of sufferers who are in Medicare Portion D charge-for-service that do not have any relevant blocks and can access the medicines.
Also, in November 2021, the Swedish-primarily based investment group EQT and Germany's Struengmann family members, who are investors in BioNTech, had been considering a USD21.6bn joint supply for Sandoz. Other potential suitors contain Advent International, Hellman & Friedman, and KKR&CO. Despite potential investors offered for Sandoz, elevated inflationary pressures, the war in Ukraine, and volatile stock markets continue to hinder banks' willingness to lend cash for significant acquisitions. We think this will make the acquisition option for Sandoz much less most likely, as a result growing the prospective of Sandoz spinoff additional most likely.
Novartis is passionate about the discovery and development of revolutionary medicines to help present a broad variety of new therapies and practical options to advance care of sufferers. The company's investigation is driven by a distinctive scientific and clinical approach focusing on unmet healthcare wants and know-how of disease pathways. The Novartis investigation approach leverages biomarkers and targeted drug development focused on person individuals.
We also want to enable stronger newborn screening programs outside of the United States. 97% of newborns are screened in the U.S., but only 30% in Europe, and those numbers are similar or reduce in a lot of other geographies. As we can get far more newborn screened, then we believe Zolgensma is the treatment of decision for these babies, allows for normalization of their overall improvement. And we saw that in a Nature publication that recently summarized the information from 1 of our earlier studies with 14 out of 15 patients walking alone and 11 of them in the typical development window when treated early with Zolgensma. Vasant Narasimhan will be elevated as chief executive of Novartis in February, the Swiss pharma giant said these days. A Novartis employee considering that 2005, Mr Narasimhan is presently the worldwide head of drug development and chief healthcare officer with the Swiss drug firm.
The programme is made to address specifically those difficulties that we know talented ladies may face when striving for the most senior levels of the organization. These include exploring improvement opportunities and strategic profession planning, but also broad cultural issues, such as lack of flexibility in operating hours, the impact of dual-profession families on mobility and low tolerance for distinct leadership types. Additionally, generic competitors had a unfavorable effect of four percentage points, mainly due to Afinitor/Votubia, Gilenya (ex-US), Gleevec/Glivec and Exjade. Sales in the US have been USD 4.1 billion (+8%) and in the rest of the globe USD six.two billion (-9%, +2% cc), the enterprise stated.
And then we had quite fantastic data in the initially-line setting as effectively. As we announced, that's been pushed back as we await the capability for FDA to inspect the facilities in China. And then hopefully, we'd be capable to have both, first and second line in esophageal. We'd have been hopefully second line in non-compact cell lung cancer, and we would expand from there. I do assume that the FDA is creating it extremely clear now that they count on a — any studies to be filed that they are worldwide in nature, they have an proper quantity of U.S. sufferers and that the standard of care employed reflects standard of care in the U.S. Chief Executive Officer Vas Narasimhan has been below stress to convince shareholders he can strengthen the company's overall performance.
Proper now, the concentrate is about 80 per cent revolutionary medicines and 20 per cent generics. We have 165 projects in drug development, which will hopefully be the next wave of innovation at Novartis. So, within the divisions, we anticipate Revolutionary Medicines sales increasing mid-single digit and core operating earnings developing mid- to high-single digit ahead of sales. The expected IM core margin increase will be driven by expected continued very good leading line momentum and continuation of our productivity programs, of course, such as the new organizational structure, providing us some added benefits in the second half already. We've actually focused attention as a company on six crucial growth drivers, we think, which will allow us to deliver the growth profile we've outlined, both in the next five years and also beyond. Notably Cosentyx and Entresto continued their outstanding efficiency towards their respective peak sales goal.
Although Schwan and Narasimhan were effectively compensated for their leadership at Roche and Novartis, respectively, other pharma CEOs have brought dwelling considerably larger paydays, such as the heads of Regeneronand BioMarin. Narasimhan himself, as well as the company's executive committee, are amongst the participants in the year-long leadership improvement system, which requires webinars, simulations, social finding out and personalized coaching created to train leaders in delivering the "unbossed" culture. Vasant "Vas" Narasimhan is an Indian-American doctor and the chief executive officer of Novartis . Unlike some of the other CEOs on this list, Akerson wasn't appointed to head General Motors in 2009 by a corporate board of directors. He took the helm of GM at the behest of the White Residence, following the company's majority shareholder abruptly became the U.S.
Clouse began with Kraft, where he led the company's growth method. He then applied his development knowledge to spark his CEO profession at Pinnacle Foods in 2016. He was so effective in growing Pinnacle's industry share that Campbell Soup hired him as its CEO in 2018. From wholesome soil to improved vegetables on the shelf, from farmers' incomes to fair labor practices, our work brings good change to people's lives. Jimenez is handing more than the reins at a essential juncture, with the drugmaker but to make a decision on the future of its ailing Alcon eyecare enterprise or its stake in crosstown rival Roche Holding.
Posted on October 21, 2022 November 17, 2022 Categories UncategorizedTags animal, attacked, family, grave, listed, novartis, rights, targets


text:
Q: Mirroring database in sql server 2008 When pricipal database is having less changes than mirror database i.e mirror_failover_lsn is greater than mirror_end_of_log_lsn of principal server, the mirroring session got suspended nad couldn't get resumed. Why so? . Now how can I restore my database and how to establish the session again?

A: What mirroring mode are you using?
Are you saying that you have writeable access to both databases in the mirror?  If so you may be affected by one of these bugs: 978947,978791
What status is your principal/mirror in?  check this by looking at the sys.database_mirroring DMV on each server.

A: You could try one of these options:
May work
 - Pause/suspend mirroring
 - Backup database and logs and copy backups to mirror
 - Restore backups and logs with NORECOVERY
 - Try and resume mirroring
Will work
 - Remove mirroring
 - Restore latest backup and log files to mirror
 - Re-run mirroring setup

redpajama_set_name: RedPajamaStackExchange


text:
<?xml version="1.0" encoding="UTF-8"?>
<!-- AMALGAM REAL DATASET SCENARIO                                                       -->
<!-- AMALGAM SCHEMA 1 to SCHEMA 2                                                        -->
<!-- Mappings created by BG according to material provided by Bodgan Alexe [SIGMOD 2011] -->
<this:MappingScenario xmlns:this="org/vagabond/xmlmodel" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Schemas>
	<SourceSchema>

<!--  ****************** Publication type tables ************************** -->
		<Relation name="InProceedings">
			<Attr><Name>inprocID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>bktitle</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>inprocID</Attr></PrimaryKey>
		</Relation>
		<Relation name="Article">
			<Attr><Name>articleID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>journal</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>articleID</Attr></PrimaryKey>
		</Relation>
		<Relation name="TechReport">
			<Attr><Name>techID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>inst</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>techID</Attr></PrimaryKey>
		</Relation>
		<Relation name="Book">
			<Attr><Name>bookID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>publisher</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>bookID</Attr></PrimaryKey>
		</Relation>
		<Relation name="InCollection">
			<Attr><Name>collID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>bktitle</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>collID</Attr></PrimaryKey>
		</Relation>
		<Relation name="Misc">
			<Attr><Name>miscID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>howpub</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>confloc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>miscID</Attr></PrimaryKey>
		</Relation>
		<Relation name="Manual">
			<Attr><Name>manID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>org</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>year</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>month</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pages</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>vol</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>loc</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>class</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>annote</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>manID</Attr></PrimaryKey>
		</Relation>

<!--  ****************** Author table ************************** -->

		<Relation name="Author">
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>name</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>AuthID</Attr></PrimaryKey>
		</Relation>

<!--  ****************** Relationship tables ************************** -->
		<Relation name="InprocPublished">
			<Attr><Name>inprocID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>inprocID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="ArticlePublished">
			<Attr><Name>articleID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>articleID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="TechPublished">
			<Attr><Name>techID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>techID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="BookPublished">
			<Attr><Name>bookID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>bookID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="InCollPublished">
			<Attr><Name>collID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>collID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="MiscPublished">
			<Attr><Name>miscID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>miscID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>
		<Relation name="ManualPublished">
			<Attr><Name>manID</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>AuthID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>manID</Attr><Attr>AuthID</Attr></PrimaryKey>
		</Relation>

<!--  ****************** Foreign Keys ************************** -->
		<ForeignKey id="inprocPub">
			<From tableref="InprocPublished"><Attr>inprocID</Attr></From>
			<To tableref="InProceedings"><Attr>inprocID</Attr></To>
		</ForeignKey>
		<ForeignKey id="inprocAuthor">
			<From tableref="InprocPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="articlePub">
			<From tableref="ArticlePublished"><Attr>articleID</Attr></From>
			<To tableref="Article"><Attr>articleID</Attr></To>
		</ForeignKey>
		<ForeignKey id="articleAuthor">
			<From tableref="ArticlePublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="techPub">
			<From tableref="TechPublished"><Attr>techID</Attr></From>
			<To tableref="TechReport"><Attr>techID</Attr></To>
		</ForeignKey>
		<ForeignKey id="techAuthor">
			<From tableref="TechPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="bookPub">
			<From tableref="BookPublished"><Attr>bookID</Attr></From>
			<To tableref="Book"><Attr>bookID</Attr></To>
		</ForeignKey>
		<ForeignKey id="bookAuthor">
			<From tableref="BookPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="incollPub">
			<From tableref="InCollPublished"><Attr>collID</Attr></From>
			<To tableref="InCollection"><Attr>collID</Attr></To>
		</ForeignKey>
		<ForeignKey id="incollAuthor">
			<From tableref="BookPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="miscPub">
			<From tableref="MiscPublished"><Attr>miscID</Attr></From>
			<To tableref="Misc"><Attr>miscID</Attr></To>
		</ForeignKey>
		<ForeignKey id="miscAuthor">
			<From tableref="MiscPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

		<ForeignKey id="manualPub">
			<From tableref="ManualPublished"><Attr>manID</Attr></From>
			<To tableref="Manual"><Attr>manID</Attr></To>
		</ForeignKey>
		<ForeignKey id="manualAuthor">
			<From tableref="ManualPublished"><Attr>AuthID</Attr></From>
			<To tableref="Author"><Attr>AuthID</Attr></To>
		</ForeignKey>

	</SourceSchema>
	<TargetSchema>

<!--  ****************** Publication type tables ************************** -->
		<Relation name="allBibs">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="citForm">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>form</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="authors">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>authNm</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>authNm</Attr></PrimaryKey>
		</Relation>

		<Relation name="editors">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>edNm</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>edNm</Attr></PrimaryKey>
		</Relation>

		<Relation name="titles">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>title</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="schools">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>schoolNm</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="institutions">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>institNm</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="addresses">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>address</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="types">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>type</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="ISBN">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>isbnNum</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="notes">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>note</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>note</Attr></PrimaryKey>
		</Relation>

		<Relation name="volumes">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>volNum</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="numbers">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>num</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="months">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>mon</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="years">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>yr</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="pages">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pgRange</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="abstracts">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>txt</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr></PrimaryKey>
		</Relation>

		<Relation name="publisher">
			<Attr><Name>pubNm</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pubID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>pubID</Attr></PrimaryKey>
		</Relation>

		<Relation name="citPublisher">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>pubID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>pubID</Attr></PrimaryKey>
		</Relation>

		<Relation name="journal">
			<Attr><Name>jrnlNm</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>jrnlID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>jrnlID</Attr></PrimaryKey>
		</Relation>

		<Relation name="citJournal">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>jrnlID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>jrnlID</Attr></PrimaryKey>
		</Relation>

		<Relation name="series">
			<Attr><Name>seriesNm</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>seriesID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>seriesID</Attr></PrimaryKey>
		</Relation>

		<Relation name="citSeries">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>seriesID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>seriesID</Attr></PrimaryKey>
		</Relation>

		<Relation name="booktitle">
			<Attr><Name>bkTitleNm</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>bktitleID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>bktitleID</Attr></PrimaryKey>
		</Relation>

		<Relation name="citBkTitle">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>bktitleID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>bktitleID</Attr></PrimaryKey>
		</Relation>

		<Relation name="keyWord">
			<Attr><Name>word</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>keyWdID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>keyWdID</Attr></PrimaryKey>
		</Relation>

		<Relation name="citKeyWord">
			<Attr><Name>citKey</Name><DataType>TEXT</DataType></Attr>
			<Attr><Name>keyWdID</Name><DataType>TEXT</DataType></Attr>
			<PrimaryKey><Attr>citKey</Attr><Attr>keyWdID</Attr></PrimaryKey>
		</Relation>

<!--  ****************** Foreign Keys ************************** -->

	<ForeignKey id="citFormToAllBib">
			<From tableref="citForm"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="authorssToAllBib">
			<From tableref="authors"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="editorsToAllBib">
			<From tableref="editors"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="titlesToAllBib">
			<From tableref="titles"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="schoolsToAllBib">
			<From tableref="schools"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="institutionsToAllBib">
			<From tableref="institutions"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="addressesToAllBib">
			<From tableref="addresses"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="typesToAllBib">
			<From tableref="types"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="ISBNToAllBib">
			<From tableref="ISBN"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="notesToAllBib">
			<From tableref="notes"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="volumesToAllBib">
			<From tableref="volumes"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="numbersToAllBib">
			<From tableref="numbers"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="monthsToAllBib">
			<From tableref="months"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="yearsToAllBib">
			<From tableref="years"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="pagesToAllBib">
			<From tableref="pages"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="abstractsToAllBib">
			<From tableref="abstracts"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>

	<ForeignKey id="citPublisherToAllBib">
			<From tableref="citPublisher"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>
	<ForeignKey id="citPublisherToPublisher">
			<From tableref="citPublisher"><Attr>pubID</Attr></From>
			<To tableref="publisher"><Attr>pubID</Attr></To>
	</ForeignKey>

	<ForeignKey id="citJournalToAllBib">
			<From tableref="citJournal"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>
	<ForeignKey id="citJournalToJournal">
			<From tableref="citJournal"><Attr>jrnlID</Attr></From>
			<To tableref="journal"><Attr>jrnlID</Attr></To>
	</ForeignKey>

	<ForeignKey id="citSeriesToAllBib">
			<From tableref="citSeries"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>
	<ForeignKey id="citSeriesToSeries">
			<From tableref="citSeries"><Attr>seriesID</Attr></From>
			<To tableref="series"><Attr>seriesID</Attr></To>
	</ForeignKey>

	<ForeignKey id="citBkTitleToAllBib">
			<From tableref="citBkTitle"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>
	<ForeignKey id="citBkTitleToBooktitle">
			<From tableref="citBkTitle"><Attr>bktitleID</Attr></From>
			<To tableref="booktitle"><Attr>bktitleID</Attr></To>
	</ForeignKey>

	<ForeignKey id="citKeyWordToAllBib">
			<From tableref="citKeyWord"><Attr>citKey</Attr></From>
			<To tableref="allBibs"><Attr>citKey</Attr></To>
	</ForeignKey>
	<ForeignKey id="citKeyWordToKeyWord">
			<From tableref="citKeyWord"><Attr>keyWdID</Attr></From>
			<To tableref="keyWord"><Attr>keyWdID</Attr></To>
	</ForeignKey>

	</TargetSchema>
</Schemas>

<Correspondences/>

<Mappings>
<!--
InProceedings(inprocID, title, bktitle, year, month, pages, vol, num, loc, class, note, annote) & InprocPublished(inprocID, authId) & Author(authId, authName)
->
authors(SK1(inprocID), authName) & allBibs(SK1(inprocID)) & addresses(SK1(inprocID), loc) & titles(SK1(inprocID), title) & citBkTitle(SK1(inprocID), SK2(bktitle)) & booktitle(SK2(bktitle), bktitle) & years(SK1(inprocID), year) & months(SK1(inprocID), month) & pages(SK1(inprocID), pages) & volumes(SK1(inprocID), vol) & numbers(SK1(inprocID), num) & notes(SK1(inprocID), note) & notes(SK1(inprocID), annote)
-->

	<Mapping id="M1">
<Uses/>
		<Foreach>
			<Atom tableref="InProceedings">
			  <Var>inprocID</Var>
			  <Var>title</Var>
			  <Var>bktitle</Var>
			  <Var>year</Var>
			  <Var>month</Var>
			  <Var>pages</Var>
			  <Var>vol</Var>
			  <Var>num</Var>
			  <Var>loc</Var>
			  <Var>class</Var>
			  <Var>note</Var>
			  <Var>annote</Var>
			</Atom>
			<Atom tableref="InprocPublished">
			  <Var>inprocID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="citBkTitle">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<!--  bktitleid -->
				<SKFunction skname="SK2">
					<Var>bktitle</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="booktitle">
				<!--  bktitleid -->
				<SKFunction skname="SK2">
					<Var>bktitle</Var>
				</SKFunction>
				<Var>bktitle</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK1">
					<Var>inprocID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
Article(articleID, title, journal, year, month, pages, vol, num, loc, class, note, annote) & ArticlePublished(articleID, authId) & Author(authId, authName)
->
authors(SK3(articleID), authName) & allBibs(SK3(articleID)) & addresses(SK3(articleID), loc) & titles(SK3(articleID), title) & citJournal(SK3(articleID), SK4(journal)) & journal(SK4(journal), journal) & years(SK3(articleID), year) & months(SK3(articleID), month) & pages(SK3(articleID), pages) & volumes(SK3(articleID), vol) & numbers(SK3(articleID), num) & notes(SK3(articleID), note) & notes(SK3(articleID), annote)
-->

	<Mapping id="M2">
<Uses/>
		<Foreach>
			<Atom tableref="Article">
			  <Var>articleID</Var>
			  <Var>title</Var>
			  <Var>journal</Var>
			  <Var>year</Var>
			  <Var>month</Var>
			  <Var>pages</Var>
			  <Var>vol</Var>
			  <Var>num</Var>
			  <Var>loc</Var>
			  <Var>class</Var>
			  <Var>note</Var>
			  <Var>annote</Var>
			</Atom>
			<Atom tableref="ArticlePublished">
			  <Var>articleID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="citJournal">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<!--  journalid -->
				<SKFunction skname="SK4">
					<Var>journal</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="journal">
				<!--  journalID -->
				<SKFunction skname="SK4">
					<Var>journal</Var>
				</SKFunction>
				<Var>journal</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK3">
					<Var>articleID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
TechReport(techID, title, inst, year, month, pages, vol, num, loc, class, note, annote) & TechPublished(techID, authId) & Author(authId, authName)
->
authors(SK5(techID), authName) & allBibs(SK5(techID)) & addresses(SK5(techID), loc) & titles(SK5(techID), title) & institutions(SK5(techID), inst) & years(SK5(techID), year) & months(SK5(techID), month) & pages(SK5(techID), pages) & volumes(SK5(techID), vol) & numbers(SK5(techID), num) & notes(SK5(techID), note) & notes(SK5(techID), annote)
-->

	<Mapping id="M3">
<Uses/>
		<Foreach>
			<Atom tableref="TechReport">
			  <Var>techID</Var>
			  <Var>title</Var>
			  <Var>inst</Var>
			  <Var>year</Var>
			  <Var>month</Var>
			  <Var>pages</Var>
			  <Var>vol</Var>
			  <Var>num</Var>
			  <Var>loc</Var>
			  <Var>class</Var>
			  <Var>note</Var>
			  <Var>annote</Var>
			</Atom>
			<Atom tableref="TechPublished">
			  <Var>techID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="institutions">
				<!--  journalID -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>inst</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK5">
					<Var>techID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
Book(bookID, title, publisher, year, month, pages, vol, num, loc, class, note, annote) & BookPublished(bookID, authId) & Author(authId, authName)
->
authors(SK6(bookID), authName) & allBibs(SK6(bookID)) & addresses(SK6(bookID), loc) & titles(SK6(bookID), title) & citPublisher(SK6(bookID), SK7(publisher)) & publisher(SK7(publisher), publisher) & years(SK6(bookID), year) & months(SK6(bookID), month) & pages(SK6(bookID), pages) & volumes(SK6(bookID), vol) & numbers(SK6(bookID), num) & notes(SK6(bookID), note) & notes(SK6(bookID), annote)
-->

	<Mapping id="M4">
<Uses/>
		<Foreach>
			<Atom tableref="Book">
			<Var>bookID</Var>
			<Var>title</Var>
			<Var>publisher</Var>
			<Var>year</Var>
			<Var>month</Var>
			<Var>pages</Var>
			<Var>vol</Var>
			<Var>num</Var>
			<Var>loc</Var>
			<Var>class</Var>
			<Var>note</Var>
			<Var>annote</Var>
			</Atom>
			<Atom tableref="BookPublished">
			  <Var>bookID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="citPublisher">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<!--  journalid -->
				<SKFunction skname="SK7">
					<Var>publisher</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="publisher">
				<!--  journalID -->
				<SKFunction skname="SK7">
					<Var>publisher</Var>
				</SKFunction>
				<Var>publisher</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK6">
					<Var>bookID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
InCollection(IncollID, title, bktitle, year, month, pages, vol, num, loc, class, note, annote) & InCollPublished(IncollID, authId) & Author(authId, authName)
->
authors(SK8(IncollID), authName) & allBibs(SK8(IncollID)) & addresses(SK8(IncollID), loc) & titles(SK8(IncollID), title) & citBkTitle(SK8(IncollID), SK9(bktitle)) & booktitle(SK9(bktitle), bktitle) & years(SK8(IncollID), year) & months(SK8(IncollID), month) & pages(SK8(IncollID), pages) & volumes(SK8(IncollID), vol) & numbers(SK8(IncollID), num) & notes(SK8(IncollID), note) & notes(SK8(IncollID), annote)
-->

	<Mapping id="M5">
<Uses/>
		<Foreach>
			<Atom tableref="InCollection">
			<Var>IncollID</Var>
			<Var>title</Var>
			<Var>bktitle</Var>
			<Var>year</Var>
			<Var>month</Var>
			<Var>pages</Var>
			<Var>vol</Var>
			<Var>num</Var>
			<Var>loc</Var>
			<Var>class</Var>
			<Var>note</Var>
			<Var>annote</Var>
			</Atom>
			<Atom tableref="InCollPublished">
			  <Var>IncollID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>

			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="citBkTitle">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<!--  bktitleid -->
				<SKFunction skname="SK9">
					<Var>bktitle</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="booktitle">
				<!--  bktitleid -->
				<SKFunction skname="SK9">
					<Var>bktitle</Var>
				</SKFunction>
				<Var>bktitle</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK8">
					<Var>IncollID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
Misc(miscID, title, howpub, confloc, year, month, pages, vol, num, loc, class, note, annote) & MiscPublished(miscID, authId) & Author(authId, authName)
->
authors(SK10(miscID), authName) & allBibs(SK10(miscID)) & titles(SK10(miscID), title) & addresses(SK10(miscID), confloc) & years(SK10(miscID), year) & months(SK10(miscID), month) & pages(SK10(miscID), pages) & volumes(SK10(miscID), vol) & numbers(SK10(miscID), num) & notes(SK10(miscID), note) & notes(SK10(miscID), annote)
-->
	<Mapping id="M6">
<Uses/>
		<Foreach>
			<Atom tableref="Misc">
			  <Var>miscID</Var>
			  <Var>title</Var>
			  <Var>howpub</Var>
			  <Var>confloc</Var>
			  <Var>year</Var>
			  <Var>month</Var>
			  <Var>pages</Var>
			  <Var>vol</Var>
			  <Var>num</Var>
			  <Var>loc</Var>
			  <Var>class</Var>
			  <Var>note</Var>
			  <Var>annote</Var>
			</Atom>
			<Atom tableref="MiscPublished">
			  <Var>miscID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>confloc</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK10">
					<Var>miscID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
Manual(manID, title, org, year, month, pages, vol, num, loc, class, note, annote) & ManualPublished(manID, authId) & Author(authId, authName)
->
authors(SK11(manID), authName) & allBibs(SK11(manID)) & titles(SK11(manID), title) & addresses(SK11(manID), loc) & years(SK11(manID), year) & months(SK11(manID), month) & pages(SK11(manID), pages) & volumes(SK11(manID), vol) & numbers(SK11(manID), num) & notes(SK11(manID), note) & notes(SK11(manID), annote)
-->
	<Mapping id="M7">
<Uses/>
		<Foreach>
			<Atom tableref="Manual">
			  <Var>manID</Var>
			  <Var>title</Var>
			  <Var>org</Var>
			  <Var>year</Var>
			  <Var>month</Var>
			  <Var>pages</Var>
			  <Var>vol</Var>
			  <Var>num</Var>
			  <Var>loc</Var>
			  <Var>class</Var>
			  <Var>note</Var>
			  <Var>annote</Var>
			</Atom>
			<Atom tableref="ManualPublished">
			  <Var>manID</Var>
			  <Var>authId</Var>
			</Atom>
			<Atom tableref="Author">
			  <Var>authId</Var>
			  <Var>authName</Var>
			</Atom>
		</Foreach>
		<Exists>
			<Atom tableref="authors">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>authName</Var>
			</Atom>
			<Atom tableref="allBibs">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
			</Atom>
			<Atom tableref="titles">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>title</Var>
			</Atom>
			<Atom tableref="addresses">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>loc</Var>
			</Atom>
			<Atom tableref="years">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>year</Var>
			</Atom>
			<Atom tableref="months">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>month</Var>
			</Atom>
			<Atom tableref="pages">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>pages</Var>
			</Atom>
			<Atom tableref="volumes">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>vol</Var>
			</Atom>
			<Atom tableref="numbers">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>num</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>note</Var>
			</Atom>

			<Atom tableref="notes">
				<!--  ckey -->
				<SKFunction skname="SK11">
					<Var>manID</Var>
				</SKFunction>
				<Var>annote</Var>
			</Atom>

		</Exists>
	</Mapping>

<!--
Author(authId, authName)
->
authors(SK0(authId), authName)
-->
    <Mapping id="M8" >
<Uses/>
      <Foreach>
        <Atom tableref="Author">
	  <Var>authId</Var>
	  <Var>authName</Var>
	</Atom>
      </Foreach>
      <Exists>
        <Atom tableref="authors">
	  <!-- citKey -->
	  <SKFunction skname="SK0">
	    <Var>authId</Var>
	  </SKFunction>
	  <Var>authName</Var>
        </Atom>
      </Exists>
    </Mapping>

  </Mappings>
  <Data>
	<InstanceFile name="Article">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>article.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="ArticlePublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>articleRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="Author">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>author.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="Book">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>book.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="BookPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>bookRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="InCollection">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>incollection.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="InCollPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>incollectionRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="InProceedings">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>inproceedings.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="InprocPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>inproceedingsRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="Manual">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>manual.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="ManualPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>manualRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="Misc">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>misc.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="MiscPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>miscRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="TechReport">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>techreport.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
	<InstanceFile name="TechPublished">
		<Path>resource/exampleScenarios/Amalgam/data1</Path>
		<FileName>techreportRel.txt</FileName>
		<ColumnDelim>|</ColumnDelim>
	</InstanceFile>
</Data>
<ConnectionInfo>
	<Host>localhost</Host>
	<DB>amalgam</DB>
	<User>lordpretzel</User>
	<Password/>
	<Port>5432</Port>
</ConnectionInfo>
</this:MappingScenario>

redpajama_set_name: RedPajamaGithub