text:
SunsetRecordsMalta
FREE DELIVERY/SHIPPING ON ORDERS OVER 30€
Four Tet - New Energy
Four Tet is the pseudonym Kieran Hebden uses for his electronic productions at the interface of techno, experiment and micro-sampling. "New Energy" is already his ninth Four Tet album since "Dialogue" in 1999
His last work, "Morning/Evening", appeared in 2015, but met with divided criticism: With a running time of about 20 minutes, it contained just two songs, which were arranged virtuously, but not very accessible. The whole thing was more reminiscent of sounds Hebden had recorded in the mid-zeros with jazz drummer Steve Reid
So it is all the more gratifying that the London-based producer with the 14 tracks of "New Energy" has apparently reverted to his tried and tested methodology, known and appreciated from the past, and created harmonic, straightforward, forward-driving tracks from his hodgepodge of samples. By the way: If you can't get enough of it, you should check out the numerous remixes Four Tet produced in the last two years for The XX, A$AP Rocky and Oneohtrix Point Never, among others.
Sign up and we will send you our latest news and offers!
Sunset Records Malta
57, Triq San Piju V
Sliema, SLM1540
SLM1540
vinyl@sunsetrecordsmalta.com
© 2021, SunsetRecordsMalta. Powered by Shopify


text:
Home » Palliative care and hospice pain experts provide best practice care guidelines
Palliative care and hospice pain experts provide best practice care guidelines
Pain experts provide guidelines for care
Hospice to help hospitals provide palliative care
Hospice nurses must provide spiritual care
Dementia Updates for Primary Care Providers
Alzheimer's Disease: What the Primary Care Physician Needs to Know
One hospice reduces pain 100% in 48 hours
Hospices may be the leaders in pain management, but most could improve their efforts by following best practice guidelines and initiating a quality improvement process, several pain experts say. "It's been well documented over the years that pain is poorly managed for many reasons," says Frank Forte, MD, director of medical oncology/hematology and director of palliative medicine at Staten Island (NY) University Hospital.
"Not the least of which is the fear people have of side effects, the fear of becoming addicted, the fear that it will be stigmatized, and a lot of other things that are both patient- and doctor-related," he says. "Many patients who are older think it's good to suffer in silence and think good people don't complain — so, for all of these reasons, chronic pain and cancer pain have been poorly managed."
Forte has been involved with PC Quick, a collaborative quality improvement project, funded by the RAND Corp. of Santa Monica, CA, and the United Hospital Fund of New York City. "One of the initiatives we did was to see whether or not pain could be better managed at our hospital," he says. "Before that, we had formed a palliative consultation service, so we did a comparison to see whether pain was relieved better with patient consultations or during the usual and customary way of caring for them."
After analyzing outcomes among 29 patients, it became obvious that patients who received care from the consultation service had better and faster pain relief than those who didn't, Forte notes. "So, our goal was to make this an initiative where everyone would do better," he adds.
The Hospice of the Western Reserve of Cleveland also has a continuous quality improvement process for pain management that was instituted in 2000, reports Mary Kay Tyler, MSN, CNP, pediatric nurse practitioner/team leader and chair of the pain subcommittee. "We are constantly reevaluating our practice and making sure we have the most cost-effective tools to assess pain," she explains.
The hospice has always followed pain management basics and maintains a transdisciplinary team approach to pain management, notes Bridget J. Montana, MS, APRN, MBA, chief operating officer. "It's everyone's responsibility to observe and report," she says. "Any time a team member is with a patient, they'll observe the patient's pain and ask the individual to rate the pain."
If the patient's pain level differs from what is usually reported or if the patient reports feeling uncomfortable, then this information is reported to the primary nurse and the rest of the team, Montana adds. Everyone involved in patient care, including the hospice volunteers, are trained and educated about pain assessment and management, she says.
As a result of the hospice's pain program, a recent chart audit of 109 patient charts showed that of the 64% of patients who experienced pain, 75% had their pain reduced within 24 hours and 100% had their pain reduced within 48 hours, Montana says.
The positive results were achieved partly because of the hospice's adoption of a tool that can be used to assess pain among patients who are unable to verbally indicate their discomfort, Tyler says. The PAINAD scale, which was developed by nurse researchers through the Department of Veterans Affairs, enables clinicians to use nonverbal cues to determine a patient's level of pain and discomfort, she explains. (See PAINAD scale.) "PAINAD was developed for patients with dementia, and we have adapted it to use with any patients who are noncommunicative," Tyler says. "It looks at nonverbal cues, including facial grimacing, crying, things like that."
Caregivers also are educated
Hospice staff educate caregivers to use the tool so they can observe the loved one and report their observations to a nurse, she adds. "This is particularly important in our elderly and pediatric populations," Tyler says.
Also, the hospice uses pain management protocol cards, which are continuously updated. These are laminated and placed on a ring so nurses can carry them on patient visits, Montana says. (See principles of pain management chart.) "The cards are tied into our drug list, not only for the proper medication for symptoms, but also for looking at pharmacokinetics and the economics of drug prescriptions," she says.
The hospice has a preferred drug list, as many hospices have these days, and this helps solidify the best practices, says Janice Scheuffler, PharmD, clinical pharmacist with the Hospice of the Western Reserve.
Staff are audited for compliance
The hospice also uses audits to make certain staff are following pain management best practices and to evaluate why problems have arisen, she says. "We have an audit committee that looks at outcomes measurements on all kinds of topics, including pain, and we hit charts and outcomes research hard," Scheuffler adds.
Another dimension to the hospice's pain management best practices is the staff's focus on a holistic approach to reducing pain and suffering, Tyler says.
Industry taking notice
While the physical aspect of pain and suffering is the easiest to understand, the hospice and palliative care industry increasingly are recognizing that there are many things that cause people to suffer, she notes. For example, patients also might suffer from distress caused by spiritual questions of why this is happening to them and the financial stress of wondering how the family will continue financially without them, as well as emotional problems resulting from loneliness and loss, Tyler explains.
The hospice's pain management committee has been working to determine the chief circumstances that cause suffering among the hospice's patient population, she reports. This type of holistic approach to pain management is important because if a patient is suffering from a spiritual, financial, or emotional problem, then it may be difficult to manage the patient's physical pain unless this other problem is addressed, Tyler says. "The health care community throws pain and suffering together, but they're very different," she notes.
Research has shown that patients view pain and suffering as separate entities and, even patients who report no pain frequently will report experiencing some suffering.1
"We're very conscious that suffering is such an all-encompassing emotion that we don't want people to go in with a checklist, asking, 'Are you suffering? Is this bothering you?'" Tyler says. "We want to integrate assessing suffering into our practice and educate staff about how to identify when someone might be suffering."
1. Baines BK, Norlander L. The relationship of pain and suffering in a hospice population. Am J Hospice Palliat Care 2000; 17(5):319-327.
Frank Forte, MD, Director of Medical Oncology/ Hematology, Director of Palliative Medicine, Staten Island University Hospital, Nalitt Institute, 256 Mason Ave., Staten Island, NY 10305. Telephone: (718) 226-6606. E-mail: fforte@siuh.edu.
Bridget J. Montana, MS, APRN, MBA, Chief Operating Officer, Hospice of the Western Reserve, 300 E. 185th St., Cleveland, OH 44118-1330. Telephone: (216) 383-3730.
Janice Scheuffler, PharmD, Clinical Pharmacist, Hospice of the Western Reserve, 300 E. 185th St., Cleveland, OH 44118-1330.
Mary Kay Tyler, MSN, CNP, Pediatric Nurse Practitioner/Team Leader, Chair, Pain Subcommittee, Hospice of the Western Reserve, 10645 Euclid Ave., Cleveland, OH 44106-2206. Telephone: (216) 502-4440.
Hospice Management Advisor Archives
Hospice Management Advisor 2005-07-01
Pain management project includes hospital pathway
Making pain management education top priority
Use the four-box method to enhance decision making
Don't be fooled by the illusion of patient safety
Aspirin prevents strokes in middle-aged women

redpajama_set_name: RedPajamaCommonCrawl


text:
/* eslint-disable ember/no-new-mixins */
import Mixin from '@ember/object/mixin';
import { on } from '@ember/object/evented';
import { set } from '@ember/object';
import { deprecate } from '@ember/debug';

export default Mixin.create({
  init(...args) {
    deprecate(
      '`EKOnInsertMixin` of ember-keyboard is deprecated. You can achieve this behavior by using the `on-key` helper, or by using `@keyResponder` in conjunction with a `did-insert` modifier.',
      false,
      {
          id: 'ember-keyboard.activate-keyboard-on-insert-mixin',
          for: 'ember-keyboard',
          since: '6.0.2',
          until: '7.0.0',
          url: 'https://adopted-ember-addons.github.io/ember-keyboard/deprecations#activate-keyboard-on-insert-mixin'
      }
    );

    return this._super(...args);
  },

  activateKeyboardWhenPresent: on('didInsertElement', function() {
    set(this, 'keyboardActivated', true);
  })
});

redpajama_set_name: RedPajamaGithub


