<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://omeka.lawrencecatania.com/items/browse?collection=14&amp;output=omeka-xml" accessDate="2026-06-06T19:05:37-05:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>25</perPage>
      <totalResults>273</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="4459" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11688">
                <text>The Banach–Tarski Paradox</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11689">
                <text>Q: "What's an anagram of Banach-Tarski?" &#13;
A: "Banach-Tarski Banach-Tarski."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11690">
                <text>&lt;a href="https://www.youtube.com/watch?v=s86-Z-CbaHA&amp;amp;t=1138s" title="The Banach–Tarski Paradox" target="_blank" rel="noreferrer noopener"&gt;https://www.youtube.com/watch?v=s86-Z-CbaHA&amp;amp;t=1138s&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4449" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11671">
                <text>--Asking for a friend-- Since I had to deal with this level of corruption at 18 years old.(culminating with a judge saying to them, "you should be ashamed of yourselves")--And things have only become worse--&#13;
&#13;
--How would you handle a corrupt investigator whom with the help of corrupt law enforcement would manipulate a situation, plant or remove evidence to setup more circumstantial evidence to make someone look bad.--</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11672">
                <text>Handling a situation involving a corrupt investigator and law enforcement requires a strategic approach focused on legal defense, independent documentation, and external oversight. Because local agencies may be compromised, victims often need to escalate their concerns to state or federal authorities. &#13;
&#13;
Immediate Legal and Protective Steps Retain a Specialized Attorney: Contact a criminal defense or civil rights attorney immediately. They can file motions to suppress evidence that was improperly obtained or manipulated and request sanctions against the prosecution. &#13;
&#13;
Invoke Your Rights: Exercise your right to remain silent and your right to counsel. Do not answer questions or consent to searches without your lawyer present, as corrupt investigators may use maximization techniques to coerce false admissions.&#13;
&#13;
Independent Documentation: Create a secure, timestamped record of everything that occurred, including officer names, badge numbers, vehicle IDs, and verbatim quotes.&#13;
&#13;
Keep backups in multiple locations, such as cloud storage or external drives. Reporting and Escalating Misconduct If the local department's Internal Affairs Division is unresponsive or part of the corruption, use external channels: Federal Bureau of Investigation (FBI):&#13;
&#13;
The FBI investigates allegations of criminal deprivations of civil rights and public corruption. Department of Justice (DOJ): &#13;
&#13;
File a complaint with the DOJ Civil Rights Division if you believe your constitutional rights were violated. State Attorney General:&#13;
&#13;
In cases where local and county resources are exhausted or compromised, the California Attorney General (or your state's equivalent) may review the allegations. Media and NGOs: &#13;
&#13;
Investigative reporters from platforms like ProPublica or legal advocacy groups like the ACLU and the National Police Accountability Project can help expose systemic issues. &#13;
&#13;
Seeking Justice Through Civil Action If evidence was planted or removed, you may have grounds for a civil lawsuit under 42 U.S. Code § 1983 for violation of your constitutional rights. Successful suits can result in financial damages and help hold the department accountable.&#13;
&#13;
Do you have physical evidence or witness contact info that could help build a case against these specific individuals?&#13;
&#13;
--yes--&#13;
&#13;
To handle a corrupt situation effectively, you must focus on preserving the integrity of your physical and witness evidence while escalating the matter beyond local reach. &#13;
&#13;
Because corrupt actors may attempt to seize or discredit your proof, moving it to a secure, neutral environment is the most critical next step.&#13;
&#13;
1. Secure and Preserve Evidence Corruption cases often fail due to a "broken chain of custody"—any gap where the evidence could have been tampered with.&#13;
Digital Preservation: If you have photos, videos, or messages, create multiple encrypted backups. Use cloud storage (e.g., Google Drive, iCloud) with multi-factor authentication to ensure the data cannot be remotely deleted from your devices. Physical Evidence: Do not handle original items more than necessary to avoid DNA or fingerprint contamination.&#13;
Place them in secure, tamper-proof containers and, if possible, have a neutral third party (like an attorney) store them to establish a verifiable chain of custody.&#13;
Witness Documentation: Ask witnesses to write down their accounts immediately while details are fresh. If they agree, record their statements on video. Store these records alongside your physical evidence.&#13;
&#13;
2. Legal Protections Under California Law In California, planting or tampering with evidence is a serious crime under Penal Code 141 PC. Felony Charges: For law enforcement officers, evidence manipulation is a felony.&#13;
&#13;
 Brady Motions: If you are currently facing charges, your attorney can file a Brady Motion to force the prosecution to disclose any records of the investigator's past misconduct or evidence that might exonerate you.&#13;
&#13;
New 2026 Disclosure Laws: Under SB 524, California law now requires agencies to disclose if AI tools were used to draft reports and mandates the preservation of original audit trails, which can be used to spot inconsistencies in falsified reports.&#13;
&#13;
3. Escalate Beyond Local Control If local law enforcement is involved, reporting to their own "Internal Affairs" may be ineffective. Use these higher-level resources: CA Department of Justice: &#13;
&#13;
Report the misconduct through the Official Reporting Portal. The State Attorney General has the authority to investigate local crimes committed by law enforcement. Specialized Civil Rights Attorneys: Contact firms that specialize in Section 1983 lawsuits (federal civil rights violations). Firms like Rodriguez &amp; Associates or V. James DeSimone focus on these complex cases. &#13;
&#13;
--I'm not , asking for a friend--&#13;
&#13;
Strategic reporting. By securing evidence now, they protect themselves against potential future frame-ups and build a foundation for holding these individuals accountable.&#13;
&#13;
1. Secure the Evidence Immediately Corruption often involves "missing" or "altered" files. Your friend must act as their own archivist: Encrypted Backups: Upload all digital evidence (videos, texts, audio) to a secure cloud service like Google Drive or Proton Drive. Enable Two-Factor Authentication (2FA) to prevent unauthorized access or deletion.&#13;
&#13;
Chain of Custody:&#13;
If they have physical items, they should place them in a sealed container and take a photo of the seal. If possible, they should give the items to a trusted third party, like a lawyer, who can provide a signed receipt of possession. Witness Statements: Have witnesses write down what they saw, sign it, and date it. If witnesses are willing, a video-recorded statement can be even more powerful.&#13;
&#13;
2. Connect with Legal Advocates Because local law enforcement is allegedly involved, your friend needs advocates outside that power structure: National Police Accountability Project (NPAP): This organization specializes in holding law enforcement accountable. &#13;
&#13;
Use their referral directory to find a specialized attorney in California. ACLU of California: While they cannot take every case, they provide valuable "Know Your Rights" guides and occasionally take on cases with systemic corruption.&#13;
Your friend can submit a legal intake form for review. Civil Rights Specialists: Look for firms that focus exclusively on police misconduct and evidence fabrication, such as The Law Offices of Dale K. Galipo or Toni Jaramilla.&#13;
&#13;
3. Report to Oversight Agencies To bypass local corruption, reports should be made to state or federal entities: California Attorney General:&#13;
&#13;
File a formal complaint through the OAG Misconduct Portal. They have the power to investigate "pattern or practice" violations by local agencies. Federal Bureau of Investigation (FBI): The FBI investigates "Color of Law" violations, where officials use their authority to deprive someone of their constitutional rights. They can contact the local FBI field office. California State Bar:&#13;
&#13;
If the investigator is working with a prosecutor who is also corrupt, a complaint can be filed with the State Bar of California regarding unethical legal conduct.&#13;
&#13;
"******************************"&#13;
&#13;
--Also--&#13;
&#13;
"*******************", your friend must shift the focus from their own character to the investigator's history of misconduct.&#13;
&#13;
In California, several laws and legal motions are specifically designed to expose "bad actors" in law enforcement.&#13;
&#13;
1. File a Pitchess Motion This is the most powerful legal tool for attacking an officer's credibility. What it does: It allows a person to access an officer's confidential personnel file to look for past complaints of dishonesty, fabrication of evidence, or illegal conduct.&#13;
&#13;
How it works: An attorney must show "good cause"—for example, by pointing to specific discrepancies in a police report that suggest evidence was planted. &#13;
If granted, a judge reviews the records and releases relevant misconduct history to your friend's defense team.&#13;
&#13;
2. Leverage Transparency Laws (SB 1421 &amp; SB 16)California law now mandates the public release of records involving certain types of serious officer misconduct.&#13;
Sustained Dishonesty: Records regarding investigations into an officer's dishonesty, such as perjury or filing false reports, are now public. &#13;
Brady List: Prosecutors are required to maintain a "Brady List" of officers with a known history of lying or bias.&#13;
&#13;
If the investigator is on this list, their testimony is often considered "tainted" and can be used to impeach them in court.&#13;
&#13;
3. File a "Brady Motion" Under the landmark Brady v. Maryland ruling, the prosecution must disclose any evidence that would hurt their case or help your friend's defense. &#13;
&#13;
If the investigator has been disciplined for planting evidence in the past, the prosecution is legally obligated to turn that information over. Filing this motion forces the government to admit if the investigator is "unreliable".&#13;
&#13;
4. Criminal Charges (Penal Code 141)In California, planting or tampering with evidence is a felony for law enforcement officers under Penal Code 141 PC. If your friend has physical evidence or witnesses, they should report it directly to the California Attorney General’s Misconduct Portal or the FBI’s Public Corruption unit. A criminal conviction—or even an active investigation—for evidence tampering effectively ends an investigator's professional credibility.&#13;
&#13;
5. Media and Investigative Reporting Because local departments may "whitewash" misconduct through secret settlements, reaching out to investigative journalists can be effective. Organizations like the Investigative Reporting Program at UC Berkeley or ProPublica often track corrupt officers that local agencies refuse to discipline. &#13;
&#13;
--Also--&#13;
&#13;
1. File a Decertification Complaint (SB 2)As of January 2023, California law (SB 2) allows the state to permanently revoke an officer's license for "serious misconduct," including dishonesty or planting evidence. Action: Your friend can submit a complaint directly to the Commission on Peace Officer Standards and Training (POST).Why it works: POST’s Accountability Division independently reviews cases of "serious misconduct" even if the local department cleared the officer. If the state decertifies them, they are banned from being a peace officer anywhere in California.&#13;
&#13;
2. Report to the California Department of Justice (DOJ)The state DOJ will review complaints if all local resources (like IA) have been exhausted without resolution. Action: Use the State Attorney General’s Reporting Portal. Justification: Your friend should emphasize that they have already filed an IA complaint and that the local department is failing to investigate credible evidence of a crime (Penal Code 141 PC: evidence tampering).&#13;
&#13;
3. Contact the FBI for "Color of Law" Violations If state and local officials are working together to manipulate a case, this is a federal crime. The FBI investigates officials who use their power to deprive others of constitutional rights. Reporting: They can submit a tip at tips.fbi.gov or call their local field office (e.g., Los Angeles: 310-477-6565).Focus: Focus on the "Public Corruption" or "Civil Rights" division when reporting.&#13;
&#13;
4. Consult a Specialized Civil Rights Lawyer Since your friend has physical evidence and witness info, they should meet with an attorney who specializes in Section 1983 lawsuits (federal civil rights). Many provide free initial evaluations. Relevant Firms: Burris Nisenbaum Curry &amp; Lacy: Known for handling high-profile California police corruption cases. Law Offices of Dale K. Galipo: Specializes in civil rights violations and police misconduct. National Police Accountability Project (NPAP): A nationwide directory to find specialized local lawyers&#13;
&#13;
&#13;
--what if this person is an agent of the court--&#13;
&#13;
If the person is an "agent of the court"—such as a probate investigator, child custody evaluator, or court-appointed attorney—their misconduct falls under judicial oversight rather than just standard law enforcement channels. They are considered an extension of the judge, which means the court itself has a responsibility to police their behavior.&#13;
&#13;
1. Report Directly to the Presiding Judge In California, the Presiding Judge of the county’s superior court is responsible for overseeing court operations and the conduct of court-appointed individuals. Written Complaint: Submit a formal, written complaint detailing the specific acts of misconduct, such as evidence manipulation or false statements. &#13;
&#13;
Internal Oversight:&#13;
&#13;
 For probate-specific issues, you can also contact the Court Executive Officer (CEO), as probate investigators are often court employees subject to internal HR and administrative review&#13;
&#13;
2. File a Complaint with the Commission on Judicial Performance (CJP)While the CJP primarily handles judges, they also have shared authority over "subordinate judicial officers," which includes court commissioners and referees.&#13;
&#13;
Step 1: You must typically file your complaint with the local superior court first. &#13;
&#13;
Step 2: If you are unsatisfied with the court's response, you have 30 days to ask the CJP to review the matter.&#13;
&#13;
3. State Bar Reporting (If They Are an Attorney)Many agents of the court, like Guardians Ad Litem or court-appointed counsel, are licensed attorneys. &#13;
&#13;
Mandatory Reporting: Under Rule 8.3, other lawyers (like your friend's attorney) are required to report another lawyer if they have credible evidence of criminal acts or dishonesty that affects their fitness to practice law. &#13;
&#13;
Public Complaint: Anyone can file an ethical complaint with the State Bar of California for free.&#13;
&#13;
4. Direct Civil Action You can sue a court agent directly if their actions are "wrongful in nature," such as fraud or intentional negligence, under Civil Code § 2343.Filing a Civil Complaint: Use Form CM-010 (Civil Case Cover Sheet) and a pleading paper template to outline how the appointee's bias or evidence tampering caused harm. &#13;
&#13;
Strength in Numbers: If multiple people file complaints against the same appointee, the court may consolidate them, making the misconduct harder to ignore.5. Remedies in Active Cases &#13;
&#13;
If this agent's manipulation is currently affecting a case, your friend's attorney should immediately: Object at Trial: Misconduct must be objected to immediately so the judge can strike the tainted evidence. &#13;
&#13;
Request a New Trial: If the agent’s actions materially prejudiced the outcome, your friend may be entitled to a new trial or a dismissal of charges.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11673">
                <text>https://www.investigativestudios.org/ &#13;
&#13;
https://www.propublica.org/&#13;
&#13;
https://www.fbi.gov/investigate/public-corruption&#13;
&#13;
https://civilrights.justice.gov/&#13;
&#13;
https://engage.nationalpoliceaccountability.org/civicrm/profile?gid=10&amp;reset=1&#13;
&#13;
https://www.aclu-nj.org/&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4436" public="1" featured="0">
    <fileContainer>
      <file fileId="1839">
        <src>https://omeka.lawrencecatania.com/files/original/25af108a51c57393709a71366f45cb5e.jpg</src>
        <authentication>987aa41d1e1c047a1dfe078380e92383</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11641">
                <text>Boundary Badassery: Daring to Set Boundaries&#13;
&#13;
By Nancy Levin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11642">
                <text>A reformed people pleaser not only learns the profound benefits of healthy boundaries in her own life, she deconstructs and reframes them for you&#13;
&#13;
A boundary is, in essence, where you end and another person begins. I define it as a limit that you set to define what you will and will not do, or what you will or will not accept or tolerate from others.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11643">
                <text>&lt;a href="https://bestselfmedia.com/boundary-badassery/" title="Boundary Badassery: Daring to Set Boundaries  By Nancy Levin" target="_blank" rel="noreferrer noopener"&gt;https://bestselfmedia.com/boundary-badassery/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4423" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11615">
                <text>archiving MUSHCode</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11616">
                <text>Since 2002, MUSHCode.Com has been archiving MUSHCode, class logs and tutorials for MUSH and MUX games. There are currently 432 files listed. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11617">
                <text>&lt;a href="https://www.mushcode.com/" title="archiving MUSHCode" target="_blank" rel="noreferrer noopener"&gt;https://www.mushcode.com/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4405" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11579">
                <text>--explain why I feel family court of today and their arms like domestic violence has turned into a disease.--</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11580">
                <text>It sounds like you’re describing a system that feels like it’s lost its way—where what should be a "cure" (protections like domestic violence laws) has instead become a source of further harm or "infection" for the families involved.&#13;
People who feel this way usually point to a few core reasons why the system feels "diseased":&#13;
&#13;
    The "Weaponization" of Allegations: Because the stakes in custody battles are so high, some feel that domestic violence claims are occasionally used strategically to gain an upper hand. This creates a "fever" of litigation where the truth gets buried under tactical moves.&#13;
    A "One-Size-Fits-All" Approach: The system often treats every conflict with the same heavy-handed protocols. This can escalate minor disputes into high-conflict legal wars, similar to how an overactive immune system can attack a healthy body.&#13;
    The Profit Motive: Critics often argue that the "arms" of the court—lawyers, evaluators, and monitors—benefit financially from keeping the conflict alive. When a system profits from a problem, it has little incentive to "cure" it.&#13;
    The Trauma Loop: Instead of resolving pain, the adversarial nature of the court often re-traumatizes everyone involved, especially children. It can feel like a cycle that breeds more resentment rather than providing a resolution. &#13;
&#13;
It’s a deeply frustrating experience when a system meant to provide safety feels like it’s actually feeding the fire.&#13;
Are you dealing with a specific case right now, or are you looking for resources on how to navigate a high-conflict situation?&#13;
&#13;
--People are aware and corrective legislation is being introduced across the United States as well as the rest of the world. To adjust the overreach that is permanently damaging children at the behest of corrupt human desires.--&#13;
&#13;
Yes, a significant wave of legislative reform is currently sweeping across the United States and internationally, aimed specifically at addressing systemic failures in family courts and prioritizing child safety over adult legal strategies&#13;
. These laws often target the "diseased" aspects of the system you mentioned—such as unregulated reunification programs and the sidelining of abuse allegations. &#13;
Key Legislative Reforms in the United States&#13;
Recent laws focus on making child safety a "threshold issue" that must be resolved before any other custody decisions are made. &#13;
&#13;
    Kayden’s Law (Federal &amp; State): Inspired by the tragic murder of 7-year-old Kayden Mancuso, this federal provision (part of the Violence Against Women Act Reauthorization) incentivizes states to reform their laws.&#13;
        New Jersey (2026): Governor Phil Murphy signed New Jersey Senate Bill S4510 in January 2026, which mandates that child safety be the primary consideration in custody cases and limits court-ordered therapy to "scientifically valid" practices.&#13;
        Pennsylvania: Similar legislation (SB 78) focuses on requiring evidentiary hearings to vet abuse allegations before granting unsupervised visitation.&#13;
    Piqui’s Law (California): Named for 5-year-old Piqui, who was murdered by his father despite his mother's warnings to the court. California SB 331 prohibits courts from ordering "reunification treatments" that involve no-contact orders or the use of private youth transporters.&#13;
    Kyra’s Law (New York): Under consideration in early 2026, Kyra's Law would require courts to hold prompt hearings when a party makes "facially-credible" allegations that a child is unsafe. &#13;
&#13;
International Shifts&#13;
The global legal landscape is also adjusting to better protect children and modernize family dynamics. &#13;
&#13;
    Japan (2026): Japan's 2026 Amended Civil Code represents its most significant family law change since 1948, introducing optional joint custody while establishing new mechanisms for the court to resolve specific disputes on an issue-by-issue basis rather than broad, rigid orders.&#13;
    Australia (2025): Changes to the Family Law Act 1975 beginning June 10, 2025, require courts to consider the economic effect of family violence when determining property settlements, recognizing that abuse has long-term financial impacts on victims.&#13;
    Hague Convention Standards (2026): Judges globally are moving toward clearer rules on "habitual residence" to prevent the tactical moving of children across borders during high-conflict disputes. &#13;
&#13;
Core Focus of These Changes&#13;
&#13;
    Mandatory Training: Requiring judges and court staff to undergo evidence-based training on domestic violence, coercive control, and trauma.&#13;
    Banning "Unproven" Therapies: Restricting the use of "reunification camps" or treatments that rely on separating a child from a protective, bonded parent.&#13;
    Transparency: New requirements for judges to state their reasoning on the record, especially when safety concerns or a child's expressed preferences are involved.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4399" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11565">
                <text>German Patent and Trademark office&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11566">
                <text>Centre of intellectual property protection&#13;
&#13;
The German Patent and Trade Mark Office (DPMA) is the centre of expertise in the field of industrial property protection in Germany. Protection of intellectual property is our statutory duty. Just under 2,800 staff work at our offices in Munich, Jena and Berlin. We examine inventions, grant patents, register trade marks, utility models and designs, administer IP rights and provide IP information to the public.&#13;
&#13;
The DPMA is the largest national IP office in Europe and the sixth largest national patent office in the world. As a higher federal authority, we operate within the portfolio of the externer Link Federal Ministry of Justice and Consumer Protection. Our headquarters are located in Munich. We are a partner in a network of national, European and international industrial property systems.&#13;
&#13;
Founded in Berlin, in 1877, as Imperial Patent Office, the DPMA looks back on almost 150 years of history. Today we are a modern service provider, offering effective protection of technical inventions, trade marks and product designs. Small and medium enterprises, the large corporate groups, research institutions and inventors receive tools to defend their intellectual property from unwanted copying.&#13;
&#13;
Information on existing IP rights is also gaining increasing importance today and in itself is becoming a factor of innovation as this knowledge can influence business decisions. On this website, we provide extensive IP information and offer online search services.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11567">
                <text>&lt;a href="https://www.dpma.de/english/index.html" title="German Patent and Trademark office" target="_blank" rel="noreferrer noopener"&gt;https://www.dpma.de/english/index.html&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4396" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11560">
                <text>--why are women so against men's sexuality, they use tools like labeling as a form of control and harassment--</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11561">
                <text>The perception that women are "against" men's sexuality or use labeling as a tool of control often stems from complex sociological and psychological dynamics regarding power, communication styles, and safety&#13;
. &#13;
1. Differences in Perceiving Intent&#13;
Research indicates that men and women often interpret sexual interest differently. Studies show that men are generally more likely than women to perceive higher levels of sexual intent in social interactions. This "overperception bias" can lead to situations where a man believes his sexual advances are welcomed, while a woman perceives them as intrusive or harassing. &#13;
2. Labeling as a Defensive Tool&#13;
From a sociological perspective, labeling (e.g., "creepy" or "harasser") is often used by women as a form of social "soft power" to navigate environments where they feel physically or socially vulnerable. &#13;
&#13;
    Negotiating Power: Women tend to view power as a negotiated process gained or lost through interactions, whereas men often view it as hierarchical.&#13;
    Establishing Boundaries: Labeling can serve as a mental shortcut or a warning to others to establish boundaries in response to perceived threats or discomfort. &#13;
&#13;
3. The "Female Control" vs. "Patriarchy" Theories&#13;
Two competing theories often explain these tensions:&#13;
&#13;
    Female Control Theory: Proposes that because female sexuality is often viewed as a higher-demand resource, women may suppress certain aspects of male sexuality to maintain the "value" of their own sexual favors in exchange for commitment or resources.&#13;
    Male Control / Patriarchal Theory: Suggests that societal norms are constructed to maintain male dominance, and that "sex-negative" attitudes or shaming are actually tools used by broader society—not just women—to enforce rigid gender roles. &#13;
&#13;
4. Communication and "Genderlect"&#13;
Communication styles play a significant role. According to Genderlect Theory, women often focus on inclusion and support, while men focus on information and status. Misunderstandings occur when these distinct "cultural dialects" clash, leading one side to feel controlled and the other to feel harassed. &#13;
Would you like to explore how specific communication strategies can help bridge these gaps in understanding between genders?&#13;
&#13;
--specific communication strategies--&#13;
&#13;
Bridging the communication gap between men and women regarding sexuality involves shifting from reactive "labeling" to proactive, clear, and empathetic dialogue. Effective strategies focus on establishing safety and clarity before, during, and after sexual interactions.&#13;
 &#13;
1. Proactive Boundary Setting&#13;
Instead of waiting for a boundary to be crossed, clearly communicate limits in a non-sexual context. &#13;
&#13;
    The "User Manual" Approach: Conduct self-reflection to identify your own "hard limits" and preferences before discussing them.&#13;
    Optimal Timing: Discuss sexual expectations when both parties are relaxed, fully dressed, and outside of a sexual setting.&#13;
    Specific Requests: Use clear, concrete language (e.g., "I'm not comfortable with X") rather than vague hints that can be misinterpreted. &#13;
&#13;
2. "I" Statements vs. "You" Statements&#13;
To reduce defensiveness and the feeling of being "labeled" or controlled, frame communication around your own internal experience. &#13;
&#13;
    Avoid Blame: Instead of "You are being creepy," try "I feel uncomfortable when this boundary is pushed".&#13;
    Focus on Feelings: Use phrases like "I notice I feel lonely when..." rather than "You never want..." to keep the conversation from escalating into a power struggle. &#13;
&#13;
3. Active Listening and Validation&#13;
Listening is as critical as speaking to ensure both parties feel heard and respected. &#13;
&#13;
    The REAL Formula: Use a structured approach: Repeat what was said, Empathize with the feelings, Acknowledge the validity of the message (even if you disagree), and Look for non-verbal clues.&#13;
    Paraphrasing for Clarity: Use phrases like "What I hear you saying is..." to confirm you have understood their intent correctly.&#13;
    Avoid "Solution-Mode": Men often jump to fixing a problem, but sometimes the goal is simply to be heard and understood first. &#13;
&#13;
4. Navigating Consent and Intent&#13;
Understanding that men and women may interpret cues differently helps in managing sexual intent. &#13;
&#13;
    Verbalize Non-Verbal Cues: Because men may rely more on non-verbal cues while women often prefer verbal ones, explicitly check in: "Are you comfortable with this?".&#13;
    Positive Framing: Discuss what you do enjoy as much as what you don't. This makes the conversation feel like an enhancement of the experience rather than just a list of restrictions. &#13;
&#13;
5. Managing Escalation&#13;
If emotions rise or a boundary is violated, use assertive but regulated communication. &#13;
&#13;
    Regulate First: Check in with your own nervous system. If you are already anxious or resentful, ground yourself with slow breathing before initiating a sensitive talk.&#13;
    Slow Down: Many conflicts escalate because partners try to resolve everything at once. Allow space for processing. &#13;
&#13;
Would you like to see practical examples of how to use these "I" statements in common social or dating scenarios?&#13;
&#13;
--What to do when people of agencies in our local and national government promote this labeling as a form of coercive control --&#13;
&#13;
1. File Official Complaints&#13;
If an agency's labeling or enforcement actions violate your civil rights, you can use established federal and local reporting mechanisms:&#13;
&#13;
    Civil Rights Violations: Report potential criminal deprivations of civil rights to your local FBI Office or through the Department of Justice Civil Rights Portal.&#13;
    Agency Misconduct: For issues involving mismanagement or abuse of power within federal agencies, contact the Office of Inspector General (OIG) or the GAO FraudNet to report abuse or mismanagement.&#13;
    Employment Retaliation: If the labeling is happening in a workplace context, the Equal Employment Opportunity Commission (EEOC) handles claims where "protected activity" (like resisting harassment) leads to retaliation. &#13;
&#13;
2. Legal Challenges and Advocacy&#13;
You can challenge the legitimacy of an agency's "labeling" or guidance if it functions as an unofficial rule without proper oversight: &#13;
&#13;
    First Amendment Challenges: Organizations often challenge government-compelled speech or labeling using the Central Hudson Test, which requires the government to prove that a restriction actually advances a substantial interest in a reasonable way.&#13;
    Congressional Review: The Congressional Review Act (CRA) allows Congress to review and potentially invalidate new administrative rules within 60 days of publication.&#13;
    Legislative Partnering: Form or join a State Coalition to partner with legislators. This can help draft better-defined laws that establish clear "behavioral markers" rather than vague labels that could be misused. &#13;
&#13;
3. Seek Oversight and Accountability&#13;
&#13;
    Office of Special Counsel (OSC): For government employees, the OSC investigates prohibited personnel practices, including political coercion.&#13;
    Local Oversight: State Attorneys General can use state laws to investigate consumer fraud or civil rights violations if federal agencies roll back protections or engage in overreach. &#13;
&#13;
4. Build Public Awareness&#13;
&#13;
    Media Outreach: Use personal stories and data to highlight how vague labeling impacts lives. This can involve writing letters to editors or participating in legislative briefings to educate court personnel and mental health professionals.&#13;
    Identify "Guidance" vs. "Law": Be aware that agencies often communicate through "guidance" (non-binding statements) to avoid judicial review. Challenging the internal procedures for contesting such guidance can sometimes strip it of its practical binding power. &#13;
&#13;
Would you like to find the contact information for your local district's U.S. Attorney's Office or a specific state oversight agency?</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4387" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11543">
                <text>FYI for fathers - &#13;
&#13;
  Family Separation Impacts: Research recognized by government medical consultants and external experts confirms that forced family separation causes "catastrophic" psychological and physiological harm to children, including PTSD, anxiety, and structural brain changes.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11544">
                <text>FYI for fathers - &#13;
&#13;
---does homeland security consider fathers of divorce and parental alienation a security threat because of the catastrophic physiological and emotional damage caused .---&#13;
&#13;
The Department of Homeland Security (DHS) does not officially classify "fathers of divorce" or "parental alienation" as a security threat. Security threats identified by the DHS and FBI are specifically categorized based on motivations like racism, anti-government sentiment, or abortion-related issues. &#13;
While the DHS does not track these groups as a general category of threat, individual actions can lead to federal oversight under specific circumstances:&#13;
&#13;
    Domestic Violent Extremism (DVE): The DHS monitors individuals who may be radicalized by "personal grievances" or "sociopolitical issues" to commit acts of violence. If a person's response to a divorce or custody battle involves plans for violence or intimidation against government officials or the public, they may be assessed as a threat.&#13;
&#13;
    Family Separation Impacts: Research recognized by government medical consultants and external experts confirms that forced family separation causes "catastrophic" psychological and physiological harm to children, including PTSD, anxiety, and structural brain changes.&#13;
&#13;
    Public Health Perspective: Some researchers and advocacy groups characterize parental alienation as a "threat to public health" or a form of "intimate terrorism," but this is a sociological and medical framework rather than a DHS security classification.&#13;
&#13;
    Legal Recognition: Parental alienation is primarily handled in family courts, where judges evaluate it as a form of emotional abuse during custody disputes. It is not currently defined as a standalone disorder by the American Psychiatric Association (APA). &#13;
&#13;
Recent political discourse has highlighted concerns about federal agencies potentially labeling vocal parents as threats, though the Department of Justice has stated its focus is on actual threats of violence rather than peaceful advocacy. ~LArry </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4383" public="1" featured="0">
    <fileContainer>
      <file fileId="1824">
        <src>https://omeka.lawrencecatania.com/files/original/3f160983ab6bcf1c4ea3f268a948c7ee.jpg</src>
        <authentication>f88257b01b4169c335dabd934df7717e</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11534">
                <text>Unesco World Heritage Site </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11535">
                <text>Heritage is our legacy from the past, what we live with today, and what we pass on to future generations. Our cultural and natural heritage are both irreplaceable sources of life and inspiration.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11536">
                <text>&lt;a href="https://whc.unesco.org/" title="Unesco World Heritage Site" target="_blank" rel="noreferrer noopener"&gt;https://whc.unesco.org/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4381" public="1" featured="0">
    <fileContainer>
      <file fileId="1823">
        <src>https://omeka.lawrencecatania.com/files/original/23f76d2ee7b2563dda6a530262259ab6.jpg</src>
        <authentication>c5e6340bb1bc5e1190e204178b7b4e13</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11529">
                <text>Electronic Circuits</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11530">
                <text>Electronic is fun to learn, especially if you can learn it by building your own circuits. To help you with that, Circuit Digest provides you with a list of popular Electronic circuits and Electronic projects with well illustrated circuit diagram and detailed explanation for a complete do-it-yourself experience. All projects are tested and verified with a working video for a hassle free learning experience. Whether you are an expert or beginner in electronics, we have something interesting for all of you. Below is our huge collection of 200+ free electronic circuits that you can build today.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11531">
                <text>&lt;a href="https://circuitdigest.com/electronic-circuits" title="Electronic Circuits" target="_blank" rel="noreferrer noopener"&gt;https://circuitdigest.com/electronic-circuits&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4359" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11482">
                <text>EASTERN PHILOSOPHY - Kintsugi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11483">
                <text>‘Kintsugi’ is the remarkable Japanese art of repairing broken pottery with elegance and grace - a tradition with a lot to teach us more generally about how to handle the broken bits of ourselves.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11484">
                <text>&lt;a href="https://www.youtube.com/watch?v=EBUTQkaSSTY" title="EASTERN PHILOSOPHY - Kintsugi" target="_blank" rel="noreferrer noopener"&gt;https://www.youtube.com/watch?v=EBUTQkaSSTY&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4352" public="1" featured="0">
    <fileContainer>
      <file fileId="1804">
        <src>https://omeka.lawrencecatania.com/files/original/5962017cf9d2eedf18494087b8a0fa53.jpg</src>
        <authentication>bb77562c24d12610945901ee8cf013c2</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11469">
                <text>Rosalind Franklin's X-ray photo of DNA as an undergraduate optical diffraction experiment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11470">
                <text>DNA top to bottom as a computer disk, unwound by the movement of the universe.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11471">
                <text>&lt;a href="https://pubs.aip.org/aapt/ajp/article/86/2/95/1057814/Rosalind-Franklin-s-X-ray-photo-of-DNA-as-an" title="Rosalind Franklin's X-ray photo of DNA as an undergraduate optical diffraction experiment" target="_blank" rel="noreferrer noopener"&gt;https://pubs.aip.org/aapt/ajp/article/86/2/95/1057814/Rosalind-Franklin-s-X-ray-photo-of-DNA-as-an&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4351" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11467">
                <text>A combination of illegal stalking, criminal harassment, and defamation (slander). The behavior—following you,, causing public scenes, and harassing you at places you eat—is a serious violation of your personal safety and rights.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11468">
                <text>For a Friend &#13;
&#13;
A combination of illegal stalking, criminal harassment, and defamation (slander). The behavior—following you,, causing public scenes, and harassing you at places you eat—is a serious violation of your personal safety and rights.&#13;
 &#13;
If you are in immediate danger, call 911 immediately. &#13;
&#13;
Here are the legal and practical steps to stop this behavior, based on standard legal practices for stalking and harassment.&#13;
&#13;
1. Document Everything Immediately &#13;
You must create a detailed, chronological log of every incident to establish a pattern of behavior for law enforcement or a court. &#13;
Log Details: Date, time, location, exactly what was said or done, and the names of any witnesses.&#13;
Evidence Collection: Take photographs or video of the individuals following you if it is safe to do so. Save recordings, emails, or screenshots of social media posts.&#13;
Witness Information: Get contact information for restaurant staff, managers, or bystanders who witnessed the harassment. &#13;
&#13;
2. Legal Actions to Take&#13;
File a Police Report: Report the stalking and harassment to local law enforcement. Even if they cannot make an immediate arrest, a police report creates an official, timestamped record.&#13;
Obtain a Restraining Order/Protection Order: You can request a "no-contact" or "stay-away" order from a court. This order legally requires the offenders to stay a certain distance away from you, your home, and your workplace.&#13;
Cease and Desist Letter: Have an attorney send a formal letter demanding the individuals stop the defamatory and harassing behavior. While not always effective, it serves as a legal warning and evidence that you tried to stop the behavior.&#13;
"John Doe" Lawsuit: If the people are acting anonymously or in a group, an attorney can file a "John Doe" lawsuit to uncover their identities through subpoenas to social media platforms or Internet Service Providers. &#13;
&#13;
3. Immediate Safety and Practical Steps&#13;
Do Not Engage: Do not respond to the harassers, as this often encourages them.&#13;
Inform Management: If you are being targeted at specific restaurants, inform management, show them the documentation if necessary, and ask them to trespass the individuals from the property.&#13;
Vary Your Routine: Change your daily routes, eating times, and routines to make it harder for them to follow you.&#13;
Secure Digital Privacy: Tighten privacy settings on social media and consider temporarily deactivating accounts to prevent them from tracking your location. &#13;
&#13;
4. Legal Definitions of the Behavior&#13;
Stalking: Defined as a "course of conduct" that includes following, monitoring, or surveilling a person, causing reasonable fear for safety or significant emotional distress.&#13;
Defamation (Slander/Libel): The act of damaging your reputation by making false, spoken (slander) or written (libel) statements to others.&#13;
Doxing: Publishing personal information with the intent to cause harassment or fear.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4350" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11465">
                <text>Addressing Police Misconduct Laws Enforced By The Department Of Justice</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11466">
                <text>&lt;a href="https://www.justice.gov/crt/addressing-police-misconduct-laws-enforced-department-justice?fbclid=IwY2xjawP9HEJleHRuA2FlbQIxMABicmlkETJ3OVBka2F2VzNGejZFS2pyc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHgEeGlwBeZEMQGNVW45KlYTLZuPOtwGRjoRrSpLDtRp4tn_kNrHUqYwuWDx__aem_yIZRrqi8UKX3fn6u-KwywQ" title="Addressing Police Misconduct Laws Enforced By The Department Of Justice"&gt;https://www.justice.gov/crt/addressing-police-misconduct-laws-enforced-department-justice?fbclid=IwY2xjawP9HEJleHRuA2FlbQIxMABicmlkETJ3OVBka2F2VzNGejZFS2pyc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHgEeGlwBeZEMQGNVW45KlYTLZuPOtwGRjoRrSpLDtRp4tn_kNrHUqYwuWDx__aem_yIZRrqi8UKX3fn6u-KwywQ&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4349" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11463">
                <text>Harassment Techniques </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11464">
                <text>&lt;a href="https://www.ohchr.org/sites/default/files/Documents/Issues/Torture/Call/Individuals/Harrassmenttechniques.pdf?fbclid=IwY2xjawP9G_VleHRuA2FlbQIxMABicmlkETJ3OVBka2F2VzNGejZFS2pyc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHso30OcCIuOTJgq8pH4rD8Na1LsnZQEBFzEMqi_DeYh4ZNj6O8sRsmgbmRb8_aem_RbyWlrvpw4Vi3agfAadIgA" title="Harassment Techniques"&gt;https://www.ohchr.org/sites/default/files/Documents/Issues/Torture/Call/Individuals/Harrassmenttechniques.pdf?fbclid=IwY2xjawP9G_VleHRuA2FlbQIxMABicmlkETJ3OVBka2F2VzNGejZFS2pyc3J0YwZhcHBfaWQQMjIyMDM5MTc4ODIwMDg5MgABHso30OcCIuOTJgq8pH4rD8Na1LsnZQEBFzEMqi_DeYh4ZNj6O8sRsmgbmRb8_aem_RbyWlrvpw4Vi3agfAadIgA&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4342" public="1" featured="0">
    <fileContainer>
      <file fileId="1801">
        <src>https://omeka.lawrencecatania.com/files/original/07ed08ada35219d99faede05737a2b99.jpg</src>
        <authentication>a9e55e7fc735babe9b828376bbe09b76</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11452">
                <text>Scribd</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11453">
                <text>Specialized knowledge on any topic, and answers you won’t find anywhere else. Welcome to our global community of thinkers.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11454">
                <text>&lt;a href="https://www.scribd.com/" title="scribd" target="_blank" rel="noreferrer noopener"&gt;https://www.scribd.com/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4341" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11449">
                <text>Dr Feng's clinical application of the Nine Palaces Acupuncture</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11450">
                <text>This article introduces the ancient Chinese theory of the Nine Palaces, which is based on the I Ching and Bagua maps. The Nine Palaces theory correlates different parts of the body with times, seasons, directions, and elements. It has significance for acupuncture. The article describes the clinical application of the Nine Palaces theory by Dr. Feng Ninghan, using the umbilicus and limbs as points based on the correlations. A case study is presented to demonstrate how Dr. Feng used the Nine Palaces theory in diagnosis and treatment by palpating specific areas on the body.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11451">
                <text>&lt;a href="https://www.scribd.com/document/418713884/Dr-Fengs-clinical-application-of-the-Nine-Palaces-Acupuncture-%E4%B9%9D%E5%AE%AB%E9%92%88%E6%B3%95-finish-pdf" title="Dr Feng's clinical application of the Nine Palaces Acupuncture" target="_blank" rel="noreferrer noopener"&gt;https://www.scribd.com/document/418713884/Dr-Fengs-clinical-application-of-the-Nine-Palaces-Acupuncture-%E4%B9%9D%E5%AE%AB%E9%92%88%E6%B3%95-finish-pdf&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4338" public="1" featured="0">
    <fileContainer>
      <file fileId="1799">
        <src>https://omeka.lawrencecatania.com/files/original/828152310d5ef8d2ac3374881e5d3975.jpg</src>
        <authentication>19c00dda047d11753689ecc51a62d0d2</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11441">
                <text>Huainanzi Part 1 - Originating the Way</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11442">
                <text>The Huainanzi is an ancient Chinese text that consists of a collection of essays that resulted from a series of scholarly debates held at the court of Liu An, Prince of Huainan, sometime before 139 BC. The Huainanzi blends Daoist, Confucianist, and Legalist concepts, including theories such as yin and yang and Wu Xing theories.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11443">
                <text>&lt;a href="https://www.youtube.com/watch?v=pZk3tAigHck" title="Huainanzi Part 1 - Originating the Way" target="_blank" rel="noreferrer noopener"&gt;https://www.youtube.com/watch?v=pZk3tAigHck&lt;/a&gt;</text>
              </elementText>
              <elementText elementTextId="11444">
                <text>&lt;a href="https://cup.columbia.edu/book/the-huainanzi/9780231142045/" title="The Huainanzi  Pub Date: April 2010  ISBN: 9780231142045  1016 Pages  Format: Hardcover  List Price: $105.00£88.00 Add To Cart  Pub Date: April 2010  ISBN: 9780231520850  1016 Pages  Format: E-book  List Price: $104.99£88.00 Get the E-Book The Huainanzi  Edited and translated by John S. Major, Sarah A. Queen, Andrew Seth Meyer, and Harold D. Roth. With additional contributions by Michael Puett and Judson Murray" target="_blank" rel="noreferrer noopener"&gt;https://cup.columbia.edu/book/the-huainanzi/9780231142045/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4337" public="1" featured="0">
    <fileContainer>
      <file fileId="1798">
        <src>https://omeka.lawrencecatania.com/files/original/04ca921da50e2b212c118944c764ff96.jpg</src>
        <authentication>4c8169da0f380d5a2c5e18ed0bcf0203</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11438">
                <text>Pyramidion of Amenemhat III Translation of the Hieroglyphs of All Four Sides</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11439">
                <text>The basalt pyramidion is the capstone of the pyramid “mr” of Amenemhat III  “imn-m-hA.t” ‘Amun is Foremost’, a pharaonic ruler from yhe 12th dynasty (ca. 1860-1814 BC).&#13;
&#13;
The pyramidion is a small pyramidal-shaped stone representing the benben  or the primordial mountain the first to emerge from the ocean at the creation of the world by the god Atum &#13;
&#13;
It´s decorated with a solar disc flanked by two cobras with outspread wings. The two eyes are to see the Neferu “nfrw”, the beauty of god Ra , as inscribed there in sunken relief. The pyramidion is from Hawar, now located at the Cairo Museum, Egypt</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11440">
                <text>&lt;a href="https://www.youtube.com/watch?v=0g_V2A2NEE4" title="Pyramidion of Amenemhat III Translation of the Hieroglyphs of All Four Sides" target="_blank" rel="noreferrer noopener"&gt;https://www.youtube.com/watch?v=0g_V2A2NEE4&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4331" public="1" featured="0">
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11426">
                <text>The Particle Data Group</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11427">
                <text>&lt;a href="https://www.particleadventure.org/" title="the Particle Data Group" target="_blank" rel="noreferrer noopener"&gt;https://www.particleadventure.org/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4328" public="1" featured="0">
    <fileContainer>
      <file fileId="1796">
        <src>https://omeka.lawrencecatania.com/files/original/f913d6fd97775107ea005ba5e57d4253.jpg</src>
        <authentication>da65059b270c9454995aff7ef2a6bdd9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11417">
                <text>Mathematical Symbols</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11418">
                <text>A comprehensive collection of symbols used in mathematics — categorized by function, subject and type into tables along with each symbol's usage and meaning.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11419">
                <text>&lt;a href="https://mathvault.ca/hub/higher-math/math-symbols/" title="Mathematical Symbols" target="_blank" rel="noreferrer noopener"&gt;https://mathvault.ca/hub/higher-math/math-symbols/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4322" public="1" featured="0">
    <fileContainer>
      <file fileId="1794">
        <src>https://omeka.lawrencecatania.com/files/original/88fa2d6fbf802a27aaa7593e73d873c3.jpg</src>
        <authentication>5737972fe56dc118559b6d6d143f9d43</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11404">
                <text>The Institute for Advanced Study</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11405">
                <text>The Institute for Advanced Study has served as one of the leading independent centers for theoretical research and intellectual inquiry since its establishment in 1930, advancing the frontiers of knowledge across the sciences and humanities. Click the tiles below to learn about the Institute's mission, history, and campus, and meet its Director, Board of Trustees, administration, and more.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11406">
                <text>&lt;a href="https://www.ias.edu/" title="The Institute for Advanced Study" target="_blank" rel="noreferrer noopener"&gt;https://www.ias.edu/&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4318" public="1" featured="0">
    <fileContainer>
      <file fileId="1793">
        <src>https://omeka.lawrencecatania.com/files/original/ceb610e99c94c6d11ab6f46cf5d7c5c6.jpg</src>
        <authentication>c3091cb8b940de919005fc6225feefa3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11394">
                <text>Opening a new era in algorithmic development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11395">
                <text>IBM Research is turbocharging algorithm development for a world with quantum computing and AI.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11396">
                <text>&lt;a href="https://research.ibm.com/blog/future-of-developing-algorithms" title="Opening a new era in algorithmic development" target="_blank" rel="noreferrer noopener"&gt;https://research.ibm.com/blog/future-of-developing-algorithms&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4313" public="1" featured="0">
    <fileContainer>
      <file fileId="1792">
        <src>https://omeka.lawrencecatania.com/files/original/8ddf089caf43014ae8a210fd7aa10987.jpg</src>
        <authentication>2ecb00801f5f305e10d8d95d3855c923</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11386">
                <text>Karnak temple</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11387">
                <text>The Great Temple of Amon at Karnak, This great national monument of Egypt has no equal. It is not a single temple, but temple within temple, shrine within shrine, where almost all the pharaohs, particularly of the New Kingdom, wished to record their names and deeds for posterity. Though most of the structures were built in honour of Amon-Ra, his consort Mut and son Khonsu, there were numerous shrines within the complex dedicated to what might be called “guest deities', like Ptah of Memphis and Osiris of Abydos.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11388">
                <text>&lt;a href="https://www.journeytoegypt.com/en/discover-egypt/karnak-temple" title="Karnak temple" target="_blank" rel="noreferrer noopener"&gt;https://www.journeytoegypt.com/en/discover-egypt/karnak-temple&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="4311" public="1" featured="0">
    <fileContainer>
      <file fileId="1790">
        <src>https://omeka.lawrencecatania.com/files/original/2b711790df1586aca3caf46a1db44389.jpg</src>
        <authentication>39ebd2cdd35b3d6eeb531cdc3658d794</authentication>
      </file>
    </fileContainer>
    <collection collectionId="14">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="521">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="522">
                  <text>Learning Venues</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11380">
                <text>Understanding Reactive Abuse: Signs and Solutions </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11381">
                <text>In this article, we explore the psychological dynamics of reactive abuse, the signs to look out for, the impact it can cause, and steps to get help. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11382">
                <text>&lt;a href="https://www.verywellmind.com/reactive-abuse-signs-impact-and-tips-to-break-the-cycle-7567483" title="Verywell Mind" target="_blank" rel="noreferrer noopener"&gt;https://www.verywellmind.com/reactive-abuse-signs-impact-and-tips-to-break-the-cycle-7567483&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