text:
namespace crashpad {

namespace {

// These are the core-generating signals.
//
// On macOS, these come from 10.12.3 xnu-3789.41.3/bsd/sys/signalvar.h sigprop:
// entries with SA_CORE are in the set.
//
// For Linux, see linux-4.4.52/kernel/signal.c get_signal() and
// linux-4.4.52/include/linux/signal.h sig_kernel_coredump(): signals in
// SIG_KERNEL_COREDUMP_MASK are in the set.
constexpr int kCrashSignals[] = {
    SIGABRT,
    SIGBUS,
    SIGFPE,
    SIGILL,
    SIGQUIT,
    SIGSEGV,
    SIGSYS,
    SIGTRAP,
#if defined(SIGEMT)
    SIGEMT,
#endif  // defined(SIGEMT)
#if defined(OS_LINUX) || defined(OS_CHROMEOS)
    SIGXCPU,
    SIGXFSZ,
#endif  // defined(OS_LINUX) || defined(OS_CHROMEOS)
};

// These are the non-core-generating but terminating signals.
//
// On macOS, these come from 10.12.3 xnu-3789.41.3/bsd/sys/signalvar.h sigprop:
// entries with SA_KILL but not SA_CORE are in the set. SIGKILL is excluded
// because it is uncatchable.
//
// For Linux, see linux-4.4.52/kernel/signal.c get_signal() and
// linux-4.4.52/include/linux/signal.h sig_kernel_coredump(),
// sig_kernel_ignore(), and sig_kernel_stop(): signals not in
// SIG_KERNEL_COREDUMP_MASK, SIG_KERNEL_IGNORE_MASK, or SIG_KERNEL_STOP_MASK are
// in the set. SIGKILL is excluded because it is uncatchable (it's in
// SIG_KERNEL_ONLY_MASK and qualifies for sig_kernel_only()). Real-time signals
// in the range [SIGRTMIN, SIGRTMAX) also have termination as the default
// action, although they are not listed here.
constexpr int kTerminateSignals[] = {
    SIGALRM,
    SIGHUP,
    SIGINT,
    SIGPIPE,
    SIGPROF,
    SIGTERM,
    SIGUSR1,
    SIGUSR2,
    SIGVTALRM,
#if defined(SIGPWR)
    SIGPWR,
#endif  // defined(SIGPWR)
#if defined(SIGSTKFLT)
    SIGSTKFLT,
#endif  // defined(SIGSTKFLT)
#if defined(OS_APPLE)
    SIGXCPU,
    SIGXFSZ,
#endif  // defined(OS_APPLE)
#if defined(OS_LINUX) || defined(OS_CHROMEOS)
    SIGIO,
#endif  // defined(OS_LINUX) || defined(OS_CHROMEOS)
};

bool InstallHandlers(const std::vector<int>& signals,
                     Signals::Handler handler,
                     int flags,
                     Signals::OldActions* old_actions,
                     const std::set<int>* unhandled_signals) {
  bool success = true;
  for (int sig : signals) {
    if (unhandled_signals &&
        unhandled_signals->find(sig) != unhandled_signals->end()) {
      continue;
    }
    success &= Signals::InstallHandler(
        sig,
        handler,
        flags,
        old_actions ? old_actions->ActionForSignal(sig) : nullptr);
  }
  return success;
}

bool IsSignalInSet(int sig, const int* set, size_t set_size) {
  for (size_t index = 0; index < set_size; ++index) {
    if (sig == set[index]) {
      return true;
    }
  }
  return false;
}

}  // namespace

struct sigaction* Signals::OldActions::ActionForSignal(int sig) {
  DCHECK_GT(sig, 0);
  const size_t slot = sig - 1;
  DCHECK_LT(slot, base::size(actions_));
  return &actions_[slot];
}

// static
bool Signals::InstallHandler(int sig,
                             Handler handler,
                             int flags,
                             struct sigaction* old_action) {
  struct sigaction action;
  sigemptyset(&action.sa_mask);
  action.sa_flags = flags | SA_SIGINFO;
  action.sa_sigaction = handler;
  if (sigaction(sig, &action, old_action) != 0) {
    PLOG(ERROR) << "sigaction " << sig;
    return false;
  }
  return true;
}

// static
bool Signals::InstallDefaultHandler(int sig) {
  struct sigaction action;
  sigemptyset(&action.sa_mask);
  action.sa_flags = 0;
  action.sa_handler = SIG_DFL;
  return sigaction(sig, &action, nullptr) == 0;
}

// static
bool Signals::InstallCrashHandlers(Handler handler,
                                   int flags,
                                   OldActions* old_actions,
                                   const std::set<int>* unhandled_signals) {
  return InstallHandlers(
      std::vector<int>(kCrashSignals,
                       kCrashSignals + base::size(kCrashSignals)),
      handler,
      flags,
      old_actions,
      unhandled_signals);
}

// static
bool Signals::InstallTerminateHandlers(Handler handler,
                                       int flags,
                                       OldActions* old_actions) {
  return InstallHandlers(
      std::vector<int>(kTerminateSignals,
                       kTerminateSignals + base::size(kTerminateSignals)),
      handler,
      flags,
      old_actions,
      nullptr);
}

// static
bool Signals::WillSignalReraiseAutonomously(const siginfo_t* siginfo) {
  // Signals received other than via hardware faults, such as those raised
  // asynchronously via kill() and raise(), and those arising via hardware traps
  // such as int3 on x86 (resulting in SIGTRAP but advancing the instruction
  // pointer), will not reoccur on their own when returning from the signal
  // handler.
  //
  // Unfortunately, on macOS, when SIGBUS (on all CPUs) and SIGILL and SIGSEGV
  // (on arm64) is received asynchronously via kill(), siginfo->si_code makes it
  // appear as though it was actually received via a hardware fault. See 10.15.6
  // xnu-6153.141.1/bsd/dev/i386/unix_signal.c sendsig() and 10.15.6
  // xnu-6153.141.1/bsd/dev/arm/unix_signal.c sendsig(). Received
  // asynchronously, these signals will not re-raise themselves autonomously,
  // but this function (acting on information from the kernel) behaves as though
  // they will. This isn't ideal, but these signals occurring asynchronously is
  // an unexpected condition. The alternative, to never treat these signals as
  // autonomously re-raising, is a bad idea because the explicit re-raise would
  // lose properties associated with the the original signal, which are valuable
  // for debugging and are visible to a Mach exception handler. Since these
  // signals are normally received synchronously in response to a hardware
  // fault, don't sweat the unexpected asynchronous case.
  //
  // SIGSEGV on macOS on x86[_64] originating from a general protection fault is
  // a more difficult case: si_code is cleared, making the signal appear
  // asynchronous. See 10.15.6 xnu-6153.141.1/bsd/dev/i386/unix_signal.c
  // sendsig().
  const int sig = siginfo->si_signo;
  const int code = siginfo->si_code;

  // Only these signals can be generated from hardware faults and can re-raise
  // autonomously.
  return (sig == SIGBUS ||
          sig == SIGFPE ||
          sig == SIGILL ||
          sig == SIGSEGV) &&

         // The signal was only generated from a hardware fault if the code is a
         // positive number not matching one of these SI_* constants. See
         // "Signal Actions" under XRAT "Rationale"/B.2.4 "Signal Concepts" in
         // POSIX.1-2008, 2016 Edition, regarding si_code. The historical
         // behavior does not use these SI_* constants and signals generated
         // asynchronously show up with a code of 0. On macOS, the SI_*
         // constants are defined but never used, and the historical value of 0
         // remains. See 10.12.3 xnu-3789.41.3/bsd/kern/kern_sig.c
         // psignal_internal().
         (code > 0 &&
          code != SI_ASYNCIO &&
          code != SI_MESGQ &&
          code != SI_QUEUE &&
          code != SI_TIMER &&
          code != SI_USER &&
#if defined(SI_DETHREAD)
          code != SI_DETHREAD &&
#endif  // defiend(SI_DETHREAD)
#if defined(SI_KERNEL)
          // In Linux, SI_KERNEL is used for signals that are raised by the
          // kernel in software, opposing SI_USER. See
          // linux-4.4.52/kernel/signal.c __send_signal(). Signals originating
          // from hardware faults do not use this SI_KERNEL, but a proper signal
          // code translated in architecture-specific code from the
          // characteristics of the hardware fault.
          code != SI_KERNEL &&
#endif  // defined(SI_KERNEL)
#if defined(SI_SIGIO)
          code != SI_SIGIO &&
#endif  // defined(SI_SIGIO)
#if defined(SI_TKILL)
          code != SI_TKILL &&
#endif  // defined(SI_TKILL)
          true);
}

// static
void Signals::RestoreHandlerAndReraiseSignalOnReturn(
    const siginfo_t* siginfo,
    const struct sigaction* old_action) {
  // Failures in this function should _exit(kFailureExitCode). This is a quick
  // and quiet failure. This function runs in signal handler context, and it's
  // difficult to safely be loud from a signal handler.
  constexpr int kFailureExitCode = 191;

  struct sigaction default_action;
  sigemptyset(&default_action.sa_mask);
  default_action.sa_flags = 0;
  default_action.sa_handler = SIG_DFL;

  const struct sigaction* restore_action =
      old_action ? old_action : &default_action;

  // Try to restore restore_action. If that fails and restore_action was
  // old_action, the problem may have been that old_action was bogus, so try to
  // set the default action.
  const int sig = siginfo->si_signo;
  if (sigaction(sig, restore_action, nullptr) != 0 && old_action &&
      sigaction(sig, &default_action, nullptr) != 0) {
    _exit(kFailureExitCode);
  }

  // If we can raise a signal with siginfo on this platform, do so. This ensures
  // that we preserve the siginfo information for asynchronous signals (i.e.
  // signals that do not re-raise autonomously), such as signals delivered via
  // kill() and asynchronous hardware faults such as SEGV_MTEAERR, which would
  // otherwise be lost when re-raising the signal via raise().
#if defined(OS_LINUX) || defined(OS_ANDROID) || defined(OS_CHROMEOS)
  int retval = syscall(SYS_rt_tgsigqueueinfo,
                       getpid(),
                       syscall(SYS_gettid),
                       siginfo->si_signo,
                       siginfo);
  if (retval == 0) {
    return;
  }

  // Kernels without commit 66dd34ad31e5 ("signal: allow to send any siginfo to
  // itself"), which was first released in kernel version 3.9, did not permit a
  // process to send arbitrary signals to itself, and will reject the
  // rt_tgsigqueueinfo syscall with EPERM. If that happens, follow the non-Linux
  // code path. Any other errno is unexpected and will cause us to exit.
  if (errno != EPERM) {
    _exit(kFailureExitCode);
  }
#endif  // defined(OS_LINUX) || defined(OS_ANDROID) || defined(OS_CHROMEOS)

  // Explicitly re-raise the signal if it will not re-raise itself. Because
  // signal handlers normally execute with their signal blocked, this raise()
  // cannot immediately deliver the signal. Delivery is deferred until the
  // signal handler returns and the signal becomes unblocked. The re-raised
  // signal will appear with the same context as where it was initially
  // triggered.
  if (!WillSignalReraiseAutonomously(siginfo) && raise(sig) != 0) {
    _exit(kFailureExitCode);
  }
}

// static
bool Signals::IsCrashSignal(int sig) {
  return IsSignalInSet(sig, kCrashSignals, base::size(kCrashSignals));
}

// static
bool Signals::IsTerminateSignal(int sig) {
  return IsSignalInSet(sig, kTerminateSignals, base::size(kTerminateSignals));
}

}  // namespace crashpad


text:
The War in The Far East
Operation Market Garden and The Border Regiment
Research Enquiry
Online Holiday Workshops
Friends' Diary
Friends Newsletters
The Border Regiment In The Great War (used condition)
Border Regiment In The Great War by By Colonel H C Wylly C.B.
Poor ccondition copy with the usual markings and some foxing. Green cloth covers with gilt vignette to front. Minor shelfwear unfortunately the binding is coming away from the book text at the front origanally presented to Officer commanding A coy 4th Battalion the Border Regiment and inscribed in ink by someone from the 2nd Battalion 1925, edges rubbed, includes maps in the rear slot.
Category: Second Hand Books
By Colonel H C Wylly C.B.
Originally presented to Officer Commanding A Coy 4th Battalion the Border Regiment and inscribed in ink by someone from the 2nd Battalion, 1925.
Poor condition copy with the usual markings and some foxing. Green cloth covers with gilt vignette to front. Minor shelf wear unfortunately the binding is coming away from the book text at the front, edges rubbed, includes maps in the rear slot.
Before the Great War the Border Regiment, recruited from the Lakeland counties of Cumberland and Westmoreland, consisted of two Regular and two Territorial battalions, plus the Regimental Depot. During the war this was increased to a total of thirteen battalions by the raising of volunteer service battalions. This history skilfully tells the story of all 13 battalions as 'one large united family'. The regiment saw service in France from 1914, while the 1st battalion was at Gallipoli the following year. In 1916, six of the regiment's battalions took part in the battle of the Somme. And In 1917, the regiment fought in the battle of Arras, at Bullecourt, and at the Battle of Messines. Six of its battalions took part in the third battle of Ypres (Passchendaele) while other battalions fought on the Salonika front in Macedonia and in Italy. In this excellent and tightly written history, as the regiment's Colonel, Maj.Gen. E.G. Sinclair MacLagan writes in his preface the author ' has recorded the doings of the different Battalions in six separate theatres of war, and has merged them into one consecutive narrative'. illustrated by 14 photographic plates and seven maps.
1ST EDITION When Dragons Flew
Arnhem A Tragedgy of Errors
Cumbria's Museum of Military Life
Alma Block, The Castle, Carlisle,
Cumbria, CA3 8UR
T: 01228 532774 E: enquiries@cmoml.org
www.cumbriasmuseumofmilitarylife.org
Cumbria's Museum of Military Life is run by the King's Own Royal Border Regiment Museum Trust, a Registered Charitable Trust No. 271943 and accredited under the Arts Council of England Accreditation Scheme.
Cumbria's Museum of Military Life uses the email marketing website MailChimp to manage email newsletters and marketing. By signing up to the newsletter, you are agreeing to the following:
The transfer of your contact information to MailChimp and the storage of this information in the Museum's MailChimp account
That we will send you newsletters from the Museum's MailChimp account
That we may track interactions for email marketing and purposes
Cumbria's Museum of Military Life will never pass contact details on to any other third parties and all contact details will only be used to get in touch with subscribers directly.
If you wish to unsubscribe at any time, you can contact the Museum, or simply select 'Unsubscribe' at the bottom of any previous newsletter.


This is a large, richly colored slab of petrified Araucaria (extinct Conifer) wood from Ambilobe, Madagascar. It is 15 x 12 and both sides have been polished showing off the amazing mineralization of this fossil. It is from the early Triassic period, approximately 220 million years old, close to the time the first dinosaurs appeared on the planet.


When you have your meta tags set up, I recommend using Google Webmaster Tools to check your work. If you don't have a Google Webmaster Tools account, set one up for free here.
You need to verify your site to be able to access information about how the site is indexed in Google. Additionally, the pages you have worked on need to be indexed in Google. I've previously written a post on how to get your Joomla site indexed in Google.
To see how the meta tags are rated by Google, choose your site and then 'Diagnostics'. Under this menu, you'll find 'HTML Suggestions'.
Using Google Webmaster Tools, it's very easy to spot any place in your site where you might have missed the title and/or description.
For instance, I spotted something I didn't think about earlier: When you have a section or category blog view, you might have enabled automatic pagination. The pages following the first one, will have titles like 'Page 2', 'Page 3' etc. That's not very helpful. I haven't found any way of changing these titles using the joomla core. With sh404SEF or another SEF extension, this is easily done.
As you can see from this example, the default meta description from the Joomla Global Configuration is used on 30 pages.
Some components are quite lacking in the meta tags department. And sometimes they create a lot of pages automatically, so it's hard to tell if all title tags are OK. The 'Missing title tags' page presents the culprits.
As the title tag of the page is among the most important optimization factors of a page, you should make sure that they are all unique. As you can see - the search page on my site has 30 instances in the Google index. All with the same meta description. This is due to the fact that I use SuperBlogger from Joomlaworks to create tag search. Thus, there are permalinks from each tag to the search page, which gives Google a link to follow and a page to index.
However, there are no automatic way of creating unique meta description for the search page (that I know of, anyway). You need to enter these manually into sh404SEF.
Good luck working with meta tags in Joomla. If you have a large site, this task can be a large one. However, it's great fun seeing your site improve in the search engines after doing this work correctly.
Don't hesitate to comment if you have any questions.


text:
Why Quiq?
Breakthrough Technology
Conversational AI Engine Dive into the AI that powers solutions for your business.
Bot Design Studio Discover why the world's biggest brands trust our signature bot design.
Conversational Design and Tuning Explore our thoughtful approach to design and agile iterations.
Next-Generation Contact Center Transform your contact center from a business cost to a business driver.
Best-in-Class Solutions
Conversational Care Get an overview of how Quiq solves common customer service issues.
Conversational Commerce See how you can use Quiq to increase revenue.
Customer Success Obsession
Customer Stories Gain insight into how our customers deliver amazing business results.
Convert Calls to Text Give customers the option to text you vs. waiting on hold.
Enterprise-Grade Security See why our SOC-2 certification is just the beginning.
Outbound Messaging Move the revenue needle with two-way outbound messaging.
Payments Boost revenue with secure payments by text messaging.
Rich Messaging Enable rich multimedia to ramp up results.
Surveys Understand how your customers feel in the moment with in-context surveys.
Translation Communicate with customers in their native or preferred languages.
Apple Messages for Business
Twitter Direct Messages
Google Business Messaging
Customer Knowledge Base
Developer Knowledge Base
Events From our annual Quiq Connect conference to appearances and more.
Guides and Reports E-books, whitepapers, and other value-packed reading material.
Videos Watch on-demand webinars, product demos, and more.
ROI Calculator Model the potential impact of partnering with Quiq for your business.
Delve into research, how-tos, trends, and tips on all things messaging.
Quiq Privacy Policy
This Privacy Policy covers how we collect, use, disclose, transfer, and store Your (our Customers') Personal Data. This policy applies to the https://quiq.com/ website and to all Quiq hosted software and services.
This privacy policy is comprehensive, covering all aspects of the Personal Data we collect, the uses of the Personal Data and our compliance with specific regulatory laws like the GDPR and CCPA. To make this policy more consumable, the following summarizes our Privacy Policy:
We collect Personal Data reasonably necessary to deliver our hosted software and services to You and to operate our business.
We use this Personal Data only for the business purposes of running our business and delivering our hosted software service to You
We maintain commercially reasonable safeguards to protect Your Personal Data
We will never sell or distribute Your Personal Data to a third party except as necessary to deliver the hosted software service, as directed to do so by You, or to comply with applicable laws.
This General Privacy Policy ("Privacy Policy") applies to Quiq, Inc., (collectively "we," "us" or "our").
The Controller of Your Personal Data processed under this privacy policy is Quiq, Inc., which has its principal place of business in Bozeman, Montana, USA.
"You", "Your", or "Customer": An organization which controls an instance of Quiq's hosted software. A Customer may subscribe to Quiq's software through a SaaS Agreement or gain access through free trials or other arrangements under Quiq's standard Terms of Service. "You", "Your", or "Customer" may also include our business partners who resell or distribute Quiq hosted software and whose employees interact with Quiq personnel.
"End-user": An individual that interacts with a Customer through Quiq's hosted software. End-users are typically customers of Quiq Customers and use Quiq's hosted software to communicate with the organization that is Quiq's Customer.
Privacy Policy Contents
This Privacy Policy is intended for visitors of quiq.com and for You, our Customers. The exercise of Personal Data subject rights under this privacy policy does not apply to End-users. The applicable Customer is the Personal Data controller for an End-user. And Customers configure the Quiq hosted software to connect with End-users via the following third-party messaging channels*: Apple Messages for Business, Facebook Messenger, Google's Business Messaging, Instagram, Google Rich Business Messaging, SMS/Text, Twitter Direct Messages, and WhatsApp. Each of the third-party messaging channels are Personal Data controllers for End-users using those services and each third-party messaging channel has its own applicable privacy policy. If You are an End-user and You contact Quiq under this Privacy Policy, we will do our best to help connect You to the applicable Customer who is Your Personal Data controller. Likewise, for End-users using any of the third-party messaging channels listed above, those third-party messaging channels' websites and their privacy policies should be reviewed.
*The list of third-partner messaging channels may be updated at any time. Please refer to https://quiq.com/sub-processors/ for the most current list.
Personal Data We Process
Personal data refers to any information relating to an identified or identifiable individual person ("Personal Data").
We organize the Personal Data we process into these basic categories: Website Traffic Data, Billing and Account Data, and Product Data.
Website Traffic Data
We may collect Personal Data or request that certain Personal Data be provided to us from visitors to our website. The sources from which we collect Personal Data include:
Personal Data collected from visitors to our website, https://quiq.com/, such as browsing history, information about other websites directing traffic to our website, links clicked in email or other websites and cookies or other storage used to track website visitor sessions. We use Website Traffic Data to optimize the content delivered and navigation of our website; and
Data collected directly from the visitor or the device relating to an identified or identifiable individual, and may include direct identifiers such as name, postal and email address, phone number, and online or indirect identifiers such as login account, login password, marketing preferences, social media account, and/or IP address, and the transcripts of messaging conversations visitors have with us on our website, https://quiq.com/; and
when we link other data with visitor's Personal Data, we will treat that linked data as Personal Data.
We will not collect or process special categories of Personal Data, such as data concerning health, race, ethnicity or political opinions, or deduce in any way this type of information from data we collect from our website.
Billing and Account Data
Billing and Account Data from business Customers includes the business Customer's contact(s) name, email address, business phone number, Quiq subscription information, and may include company credit card information or other payment information. In some circumstances, a business Customer purchases our hosted software and services from a trusted third-party service provider, reseller, or app store. In those circumstances, Your Billing and Account Data is processed by the relevant third party and we may receive a copy of Your Billing and Account Data to keep proper business records. See below an example of Billing and Account Data and what we use it for:
What we use it for
Name To customize our communications by addressing You by Your name
Billing address To send invoices and subscription correspondence
Email address To send You invoices, purchase receipts and subscription correspondence
Username To manage Your account and facilitate Your login into the service
Masked credit card number To process the payment and billing records
License type To enable features based on the purchased license
Renewability To check if a given subscription can be renewed under the same or similar terms
Subscription renewal date To help us validate the period the license is active
Expiration date To check whether a license is current
Trial user To add a grace period prior to the paid period of the subscription
Purchase order number To assist You in properly classifying our invoices
Product Data from Customer users and End-users includes two sub-categories:
Device Data includes information about the Customer's operating system, network, and hardware environment, including the Quiq hosted software used by the Customer, and
Service Data includes information about the Quiq hosted software usage and includes the transcript of text messages from End-users, Quiq hosted software usage statistics and logs, and the Customer's and End-user's IP addresses. Quiq includes features that allow End-users to authenticate with You and to pay you. When processing authentication and payment messages between End-users and You, Quiq does not access sensitive authentication information or credit card information. Quiq processes Device Data and Services Data to provide the Quiq services, to secure the Quiq services and the hosting environment used to provide the Quiq services, to improve the Quiq services and to enable the Quiq functionality for its Customers. Quiq does not sell Device Data or Services Data to third parties.
Why We Process Your Personal Data
We use Your Personal Data for the following purposes and on the following grounds:
On the basis of fulfilling our contract with Customers or entering into a contract with You on Your request, in order to:
Process purchase of our hosted software or services from us, our partners or our trusted third- party service providers' online stores;
Provision the activation, implementation, and performance of the hosted software or service;
Keep our hosted software or services up-to-date, safe and free of errors, including implementation of new hosted software features and versions;
Verify Your identity and entitlement to hosted software or services and when You contact us for support, or You access our services;
Process Your purchase transactions;
Update You on the status of Your orders and licenses;
Manage Your subscriptions and user accounts; and
Provide You with technical and customer support; and
Fulfil our contractual obligations specified in our agreement with You.
On the basis of Your consent or subject to Your opt-out, in order to:
Send You commercial messages from Quiq including without limitation via Your business email address or business phone number
For visitors to https://quiq.com and other affiliate sites, to send commercial messages from Quiq including without limitation via the visitor's business email address
Depending on applicable law, we will ask for Your consent or provide You the opportunity to opt-out to commercial messages.
In order to fulfill legal obligations, we process Your Personal Data when it is necessary for compliance with a legal, tax, accounting, anti-money laundering, legal order, sanction checks or other obligations to which we are subject.
On the basis of our legitimate shared interest, we will use Your Personal Data to:
Communicate about improvements, changes, or modifications to Your Quiq hosted software and services;
Evaluate and to improve the performance and quality of our hosted software, services, and websites, develop new hosted software, train our employees and to understand and analyze usage trends;
Make our systems and applications more secure;
Maintain the effective performance of our business by ensuring necessary internal administrative and commercial processes (e.g., finances, controlling, business intelligence, legal & compliance, information security etc.); and
Establish, exercise, or defend our legal rights.
Your interests are a key part of our decision-making process and have been considered in all the above-mentioned processing activities. We believe we have achieved a fair balance between privacy and operations. In any case, You have the right to object to those processing operations. For more details, please see section the section below on Your Privacy Rights.
Balancing Legitimate Interests
Before relying on our legitimate interests, we balanced them against Your interests and made sure they are compelling enough. With respect to the purposes below we consider necessary to explain what our interests are in detail.
We have a legitimate interest for messaging our business customers about performance improvements and about new or different hosted software and services from Quiq. We do not sell our business customers' email addresses to third parties.
Product and business improvement
We have a legitimate interest to use necessary Personal Data to understand users' download, activation, and interactions with our hosted software. This purpose of this processing is to optimize the user experience of our website and hosted software and services.
How We Disclose Your Personal Data
We may disclose Your Personal Data to our service provider partners to the extent necessary in order to fulfill the functionality of the hosted software and services, to fulfill the security of the software and the hosted environment, to enable access to the service through chat or text, with public authorities when required by applicable law, or to our advisors who provide tax, accounting, legal, and security services to Quiq. If we disclose Your Personal Data, we require its recipients to comply with equivalent privacy and confidentiality requirements, and security standards as our own
We may use contractors and service providers. (collectively "Subprocessors") to process Your Personal Data for the purposes described in this Privacy Policy. The current list of Sub-processors engaged in Processing Personal Data for the performance of a service, including a description of their processing activities, can be found at https://quiq.com/sub-processors; in addition, contractors and service providers may include professional consultants (including financial auditors, legal advisors, and security auditors, to defend or to exercise our rights), and marketing analytics and/or survey analytics software suppliers, such as we use Google Analytics on our website.
Distributors, Resellers
We may provide Your Personal Data to our partners for the purpose of distribution, sale or management of our hosted software. Our partners may communicate with You about Quiq hosted software or services. In addition, You may purchase our hosted software directly from our distributor, a reseller, or an app store. Because Your relationship in these cases is with that distributor, reseller or an app store, such third party will also process Your Personal Data.
Sometimes our Service Providers and partners, for example our distributors, resellers, app store partners, and messaging companies, will be independent controllers of Your Personal Data and their terms and conditions, end user license agreements ("EULA") and privacy statements will apply to such Personal Data processing.
Cookies Providers
Our website uses cookies to personalize the experience on our site, to tell us which parts of our website people have visited, to help us measure the effectiveness of campaigns, and to give us insights into user interactions so we can improve our communications and our website. Depending on applicable law, while using our website, visitors may be asked t
Analytics Tool Providers
We use analytical tools, including third-party analytical tools, which allow us, among other things, to identify potential performance or security issues with our hosted software, to improve their stability and function, to understand how You use our hosted software, and how visitors use our website so that we can optimize and improve the user experience, and to evaluate and improve our campaigns. We use Service and Device data for analytics.
While we generally prefer using our own analytical tools, we sometimes need to partner with other parties, which have developed and provide us with their own tools and expertise. Below, we list these partners and tools and their privacy policies.
Tool (provider)
Type of Analytics
Google Analytics (Google) user behavior https://support.google.com/analytics/answer/6004245
https://support.google.com/analytics/answer/6366371?hl=en&ref_topic=2919631 US, Ireland
In certain instances, it may be necessary for us to disclose Your Personal Data to public authorities or as otherwise required by applicable law. No Personal Data will be disclosed to any public authority except in response to:
A subpoena, warrant or other process issued by a court or other public authority of competent jurisdiction;
A legal process having the same consequence as a court-issued request for Personal Data, in that if we were to refuse to provide such Personal Data, it would be in breach of local law, and it or its officers, executives or employees would be subject to liability for failing to honor such legal process;
Where such disclosure is necessary for us to enforce our legal rights pursuant to applicable law; and in each case
We will notify You before we disclose your Personal Data unless the law or legal procedure requires otherwise.
Mergers, Acquisitions and Corporate Restructurings
We may transfer Your Personal Data as part of a reorganization, merger, acquisition or sale of our business, stock, or assets. We will promptly notify You after any such deal and outline Your choices in that event, if applicable. Information including Personal Data relating to our business may be shared with other third parties to evaluate and conclude the transaction, subject to an agreement with the third party protecting the confidentiality and ensuring the appropriate security of any Personal Data processed by the third party.
Cross-Border Transfers of Personal Data among Quiq Entities and to Third-Party Vendors
We are a U.S.-based business that provides hosted software and services all around the world. To reach all our customers and provide all of them with our software, we operate on an infrastructure that is located in the U.S. and the EEA and may eventually span the world. The servers that are part of this infrastructure may therefore be in a country different than the one where You live. Regardless of the location of the server supporting the Quiq hosted software(s), this privacy policy applies to all Personal Data processed.
For Personal Data processed in the EEA, when we transfer Personal Data outside of the EEA, we put in place appropriate safeguards, such as standardized contracts approved by the European Commission. Situations for Personal Data processed in the EEA where we transfer Personal Data outside of the EEA include transmission of messages on messaging channels operating outside the EEA, the support of our hosted software and services, the processing of transactions and of Your payment details, and the delivery of updates and upgrades. Further, an outside-EEA transfer may also occur in case of a merger, acquisition, or a restructuring, where the acquirer is located outside of the EEA (see the section on Mergers, Acquisitions, and Restructuring).
How We Protect Your Personal Data
We maintain administrative, technical, and physical safeguards for the protection of Your Personal Data. More information is available in the Information Security Policy Manual located here [insert link]
Access to the Personal Data is limited to authorized personnel who have a legitimate need to know based on their job descriptions, for example, employees who provide technical support or who service billing. In the case of third-party contractors who process Personal Data on our behalf, similar requirements are imposed. Where an individual employee no longer requires access, that individual's credentials to access Personal Data are revoked.
We secure Personal Data as described in our Information Security Policy Manual [include link].
Physical safeguards for Personal Data are described in our Information Security Policy Manual (include link].
We strive to process no more Personal Data from You than is required by the purpose for which we collect it. This, in turn, helps reduce the total risk of harm should Personal Data loss or a breach in security occur.
Quiq hosted software are not intended or marketed for use by minors.
How Long We Store Your Personal Data
We will hold Your Personal Data on our systems for the following periods:
For Billing and Account Data, for the duration of a customer's subscription and upon expiration or termination of the subscription, for as long as we have a legal obligation or for our legitimate interests in establishing legal rights;
For Product or Service Data, only as long as necessary for the purposes of a particular hosted software or service. The standard retention period for Product or Service Data are for the duration of the subscription plus twelve months following expiration or termination of the subscription.
For Website Data, data is maintained for as long as it is helpful to improve the functioning of the website and then it is deleted; contact information is maintained for as long as the visitor maintains active contact information with Quiq and when it is no longer valid it is labeled as inactive data.
For the categories of Personal Data listed above, until the later of, the time periods described above or after the Customer requests deletion of the Personal Data.
The Personal Data we collect from You may be stored, with risk-appropriate technical and organizational security measures applied to it, on in-house as well as third-party servers in the United States, in the EEA, as well as in locations that we or our trusted service providers and partners operate.
In all cases, we follow generally accepted standards and security measures to protect the Personal Data submitted to us, both during transmission and once we receive it.
You have the following rights regarding the processing of Your Personal Data:
Right to information – Right to receive information about the processing of Your Personal Data, prior to processing as well as during the processing, upon request.
Right of access – Aside from the information about the processing of Your Personal Data, You have the right to receive a copy of Your Personal Data undergoing processing.
Right to rectification – We should process accurate Personal Data; if You discover inaccuracy, You have the right to seek correction of inaccurate Personal Data.
Right to erasure ("right to be forgotten") – You have the right to erasure of Your Personal Data, but only in specific cases stipulated by law, e.g., if there is no legally recognized title on our part for further processing of Your Personal Data (including protection of Quiq's legitimate interests and rights).
Right to data portability – The right to receive Personal Data which You have provided and is being processed on the basis of consent or where it is necessary for the purpose of conclusion and performance of a contract, in machine-readable format. This right applies exclusively to Personal Data where processing is carried out by automated means.
Right to object – Applies to cases of processing carried out in legitimate interest. You have the right to object to such processing, on grounds relating to Your situation, and we are required to assess the processing to ensure compliance with all legally binding rules and applicable regulations. In case of direct marketing, we shall cease processing Personal Data for such purposes after the objection.
Right to withdraw consent – In the case of processing based on Your consent, You can withdraw Your consent at any time, by using the same method (if technically possible) You used to provide it to us (the exact method will be described in more detail with each consent when You provide it). The withdrawal of consent shall not affect the lawfulness of processing based on Your consent before its withdrawal.
Right to restriction of processing – You have the right to restriction of processing of Your Personal Data if: You are contesting the accuracy of Your Personal Data, for a period enabling us to verify the accuracy of Your Personal Data; the processing is unlawful and You oppose the erasure of the Personal Data and request the restriction of its use instead; we no longer need the Personal Data for the purposes of the processing, but they are required by You for the establishment, exercise or defense of legal claims; or You have objected to processing of Your Personal Data, and there is a pending verification whether our legitimate grounds override Your interests.
Right to contact a supervisory authority or court – You may contact and lodge a complaint with the supervisory authority – The Office for Personal Data Protection in Ireland or Your local authority or a relevant court.
You can submit Your requests relating to Your Personal Data subject rights by contacting us at: privacy@quiq.com. The fulfillment of Personal Data subject rights listed above will depend on the category of Personal Data and the processing activity. In all cases, we strive to fulfill Your request.
We will action Your request within one month of receiving a request from You concerning any one of Your rights as a Data Subject. When we are faced with an unusually large number of requests or particularly complicated requests, the time limit may be extended to a maximum of another two months. If we fail to meet these deadlines, we would, of course, prefer that You contact us to resolve the situation informally.
Where requests we receive are unfounded or excessive, in particular because they repeat, we may either: (a) charge a reasonable fee taking into account the administrative costs of providing the information or communication or taking the action requested; or (b) refuse to act on the request.
This section applies to residents of California, U.S.
Categories of collected Personal Data
You can see all categories of collected personal information listed in the section Personal Data We Process.
Sources from which the personal information is collected
You can find information about the sources of Personal Data in the section Personal Data We Process.
Business or commercial purpose for collecting or selling personal information
You can find all purposes of processing Your personal information listed in the section Why We Process Your Personal Data.
Categories of third parties with whom the business shares personal information
You can find all categories of recipients of personal information listed in the section How We Disclose Your Personal Data. Quiq does not and will not sell (as such term is defined in the California Consumer Privacy Act) Your personal information we collect.
Our hosted software is not targeted at minors under 16 years of age. We therefore have no knowledge of any sale of Personal Data concerning them.
know what personal information is being collected about You;
know whether Your personal information is sold or disclosed and to whom;
say no to the sale of personal information (right to opt out);
request deletion of Your personal information; information will be deleted if no exception applies
(including our right to defend our lawful interests);
access Your personal information; specific information shall be provided in a portable and, to the extent technically feasible, in a readily useable format but not more than twice in a 12-month period;
equal service and price, even if You exercise Your privacy rights (right to non-discrimination).
Under California Civil Code § 1798.83, we are required to disclose to consumers the following information upon written request: (1) the categories of personal information that we have disclosed to third parties within the prior year, if that information was subsequently used for marketing purposes; and (2) the names and addresses of all such third parties to whom such personal information was disclosed.
We have not disclosed any such personal information as defined by the California Civil Code § 1798.83 regarding any California resident for marketing purposes.
Request Submission
You can submit Your requests to us at: privacy@quiq.com
Do Not Sell / Quiq. If You are a California resident, the California Consumer Privacy Act ("CCPA") provides You with the right to opt out of the "sale" of Your personal information. Under the CCPA, "personal information" includes information that is not necessarily tied to Your identity as an individual directly but may be associated with Your device. This covers identifiers such as IP addresses, web cookies, web beacons and mobile Ad IDs, among others. In many cases, this type of information is not associated with You, but there are unique identifiers that could be. Similarly, the term "sell" is defined to include not just selling in exchange for money, but also sharing or transferring personal information (including information that does not directly identify an individual as described above) in exchange for anything of value, which covers a much broader set of situations and types of exchanges. At the same time, certain things are not considered "sales," such as cases when (1) personal information is shared with a service provider that is contractually prohibited from using the personal information for any purpose beyond the service specifically requested ("service provider exception"), or (2) when the consumer has directed a company to disclose the personal information ("consumer directed exception").
Quiq Does Not "Sell" Your Personal Information. Quiq does not sell Your personal information, like Your name, address, or email. Under the service provider exception discussed above, we share some of Your personal information with our service providers, whom we bind by contract or agree to comply with terms that limit the use of the information solely to provide a service for us or on our behalf (for example, we use partners to provide software hosting services), or in the limited additional circumstances outlined in our Privacy Policy (such as for the purpose of performing security audits on the hosted software or to comply with the law).
End of California CCPA section
To exercise any of Your rights, or if You have any other questions or complaints about our use of Your Personal Data and its privacy, write our Privacy Team at: privacy@quiq.com
We reserve the right to revise or modify this Privacy Policy. In addition, we may update this Privacy Policy to reflect changes to our Personal Data practices. If we make any material changes, we will notify by means of a notice on this website. We encourage You to periodically review this page for the latest information on our privacy practices.
This Policy was last updated in January 2023.
Bot Design Studio
Conversational AI Engine
Conversational Design and Tuning
Next-Generation Contact Center
Convert Calls to Text
Enterprise-Grade Security
Outbound Messaging
Rich Messaging
Quiq vs. LivePerson
Get Quiq
© Copyright 2022 Quiq. All Rights Reserved.


text:
Q: Rabbitmq camel spring boot auto config I have camel and rabbitmq configured like the following and it is working.  I am looking to improve the config setup.
pom.xml
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-rabbitmq-starter</artifactId>
    <version>2.19.1</version>
</dependency>

application.yml
spring:
  rabbitmq:
    host: rabbithost-url
    port: 5672
    username: my-user
    password: my-password

config bean
@Configuration
public class CamelConfig {

    @Resource private Environment env;

    @Bean
    public ConnectionFactory rabbitConnectionFactory(){
        ConnectionFactory connectionFactory = new ConnectionFactory();
        connectionFactory.setHost(env.getProperty("spring.rabbitmq.host"));
        connectionFactory.setPort(Integer.valueOf(env.getProperty("spring.rabbitmq.port")));
        connectionFactory.setAutomaticRecoveryEnabled(true);
        // more config options here etc
        return connectionFactory;
    }
}

Route Example
@Component
public class MyRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {

     from("direct:startQueuePoint")
          .id("idOfQueueHere")
          .to("rabbitmq://rabbithost-url:5672/TEST-QUEUE.exchange?queue=TEST-QUEUE.queue&autoDelete=false&connectionFactory=#rabbitConnectionFactory")
          .end();
    }
}

Would like to improve the following?  Or at least see if its possible?
1)  How do I leverage spring boot autowiring.  I feel like im duplicating beans by added the custom CamelConfig > rabbitConnectionFactory?  Its not using the RabbitAutoconfiguration?
2)  When I am using the connection factory I am referencing the rabbitmq-url and port twice?  I am adding it in the rabbitConnectionFactory bean object and in the camel url?  e.g.
.to("rabbitmq://rabbithost-url:5672/ ..etc.. &connectionFactory=#rabbitConnectionFactory")

can I not just reference it once in the connection factory?  tried the following without the host as its included in connectionFactory but it did not work.
.to("rabbitmq://TEST-QUEUE.exchange?queue=TEST-QUEUE.queue&autoDelete=false&connectionFactory=#rabbitConnectionFactory")

The 1st working example I am using is based off this.
 camel.apache.org/rabbitmq example (see Custom connection factory )

A: Found from looking at the newer docs on github.
Notice that now no url needed in the start of the route.
.to(rabbitmq:exchangeName?options
Full camel route example below
.to(rabbitmq:exchangeName?queueName&exchangeType=direct&connectionFactory=#rabbitConnectionFactory&autoDelete=false

Here is url:
https://github.com/apache/camel/blob/master/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc

redpajama_set_name: RedPajamaStackExchange


Quick Wrap Horse Bell Boots is rated 4.90 out of 5 by 10.
I love the quick wrap over reach boots. Super easy to put on, hold up great & I received them in a few days.
These boots last much longer than others I've tried. The Velcro doesn't fray out as soon.
I bought these 2 weeks ago because my horse was nicking the inside of his front hoof at the corona band. Bingo ... no more nicks. The boots fit perfectly ... medium-size for a 16 h Selle Francais. Easy on, easy off .. light, secure ... they pick up sand a bit when he rides, but wash easily.
They are great! Horse wears them upside down to protect wounds on pasterns. The wound gets air/oxygen all day long and if he rolls, the boots protect the injury. Thanks!
Covers & protects whole hoof. Easy to put on. Use them on all my show stock.
These boots are the best I have found for the trail riding I do with my Standardberd. He has a smooth, fast trot that extends his hind leg to reach the front hoof easily. By using these boots, he has not lost a shoe or cut himself in any way. Quick wrap are very easy to put on, and last me, at least, a year or more. I always buy a new pair, when they start to wear out. I won't be without them.


https://www.tradingdepot.co.uk/bette-select-160-x-70-bath-no-tap-holes-front-side-overflow 417 Bette Select 160 x 70 Bath No Tap Holes, Front Side Overflow https://www.tradingdepot.co.uk/media/catalog/product/3/4/3420000_large.jpg 285.25 285.2500 GBP OutOfStock /Bathroom/Bathroom Suites/Baths /Brands/Bette/Bette Baths/Bette Select Baths /Brands/Bette/Bette Baths/All Bette Baths /Bathroom/Bathroom Suites/Baths/Straight Baths/Double Ended Baths The Bette Select bath comes in a clear cut rectangular shape with sharp edges, but softer inside edges to create added comfort. The Select bath comes in a range of sizes, and with the overflow in a choice of 3 different positions, allowing a more spacious area for both bathing and showering. This traditional bath is a perfect design, to fit in with any bathroom suite. This particular option is the 160 x 70 bath, with no pre-drilled tap holes and overflow at the front side.
This particular option is the 160 x 70 bath, with no pre-drilled tap holes and overflow at the front side.


23 information store in it.
43 * This deallocates all the memory associated with the string space.
57 want to clean up everything from this file.
69 * Symbol table initialized and c is a null terminated string.
78 * we store efficiently.
87 * before the terminating '\0'.
97 * for the life of the ASCEND process.
102 * Returns NULL if the pointer s given is not from the table.
103 * Otherwise returns the pointer given.
106 * is in the table.
111 * Print a report on stdout about the string hash table.
112 * if (noisy) prints lots of goop.
118 * symbol table and the symbols it contains.


text:
Quarry expansion leads to Bell B30E for Skene, with original D-series still in play
Skene Group Construction Services Ltd, a leading independent operator within the construction supply sector, has drawn on seven years of success using a Bell Equipment B30D, and has further invested in an evolved B30E ADT.
The new-breed machine was brought into the fleet within one of Skene's quarry sites in September, working alongside the company's existing B30D, which continues to deliver.
Skene Group, a company based in Fife which originated in 1968, is a major supplier to the construction industry, manufacturing and supplying concrete blocks, ready-mix concrete and aggregates throughout Scotland and beyond. The company's own plant and equipment are utilised within its two quarries and Contract Division, carrying out civil engineering works within both private and commercial sectors.
The company's quarries have expanded in recent years to meet with growing commercial and domestic demand, leading Skene's taskforce of hardworking ADTs, excavators and wheel loaders to perform considerable working hours involving stripping, primary and secondary crushing, and tipping.
"The machines we choose for working within the quarries are certainly put through their paces," says Skene's Joint Managing Director, Darren Forrester. "We use the ADTs daily, primarily to perform overburden tasks to access rock, but also to shift and retrieve material from the quarries' main faces for subsequent processing at our static plants.
"The use of capable ADTs has been essential in achieving these tasks effectively, and we've tried and tested the benefits of various makes and models over the years. We bought our first Bell ADT seven years ago, and have been truly impressed with the machine's reliability and performance, right to the present day."
That machine is still 'very much up and running' and has an impressive 7,000 hours under its belt. Its robust performance has been a key contributor in forming Darren's decision to invest in another Bell. However, during the time Skene's B30D has been grafting in the quarry, the leading ADT manufacturer has been further developing the capabilities future machines, and has presented a new and improved line of vehicles to the market – the E-series.
Development of the E-series took the course of five years, and led machines to be stringently tested within some of the harshest mine sites in the world. With increased suspension travel and an A-frame adaptation to give operators a more independent ride, E-series vehicles have already proved a 'driver success'. The series offers 6x6-technology to provide class leading power and weight-ratios together with advanced engine and drivetrain characteristics, while the improvements made to the onboard diagnostics enable the interface to be more detailed, but also user friendly.
"From experience, we can see why Bell Equipment's D-series platform was so well regarded by the industry throughout its lifetime, so by carrying its successful platform through to the smaller trucks in the new E-series range and by changing the front suspension to an A-frame layout, there's a formula in place for another winning succession of machines.
"In short, we've been really impressed with the new B30E ADT. It's a cracking machine that we've used every day since delivery, without a hitch.
"The machine type has, like our own relationship with Bell Equipment, evolved over the years, and grown from strength to strength."
Darren makes reference to his company's relationship with Bell's Area Sales Manager, Sandy Fairweather, the sales team member who has been a first point of contact for Skene since the purchase of his firm's initial ADT was negotiated: "In our experience, when you buy with Bell, you get access to a full customer care package, not only from an aftersales team, but from the people you started the sales process with. We like that, because it makes you feel as though, as a customer, you've remained valued and are continued to be looked after.
"We know that should a need ever arise, we can contact Sandy directly, and he will get any issues sorted personally, and we like to think that reflects our own business ethos well.
&ld
"As a company, we're proud of the strong position we've created for ourselves within the national construction industry, and have always strived to find ways to continually commit to moving our business forward, and facilitating success for our clients, locally and nationally.
"This latest investment in an evolved machine and its potential to deliver, chimes perfectly with that valued Skene approach."
uo;As a company, we're proud of the strong position we've created for ourselves within the national construction industry, and have always strived to find ways to continually commit to moving our business forward, and facilitating success for our clients, locally and nationally.
Wheeled Loader
Bell Plant Security
Pre Owned Equipment
Product & Technical Support
Bell Reman


text:
What about Equality of Opportunity?
November 26, 2018 By Maryanne Datesman Leave a Comment
Over 90 percent of Americans believe that equality of opportunity is an "absolutely essential" American ideal—according to Stanford University.
Two questions come to mind immediately:
What does equality of opportunity mean to Americans?
And where did this "absolutely essential American ideal" come from?
First of all, what does "equality of opportunity" mean?
Americans believe everyone should have an equal chance for success—not that all people should actually be equal. This is an important distinction.
Equality of opportunity is very much tied to the ideal of the American Dream: the chance for our children to have a better life than we do. Traditionally this has meant that they will enjoy a higher standard of living.
It is also tied to the ideal of individual freedom: the right of all Americans to do what they want in life—to define their personal American dream and to choose their own path to the success they desire.
Second, where does the American ideal of equality of opportunity come from?
It started with the first settlers who came to the North American continent in the 1600s, leaving everything behind to seek a better life in the new "land of opportunity."
The belief was articulated as a national value in the Declaration of Independence of 1776:
While it continued to develop as an American ideal through the 1800s, sizable portions of the population were excluded: African Americans, women, and Native Americans. Their legal access to the right of equality of opportunity was delayed until well into the 20th century, and we are still working to make this aspiration a reality for all.
What do equality of opportunity, the American Dream, and individual freedom have in common?
We believe that these three ideals are the foundation of our country—they are what makes the United States unique. From the beginning, immigrants from all over the world have traveled here seeking these benefits, and they come here still. Our common belief in individual freedom, equality of opportunity, and the American Dream, defines our identity and our traditional cultural values.
Indeed, the organization More in Common conducted a huge study that revealed how Americans feel about these cultural values:
To be American, for most, does not require someone to be white or to be Christian. Rather it is to believe in freedom and equality and to pursue the American Dream.
Our task is to focus on these values, see where they came from, and analyze how they have endured since the founding of our nation.
So far, we have examined the value of freedom.
Join us now as we tackle the complex issue of equality of opportunity.
Maryanne & George Datesman | Chautauqua 2017 – 4th of July Fest
American Handbook: What your grandparents want you to know
By Maryanne K. Datesman
November 24, 2018 DRAFT
Chapter 6: Equality of Opportunity: A mighty aspiration and a challenging paradox
Thomas Peterffy arrived in the United States in December of 1965, with a single suitcase containing a change of clothes, his slide rule, and a handbook on surveying. He was 20 years old, fleeing communist oppression in Hungary. He did not speak any English and he did not have any money.
According to an article in Forbes magazine, Peterffy sought refuge in a Hungarian community in Spanish Harlem:
"It was a big deal to leave home and my culture and my language," he says. "But I believed that in America, I could truly reap what I sowed and that the measure of a man was his ability and determination to succeed. This was the land of boundless opportunity."
Peterffy worked his way up from a job in a surveying firm to founding his own company in the 1970s. He was a pioneer in creating ways to conduct stock trades electronically, even before the digitization of the markets. In the 1990s, he founded the Interactive Brokers Group and today, at age 72, his financial worth is estimated at $12.6 billion.
Clearly, the United States did prove to be the land of boundless opportunity for Peterffy, as it has for numerous other immigrant entrepreneurs. Forty-two of the Forbes 400 Richest People in America are naturalized citizens who immigrated to this country, and half of the American tech companies worth $1 billion or more were founded by immigrants.
The very act of immigrating, exemplified by Peterffy, is entrepreneurial, a self-selected risk taken in an effort to better one's circumstances. It's a mind-set. "You leave everything you have and get on a plane," says Forbes 400 member Shahid Khan. "You can handle change. You can handle risk. And you want to prove yourself."
This is not a new phenomenon. The tradition of immigrating to America to have a better life goes back to the beginning of our history, and it is an important factor in the development of our cultural values.
How did Equality of Opportunity become an important American cultural value?
From the beginning, our country was known as "the land of opportunity," where people could achieve anything they put their mind to, no matter who they were. Contrast that with Europe, where the class system was formalized into an "upstairs/downstairs" society. The upper class lived upstairs and the servants lived downstairs, and they lived their lives in the classes of their birth.
Imagine then, what it must have been like for the settlers to come to a new world of incredible natural resources: a multitude of trees, rich fertile farmland, wild game, an extensive system of rivers, and an agreeable climate. There were relatively few Native Americans living on this land, and they had neither the weapons nor the organization to keep the European settlers out.
Suddenly, colonists were free to create new lives for themselves and their families, and America became a land where everyone had an equal chance at succeeding. All the ingredients were there—no strong government or church to limit their freedom, no social structure that proscribed the parameters of their future lives.
Freedom and economic opportunities flourished, and the colonies evolved. When the colonists decided to band together and create a new country in 1776, they faced an enormous challenge. How could they form a government that acknowledged the great diversity in each colony, while bringing them all together under one national government?
How could they ensure that the land of opportunity would also be a land of equality of opportunity for all Americans? It was a noble experiment—governments had always been created for nations of homogeneous people. The idea of creating a system to govern a diverse heterogeneous people was new!
The United States was the first country built on shared values, rather than shared heritages!
The founders created a system where the power remained in the hands of the people, and individual rights were protected from government interference. They asserted the foundation principle of equality, and then framed a Constitution designed to give citizens equal opportunities to succeed. Citizens would have to figure out how to maintain their individual rights while respecting those of others.
Fortunately, Americans had a whole continent to work with, blessed with abundant natural resources. As the new nation began to function, restless settlers started to push west into new territory. George Washington was inaugurated as the first president in 1789, and the legislative and judicial branches of government began to function.
For the next 100 years, the exploration and settlement of the West had a profound effect on shaping the American character, until the frontier closed in 1890.
How did the American frontier function as a laboratory for realizing equality of opportunity?
On the western frontier, there was more of a tendency for people to treat each other as social equals than there was in the more settled eastern regions of the country. On the frontier, the highest importance was placed on what people could do in their lifetimes. Hardly any notice was taken of their ancestors. Frontier people were fond of saying, "What's above the ground is more important than what's beneath the ground."
Because so little attention was paid to a person's family background, the frontier offered a new beginning for many Americans who were seeking opportunities to advance themselves. An English visitor to the United States in the early 1800s observed that if Americans experienced failure in business, in politics, or even in love, they moved west to start over.
Opportunities were plentiful on the frontier. There was a continuous need for new settlers: farmers, skilled laborers, merchants, lawyers, and political leaders. There were fewer differences in wealth on the frontier than in the eastern states; Americans lived, dressed, and acted more alike there—rich or poor.
By the 1830s, de Tocqueville could see equality of opportunity at work on the frontier; it continued to develop and was firmly established as the settlements spread throughout the new nation.
Now here's where it gets tough. While equality of opportunity was being enshrined as an American cultural value, significant numbers of African Americans were living in slavery.
How do we reconcile the ideal of equality of opportunity with slavery?
When most Americans think about slavery, they think about conditions in the South leading up to the Civil War— in the 1850s, but we really need to go back to the colonial period to understand its history.
Slavery was a historical institution that "changed over time and differed from place to place," according to Dr. Rosemarie Zagarri, a colonial history scholar. From at least 1619, slavery existed in the American colonies, part of the global market for African slaves. Although less than 4% of them were brought to the North American continent, by 1776 there were African slaves in all 13 colonies.
In the North, they worked as "domestic servants, artisans, craftsmen, sailors, dock workers, laundresses, and coachmen." New York and Philadelphia had significant numbers of enslaved workers, and in Boston and Newport slaves made up as much as 20-25% of the population. In the agricultural South, they were needed for labor-intensive crops such as tobacco in Maryland and Virginia, and rice and indigo in South Carolina. Zagarri says that treatment and duties of enslaved workers varied in different areas.
Whatever the case, slaves were considered property that could be bought and sold. Slaves thus constituted a portion of the owners' overall wealth. Although Southern slaveholders had a deeper investment in slaves than Northerners, many Northerners, too, had significant portions of their wealth tied up in their ownership of enslaved people.
In this context, when white colonists were rebelling against British rule in 1776, they complained that they were being treated like slaves. It was an effective, emotional argument, but once they made it, the contradiction about their own slave ownership became undeniable. Slavery for blacks—freedom for whites. Zagarri states that they began to rationalize their behavior by arguing that blacks were racially inferior.
The founding fathers had to create a new government that could handle these contradictions, while still defending individual rights and freedoms, and maintaining a balance of power among the newly-created 13 states. They debated the problem of slavery and chose to leave it to the states to decide. Incidentally, the framers of the Constitution did not use the word "equality" in the document.
By the time of the American Revolution, slaves made up 40% of the population of Virginia, and 60% of South Carolina, while the percentages in New England were much lower. This would impact how the population of states would determine the number of representatives to the new republic. The Constitution called for two Senators for each state, regardless of population, while the members of the House of Representatives would be determined by the relative population of each state.
But what about the slaves? How would they be counted? The framers decided that not all people would be equally represented:
Slaves were counted as three-fifths of a person.
Women were counted as 100% of a person, but they did not have the right to vote.
Native American Indians were not counted at all, unless they paid taxes.
What happened to the institution of slavery after the Revolutionary War?
While slavery existed in all of the original colonies when the framers wrote the Constitution, there were patriots who sought to abolish it. During and immediately after the Revolution, many of the colonists did free their slaves. As time went by, slavery ended in the North, but it remained in the South. With the westward expansion from 1790 to 1860, the concern for the balance of power between the slave states and the free states continued; there was an effort to maintain an equal number of slave and free states, as new western territories entered the United States.
It is shocking to see a map of where slavery existed from the Revolutionary War to the Civil War—it covered a huge swath of territory. The United States stopped bringing in African slaves in 1808, but the American slave trade continued around the country as a thriving enterprise.
In fact, the total number of African American slaves increased dramatically—from almost 700,000 in the first census of 1790 to almost 4 million in 1860! And almost a half a million were in states and western territories that made up the Union during the Civil War!
In order to rationalize the existence of slavery in "the land of the free," there was a continuing attempt to de-humanize enslaved African American people— often tearing families apart when selling them as property. African Americans were not only considered as inferior to whites, they were thought to lack emotional ties to their family members, and be incapable of parental love.
There is a poignant moment in The Adventures of Huckleberry Finn where Huck realizes that this is not true. While floating down the river, Huck hears his slave friend Jim crying in the night. Jim spends his night watches "moaning and mourning" for his wife and two children. Though "it don't seem natural," Huck concludes that Jim loves his family as much as white men love theirs:
When I waked up just at daybreak he was sitting there with his head down betwixt his knees, moaning and mourning to himself. I didn't take notice nor let on. I knowed what it was about. He was thinking about his wife and his children, away up yonder, and he was low and homesick; because he hadn't ever been away from home before in his life; and I do believe he cared just as much for his people as white folks does for their'n. It don't seem natural, but I reckon it's so.
It is this moment when Huck's perspective on slavery and society's hypocritical, cruel principles shifts; he will not return Jim to his owner, even if it means breaking the law. Huck rips up his letter to Jim's owner, declaring that he'd rather be damned than defy his gut instinct; "I'll go to hell," he says.
What happened to attitudes about slavery as it ended?
The experience of ending slavery was different in the South and in the North. The South was willing to go to war to defend the right to have slaves, while in the North there was a gradual abolition of slavery. The last Northern state to abolish slavery was New Jersey in 1804.
According to historian Kathleen Logothetis Thomas, most northern states chose to phase slavery out "over an extended period of time, reflecting concern over race, social structure, and the economic benefits of owning slaves as property and a labor source." Adult slaves might have to continue working during their productive years, and then be freed when they grew old, for example, while their children might be enslaved until they entered adulthood.
The process of emancipation in the North was lengthy, often complicated, and may have had unintended consequences. Thomas observes that in areas where slavery was phased out over a number of years, there was "a gradual change in society instead of an abrupt one, and it allowed northern whites to transfer their assumptions about slaves and race onto the freed population."
In other words, beliefs that slaves were racially inferior were transferred onto freed African Americans.
It took a terrible, bloody Civil War (1861-1865) and a Constitutional amendment (1865) to finally end slavery throughout the United States, but its effects have continued for generations.
What a tragic paradox. In the 1830s de Tocqueville had observed the great equality of the American society at large, but he also predicted trouble between blacks and whites:
These two races are fastened to each other without intermingling; and they are unable to separate entirely or to combine. Although the law may abolish slavery, God alone can obliterate the traces of its existence.
While the cultural values were being forged in the new nation, the practice of slavery denied African Americans every single one of the country's benefits: freedom, equality of opportunity, and the chance for a better life for their children.
What is the importance of our ideals?
From the beginning, the ideal of equality of opportunity has been just that—an American ideal, an aspiration—a goal we seek for our nation.
We mentioned before that there have been major exceptions to the value of equality of opportunity in the United States: women, Native American Indians, and African Americans.
It took women until 1920 to get the right to vote, and they still may face discrimination in the workplace and unequal pay for equal work compared to men. Efforts to pass an equal rights amendment have so far not been successful.
The Native Americans were treated like foreign enemies: they were killed off, exiled to reservations, and—until 1924—denied U.S. citizenship unless they left their tribes. It was not until 1948 that Indians had full rights to vote and other benefits of citizenship in all states.
The terrible legacy of slavery continues today; there's no doubt about it. African Americans still face both implicit and explicit discrimination in the United States, a century and a half after slavery was ended.
But here's the important point to remember: the United States stands for freedom and equality of opportunity for all. Do we have perfect freedom and equality of opportunity for all now? No, we are still striving to meet these ideals. But our government was designed to give us a way to pass laws and even change the Constitution to extend these rights to all Americans.
We are still very much a work in progress. But the ideal of Equality of Opportunity for all Americans is an important value.
We deeply believe that everyone should have an equal chance to succeed.
The new book is tentatively titled, "American Handbook: What your grandparents want you to know," written from my perspective as a grandmother.
This is an awesome task, even though we will be drawing on the six cultural values presented on our website and developed in American Ways.
Here are working titles for the first twelve chapters:
Chapter 1: Desperate times call for desperate measures!
Chapter 2: Behavior, beliefs, and values: Chipping away at the cultural iceberg
Chapter 3: We are our beliefs: An overview of our traditional American cultural values
Chapter 4: Culture wars, and rumors of wars: What divides us now?
Chapter 5: Our rights and freedoms: What's so important about our Constitution?
Chapter 7: Self-Reliance: Use it or lose it
Chapter 8: Competition: Sports and the entrepreneurial spirit
Chapter 9: Hard Work: What do you do?
Chapter 10: The American Dream: Dead or alive?
Chapter 11: Patriotism is not a dirty word
Chapter 12: Civil Discourse: Talking across the political divide
The final draft version will be out on or before March 1, 2019. It will be available as an eBook, and possibly in a print version in the future.
We'd like to invite you along on this journey—let's begin a dialogue.
We want your opinions, your stories, and your wisdom. During pre-sale, which ends March 1, 2019, you can sign up for $5.00 to get behind-the-scenes updates on this project, and then receive the final draft version by March 1, 2019.


text:
All Quotes by author - Ron Reagan
" He had written my mother once that he wanted her to be the first thing he saw every morning and the last thing he ever saw. And that's how it turned out. "
" I admire the fact that the central core of Buddhist teaching involves mindfulness and loving kindness and compassion. "
" I couldn't join a party that, frankly, tolerates members who are bigots for one thing, homophobes, racists. "
" I could share an hour of warm camaraderie with Dad, then once I'd walked out the door, get the uncanny feeling I'd disappeared into the wings of his mind's stage, like a character no longer necessary to the ongoing story line. "
" I have to say that flying on Air Force One sort of spoils you for coach on a regular airline. "
" I'm aware that most people who meet me for the first time think of me in a certain way because of who my father is. That just comes with the territory. But that's been that way ever since I was a little kid as long as I can remember. I grew up that way. "
" I mean, we've had all these awful pictures from the prison in Iraq and these sort of memos floating around about justifying torture, all this kind of stuff. And it makes you want to take a shower, you know? "
" I mow my own lawn. "
" I've been to Reagan National Airport. I tell people it was named after me. "
" John McCain knows as well as anyone that Sarah Palin has no business being anywhere near the Oval Office. I'm sorry, it's got nothing to do with the fact that she wears skirts - she's grossly unqualified. "
" My father didn't know George W. Bush from Adam. "
" My father felt that children should make their own way. "
" My father never felt the need to wrap himself in anybody's mantle. He never felt the need to pretend to be anybody else. This is their administration. This is their war. If they can't stand on their own two feet, well, they're no Ronald Reagans, that's for sure. "
" My father was a public figure all my life, and so the presidency was an extension of that. I guess you get used to it, though you can stand back occasionally and think, 'Boy, this is really weird!' "
" My father was not a bully. I almost never heard him raise his voice to anybody. "
" My wife and I just prefer Seattle. It's a beautiful city. Great setting. You open your front door in the morning and the air smells like pine and the sea, as opposed to bus exhaust. "
" Neither of my parents would ever stand in the way of any of their children speaking their minds. "
" Now, ignorance is one thing, ignorance can be cured. But many of the Republican leaders opposing this research know better. "
" Stem cell research can revolutionize medicine, more than anything since antibiotics. "
" The joke in our family is that we can cry reading the phone book. "
" We can choose between the future and the past, between reason and ignorance, between true compassion and mere ideology. "
" We have three cats. It's like having children, but there is no tuition involved. "
" What do you say to your sister who poses in the nude? It's not like you are really itching to see photographs of your sister naked. I mean, it's just something that is not too exciting. "
" When you hear somebody justifying a war by citing the Almighty, I get a little worried, frankly. "
" You cannot be against embryonic stem cell research and be intellectually and therefore morally consistent, if you're not also against in vitro fertilization. "
" You look at women at the Republican convention and women at the Democratic convention. Republicans have a certain aesthetic beauty that involves more makeup, bigger hair, more lurid outfits. "
Check our other websites:
BookDark
MusicDark


Evidence of women's representation in science and engineering is often measured first in the attainment of undergraduate and graduate degrees.  In 2004, 50.4 percent of all S&E bachelor's degrees went to women. Women received the majority of bachelor's degrees in the agricultural sciences, biological sciences, oceanography, and chemistry, and they were awarded more than 40 percent of the bachelor's degrees in the earth sciences, mathematics and statistics, and atmospheric and other physical sciences, excluding physics.
Of all S&E master's degrees awarded in 2004, 43.6 percent went to women. They received the majority of master's degrees in the agricultural and biological sciences and other physical sciences, excluding physics and astronomy. They were awarded over 40 percent of the master's degrees in the earth sciences and oceanography, mathematics and statistics, and chemistry.
In 2005, 37.7 percent of all S&E doctorate degrees went to women. Women were awarded almost 50 percent of Ph. D.s granted in the biological sciences (National Science Foundation, 2006).


text:
Suspect in shooting is held on attempted murder charge
By Bill Talbott
A 50-year-old Taneytown man was being held on $200,000 bail after he was charged Wednesday with the attempted first-degree murder of his former girlfriend.
William Richard Bollinger, of the first block of E. Baltimore St., remained in the Carroll County Detention Center after a bail-review hearing yesterday.
Other charges lodged by state police after the shooting of Faye Virginia Glass, 34, are assault with intent to murder, assault, battery, and breaking and entering at the victim's house in the 6300 block of Keysville Road.
Mr. Bollinger surrendered to Carroll Sheriff John H. Brown on Wednesday.
George W. Mathias of Hanover, Pa., a friend of Mr. Bollinger, told police Mr. Bollinger walked into his house Wednesday, shouting his name to identify himself.
Mr. Mathias said, in court documents filed late Wednesday, that Mr. Bollinger appeared to be upset. He began talking, then stopped and asked, "Would you drive me to the police barracks?"
Ms. Glass, the mother of two young girls who had left their Keymar home for school shortly before the shooting, remained in fair and stable condition at the Maryland Shock Trauma Center in Baltimore yesterday, according to a spokeswoman.
When Taneytown police officer Paul Wingate, the first officer on the scene, found the woman on the kitchen floor about 8:30 a.m., she told him, "My ex-boyfriend beat me up," he reported.
However, he said, that didn't explain the large amount of blood around the woman, who was dressed in a nightgown and robe.
Officer Wingate said he asked the woman, who was lapsing in and out of consciousness, about the blood and she replied, "He shot me."
The officer asked who shot her, and she answered, "William Richard Bollinger; he lives in Taneytown," according to court documents.
Ms. Glass' gunshot wound in the upper left chest, above the heart, appeared to be from a small-caliber handgun, possibly a .22, police said.


3D reconstruction of a mouse embryo. Limbs are highlighted in green.
Jérôme Gros and his team are interested in the role of cell behaviour (cell shape, movement, division, etc.) in tissue morphogenesis and how it impacts patterning of different structures during embryogenesis of higher vertebrates. They use an integrative approach ranging from classical embryology, molecular genetics, cellular biology, state-of-the-art live imaging microscopy and biophysics to understand how cells and molecular cues interplay to shape tissues during embryogenesis.
Limb defects, which are amongst the most frequent congenital malformations in humans, are the result of deviation in normal developmental program deployment affecting limb specification, initiation or patterning. In most cases the mechanisms underlying limb abnormalities are, at the best, poorly defined. This is in part due because despite considerable advances in our understanding of normal limb morphogenesis, on a molecular level, fundamental aspects of limb formation are not understood at a cellular level. Thus, we still have a very incomplete picture of limb formation that prevents further progress in our understanding of this process. We propose to elucidate the role of dynamic cell behavior in the consecutive steps of limb specification, initiation and patterning. The elucidation of the cellular events underlying the different steps of limb development, together with their molecular regulation, represents crucial missing information, which will undoubtedly push forward the frontier of our current knowledge of normal limb formation. Importantly, these studies will provide an integrated and comprehensive framework for understanding the mechanisms underlying congenital limb malformations.
Cell Division Drives Epithelial Cell Rearrangements during Gastrulation in Chick.