text:
<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="
            http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">

    <bean id="hdp30ShimIdentifier" class="org.pentaho.hadoop.shim.api.internal.ShimIdentifier" scope="singleton">
        <argument value="hdp30"/>
        <argument value="Hortonworks"/>
        <argument value="3.0"/>
        <argument value="COMMUNITY"/>
    </bean>

    <service ref="hdp30ShimIdentifier" interface="org.pentaho.hadoop.shim.api.ShimIdentifierInterface"/>

    <bean id="hdp30Hadoop" class="org.pentaho.hadoop.shim.HadoopShim" scope="singleton"/>

    <service ref="hdp30Hadoop" interface="org.pentaho.hadoop.shim.spi.HadoopShim">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
        </service-properties>
    </service>

    <bean id="hadoopFileSystem" class="com.pentaho.big.data.bundles.impl.shim.hdfs.HadoopFileSystemFactoryImpl">
        <argument ref="hdp30Hadoop"/>
        <argument ref="hdp30ShimIdentifier"/>
    </bean>

    <service ref="hadoopFileSystem" interface="org.pentaho.hadoop.shim.api.hdfs.HadoopFileSystemFactory"/>

    <bean id="hdp30FormatShim" class="org.pentaho.hadoop.shim.common.CommonFormatShim"/>

    <service ref="hdp30FormatShim" auto-export="interfaces">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">format</value>
            </entry>
        </service-properties>
    </service>

    <bean id="hdp30FormatServiceFactory" class="org.pentaho.big.data.impl.shim.format.FormatServiceFactory">
        <argument ref="hdp30FormatShim"/>
    </bean>

    <service ref="hdp30FormatServiceFactory"
             interface="org.pentaho.hadoop.shim.api.cluster.NamedClusterServiceFactory">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">format</value>
            </entry>
        </service-properties>
    </service>

    <bean id="hdp30MapReduceServiceFactory" class="org.pentaho.big.data.impl.shim.mapreduce.MapReduceServiceFactoryImpl">
        <argument ref="hdp30Hadoop"/>
        <argument ref="executorService"/>
        <argument ref="transformationVisitorList"/>
    </bean>
    <reference id="executorService" interface="java.util.concurrent.ExecutorService"/>

    <service ref="hdp30MapReduceServiceFactory" interface="org.pentaho.hadoop.shim.api.cluster.NamedClusterServiceFactory">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">mapreduce</value>
            </entry>
        </service-properties>
    </service>

    <reference-list id="transformationVisitorList" interface="org.pentaho.big.data.impl.shim.mapreduce.TransformationVisitorService"
                    availability="optional"/>

    <!-- Hadoop client services definition -->
    <bean id="hdp30HadoopServicesFactory" class="org.pentaho.big.data.impl.shim.HadoopClientServicesFactory">
        <argument ref="hdp30Hadoop"/>
        <argument ref="blueprintBundleContext"/>
    </bean>
    <service ref="hdp30HadoopServicesFactory" interface="org.pentaho.hadoop.shim.api.cluster.NamedClusterServiceFactory">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">shimservices</value>
            </entry>
        </service-properties>
    </service>
    <!-- End of Hadoop client services definition -->

    <!-- Hive service definition -->
    <bean id="hdp30HiveDriver" class="com.pentaho.big.data.bundles.impl.shim.hive.HiveDriver">
        <argument ref="jdbcUrlParser"/>
        <argument value="org.apache.hive.jdbc.HiveDriver"/>
        <argument value="hdp30"/>
    </bean>

    <service ref="hdp30HiveDriver" interface="java.sql.Driver">
        <service-properties>
            <entry key="dataSourceType" value="bigdata"/>
        </service-properties>
    </service>

    <bean id="hdp30ImpalaDriver" class="com.pentaho.big.data.bundles.impl.shim.hive.ImpalaDriver">
        <argument ref="jdbcUrlParser"/>
        <argument value="org.apache.hive.jdbc.HiveDriver"/>
        <argument value="hdp30"/>
    </bean>

    <bean id="hdp30ImpalaSimbaDriver" class="com.pentaho.big.data.bundles.impl.shim.hive.ImpalaSimbaDriver">
        <argument ref="jdbcUrlParser"/>
        <argument value="org.apache.hive.jdbc.HiveDriver"/>
        <argument value="hdp30"/>
    </bean>

    <bean id="hdp30SparkSimbaDriver" class="com.pentaho.big.data.bundles.impl.shim.hive.SparkSimbaDriver">
        <argument ref="jdbcUrlParser"/>
        <argument value="org.apache.hive.jdbc.HiveDriver"/>
        <argument value="hdp30"/>
    </bean>

    <service ref="hdp30ImpalaDriver" interface="java.sql.Driver">
        <service-properties>
            <entry key="dataSourceType" value="bigdata"/>
        </service-properties>
    </service>

    <service ref="hdp30ImpalaSimbaDriver" interface="java.sql.Driver">
        <service-properties>
            <entry key="dataSourceType" value="bigdata"/>
        </service-properties>
    </service>

    <service ref="hdp30SparkSimbaDriver" interface="java.sql.Driver">
        <service-properties>
            <entry key="dataSourceType" value="bigdata"/>
        </service-properties>
    </service>

    <reference id="jdbcUrlParser" interface="org.pentaho.hadoop.shim.api.jdbc.JdbcUrlParser"/>

    <!-- End of Hive service definition -->

    <!-- Hbase service definition -->
    <bean id="hbaseShim" class="org.pentaho.hbase.shim.common.HBaseShimImpl"/>
    <service ref="hbaseShim" auto-export="interfaces">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">hbase</value>
            </entry>
        </service-properties>
    </service>

    <bean id="hdp30HBaseServiceFactory" class="com.pentaho.big.data.bundles.impl.shim.hbase.HBaseServiceFactory">
        <argument ref="hbaseShim"/>
    </bean>

    <service ref="hdp30HBaseServiceFactory" interface="org.pentaho.hadoop.shim.api.cluster.NamedClusterServiceFactory">
        <service-properties>
            <entry key="shim">
                <value type="java.lang.String">hdp30</value>
            </entry>
            <entry key="service">
                <value type="java.lang.String">hbase</value>
            </entry>
        </service-properties>
    </service>
    <!-- End of Hbase service definition -->

</blueprint>

redpajama_set_name: RedPajamaGithub


text:
Q: Call Swift ViewController from Obj C didSelectionRow I have an Obj C project that I have added a Swift viewController to.
I'm trying to attach a storyboard to the viewController.
I can programmatically add things to the view but I can not get the storyboard to show up.
I have also tried to use a xib as a vie for the Swift viewController with no luck.
Calling the Swift vie form Obj C from a didSelectRowAtInexPath:
SwiftController *sc = [[SwiftController alloc] init];
[self.navigationController pushViewController:sc animated:YES];

SwiftController.swift:
import Foundation
import UIKit

@objc class SwiftController: UIViewController {

override func viewDidLoad() {
    super.viewDidLoad()

        // This prints
        println("in the scrolling view")
        // This works
        self.view.backgroundColor = .redColor();
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        // Dispose of any resources that can be recreated.
    }
}

Storyboard is hooked up correctly:

And this is what I get every time:

Same results happen with a xib.
There are a lot of things in the Apple Docs and on the web and here on SO that deal with many issues "around" this one but I have not found anything that helps me see what I'm doing wrong here.  Doing things the way that works or Obj C does not seem to work.
Clearly I'm a noob with Swift.  Any help would be great.  Thanks.

A: There are two basic approaches when using storyboards:

*

*When you have Objective-C code that needs to transition to another scene in the storyboard, you can:

*

*give that destination scene a storyboard id (e.g. SwiftControllerScene) in Interface Builder;

*use the storyboard instantiateViewControllerWithIdentifier to instantiate that destination view controller; and

*transition to that new scene (i.e. push or present that view controller).
Thus:
SwiftController *sc = [self.storyboard instantiateViewControllerWithIdentifier:@"SwiftControllerScene"];
[self.navigationController pushViewController:sc animated:YES];

*Alternatively, when using storyboards, rather than manually instantiating the destination's view controller and then calling pushViewController, I'd prefer to set up a segue in the storyboard between the view controllers (see https://stackoverflow.com/a/27650207/1271826). I'd then programmatically perform the segue (referencing, of course, whatever storyboard identifier you gave the segue):
[self performSegueWithIdentifier:@"SegueToSwiftScene" sender:self];

This way, the storyboard continues to represent the visual flow of the app.
Note, the fact that the destination scene's view controller is written in Swift vs Objective-C is largely immaterial. The question is merely what language the source view controller uses (hence the above examples are in Objective-C) and the process is otherwise largely the same regardless of the language of the destination view controller.

A: Because in this case, you're initializing a new SwiftController instead of using the one from the storyboard. You will want to either perform a segue to the new storyboard vc or get the vc from
self.storyboard.instantiateViewControllerWithIdentifier(_controller id_)

A: in case you use a xib for your swift viewController you must init it like this:
SwiftController* controller = [[SwiftController alloc]  initWithNibName:@"SwiftController" bundle:nil]

Where SwiftController is also the name of your xib.
I notice this issue in iOS 8, but it works normally in iOS 9 and iOS 10 when you init the controller simply like this:
SwiftController* controller = [[SwiftController alloc]  init];

redpajama_set_name: RedPajamaStackExchange


text:
LEADING FASHION DESIGNER BRINGS HIS PASSION FOR FASHION TO NORTHERN ARTS SCHOOL
The Northern November 14, 2016
An award-winning fashion designer who has earned the praise of Karl Lagerfeld, Louis Vuitton and US Vogue, brought his expertise and passion for fashion to a specialist art and design college to inspire the next generation of fashion designers.
Nabil El Nayal is the designer behind the ready-to-wear brand Nabil Nayal and recently visited Cleveland College of Art and Design (CCAD), where he spoke with students from the BA (Hons) Textile and Surface Design degree programme on his career progression.
Spending his early years in Syria, where his family's textile business inspired his interest in fashion from a young age, Nabil moved to England at the age of 14 and went on to study fine arts and textiles. After graduating with a degree in fashion and spending time with Burberry designer Christopher Bailey, he won the prestigious Royal Society of Arts Award, the Graduate Fashion Week 'Best Womenswear' Award and the British Fashion Council MA Scholarship Award, which enabled him to pursue a masters at the Royal College of Art.
From Nabil's SS16 Collection
During his presentation at CCAD, Nabil talked about creating his capsule collection for River Island, which sold out within three days, and producing commissions for Crown Paints as part of a national competition. With a thirst for originality and inventiveness, Nabil took innovation to a new level when he became the first designer to use 3D printing on the catwalk. His collection was bought by exclusive department store, Harrods, and Nabil now sits on the 'Harrods Launches' panel, a platform for showcasing new and exceptional design talent.
Nabil expanded on his successful debut at London Fashion Week in 2011, where he honed his craft, and for which he was shortlisted for the iconic LMVH Prize. His collection grabbed the attention of Karl Lagerfeld, who 'loved it!', invited Nabil to show at last year's Paris Fashion Show and bought a shirt which was worn by Jerry Hall.
During a question and answer session, Nabil was able to impart a wealth of advice to the students on the benefits of gaining work experience, challenging conventions and breaking the 'fashion rules' by looking at new experiences and not settling for the easy option. Currently undertaking further study with a PhD, he also inspired the students to 'tell a story' with their fashion ideas, to take chances, enter competitions and submerse themselves in every opportunity.
Lianne and Nabil look through a number of student portfolios
He also stressed the importance of collaboration, highlighting the excellent investment in the arts and creative industry in the UK, and the amazing talents the country produces. Complimenting CCAD on its fantastic facilities, which he compared favourably with the Royal College of Art, he said: "The students are using the facilities at CCAD as tools that permits them to translate their creative visions into exciting, challenging and often thought-provoking outcomes. There is a uniquely 'northern' energy that I was drawn to; anything seemed to be possible. It was wonderful to observe the passion of the team and the enthusiasm of the students."
Student Sarah Walker talks through her artwork with Lianne and Nabil
19-year-old Sarah Walker from Darlington is a second year student on the BA (Hons) Textile and Surface Design degree. She said: "I found it motivating to hear Nabil talk about his journey, from establishing himself as a student to a well-known name in the fashion industry. My current project is about being experimental, incorporating digital aspects into design work, so his feedback really hit home.
"When Nabil visited my workspace to look over my designs and portfolio, he advised me on possibly constructing 3D drawings to make my work more innovative and exploring the potential of the digital facilities we have access to at CCAD. Here we have the freedom and encouragement to be experimental and inventive on the course, so I am looking to now blend print and embroidery together in my designs."
Lianne Hubbert, lecturer on the BA (Hons) Texture and Surface Design degree at CCAD, said: "The textiles students were really lucky to work with Nabil on their current project he is a true visionary and offered excellent feedback for their design work as well as future career advice. We are hoping that he can come back to give a final critique to all the textiles students who are breaking new boundaries in their design work, we are all very excited about what the future has to offer our undergraduates. Watch this space!"
fashionGENERALIndustrynorth east englandTEXTILES
NEW CAMPUS FOR NORTHERN ART COLLEGE IS TAKING SHAPE
ALUMNIart historycreative careersMiddlesbroughnorth east england
ALUMNIartistembroideryexhibitionTEXTILES
Textiles graduate turns hobby into thriving quilting business
ALUMNIHartlepoolnorth east englandTEXTILES
Darlington Alumni & Director James Campbell shoots short film 1986
ALUMNIdarlingtonfilmnorth east england

redpajama_set_name: RedPajamaCommonCrawl


Weekend 1 of Coachella was a success! With that being said, let's bring on the PARTIES! Amongst the many celebrities that danced the nights away in Indio, California, Olivia Culpo was seen walking into the Lucky Brand Party on April 13th wearing a chic tight pink dress finished with Hidden Crown Hair!
Shop your favorite celeb looks by visiting our website at www.hiddencrownhair.com!
Pop Star, Ally Brooke, slayed in satin! She was given a longer soft ombre using Hidden Crown Hair Extensions.
Kim Possible star, Ciara Riley Wilson, screamed chic from head to toe. She completed her look with a sleek behind the ear look thanks to Hidden Crown.
Savannah May from Knight Squad is GOALS! She rocked this look topped with a perfect Hidden Crown Hair pony!
Bravolebrity hairstylist, Julius Michael is known for making our beloved Housewives camera ready. So we ask you... Want to know one of his secret weapon?? Hidden Crown Hair Extensions! Michael recently sat down with Bravo's "The Look Book" and gave everyone his tips on how to recreate some of your favorite celeb looks.
"I cut Ramona's hair every four to six weeks, but every once in awhile I like to add some hair back! Hidden Crown clip-in extensions gave just the right amount of fullness I was looking for and made her hair go from flat to fabulous in seconds," said Michael.
Check out more from Julius Michael using Hidden Crown Hair below!
Amongst the celebs that graced the celebration, the Hilton's came... and they SLAYED.
Hair styled by Pamela Brogradi using Hidden Crown Hair Extensions. GORGEOUS!
Luxury leather goods brand MCM opened its global flagship boutique on Rodeo Drive, to an A-list crowd of stars and VIPS for a special Red Carpet event. Supporters of the brand all came out to get a first look at the beautiful new boutique which was decked out with fun merchandise, interactive elements and signature photo backdrops for the occasion.
Paris Hilton and Gigi Gorgeous attend the grand opening of the MCM Global Flagship Location in Beverly Hills.
American television personality, La La Anthony screamed "QUEEN" at Ciara's InStyle Magazine cover party. She gave off a chic spring feel wearing this floral jumpsuit and perfect pony. Celebrity Hairstylist, Netty Jordan, gave Anthony a snatched look by using Hidden Crown Hair for extra length and fullness. Sending love and congrats to Ciara on her first InStyle Magazine cover!
Which celeb will you see wearing Hidden Crown Hair NEXT?!


text:
"My Baby Left Me" is a rhythm and blues song written by blues singer Arthur Crudup.

Original recording
It was first recorded by Crudup in Chicago on November 8, 1950, with Ransom Knowling on bass and Judge Riley on drums, and was released as a single on RCA Victor 22–0109.

Later versions
It gained further exposure in covers by Elvis Presley, who placed his version on the B-side to his 1956 single "I Want You, I Need You, I Love You"; by Wanda Jackson who often shared the same bill as Presley; by Creedence Clearwater Revival, who recorded it as a track on their 1970 album, Cosmo's Factory; by Buffy Sainte-Marie on her 1972 album Moonshot; and by John Lennon (incorrectly titled "Since My Baby Left Me"), recorded during the Rock 'n' Roll sessions in 1973, but first released posthumously on Menlove Ave. in 1986. It was included as a bonus track (still incorrectly titled) on the 2004 CD version of Rock 'n' Roll. It was also a No. 37 UK Singles Chart hit in 1964 for Dave Berry and the Cruisers. Elton John used a snippet of "My Baby Left Me" as part of a medley (along with a snippet of the Beatles' "Get Back") during his concert performance of "Burn Down the Mission" on his 17-11-70 live album.  Loggins and Messina also covered this song on their 1975 album, So Fine.

Slade version

"My Baby Left Me" was covered by the British rock band Slade in 1977 and released as a non-album single as a tribute to Elvis Presley, who died in August of that year. The Slade version merged "My Baby Left Me" with "That's All Right", another Crudup-penned track. "My Baby Left Me But That's Alright Mama" reached No. 32 in the UK and remained in the charts for four weeks.

Background
Returning to the UK from the United States in August 1976, Slade found themselves out-of-favour at the time of the UK's Punk rock explosion. The band's 1977 album Whatever Happened to Slade proved a commercial failure while their tour that spring had shown that they could no longer fill large venues. Although their April 1977 single "Burning in the Heat of Love" also failed to chart, the band returned to the Top 40 with "My Baby Left Me". Released in November 1977, it reached No. 32 and would be the band's last Top 40 single until 1981's "We'll Bring the House Down".

"My Baby Left Me" was recorded in August at Advision Studios in London. The band decided to record the song as a tribute to Elvis Presley following his death earlier that month. As guitarist Dave Hill was busy doing interviews in northern England, bassist Jim Lea played guitar on the recording. "My Baby Left Me" was released on 7" vinyl by Barn Records in the UK, Ireland, Belgium, France and Germany. The B-side, "O.H.M.S.", was exclusive to the single and would later appear on the band's 2007 compilation B-Sides.

A music video was filmed to promote the single, featuring the band performing on a stage. In the UK, the band performed the song on the music show Top of the Pops. In Germany, it was performed on the TV shows Disco and Rund.

Critical reception
Upon release, Record Mirror described the song as "real pleasant", but added: "I can remember a time when Slade records were vixen fearsome rather than pleasant". Sounds rated the single as the "Best Comeback Single", describing it as a "fabulous treatment" of the "bouncy, struttin' 12-bar blues number".

Track listing
7" Single
"My Baby Left Me/That's Alright Mama" - 2:23
"O.H.M.S." - 2:41

Personnel
Slade
Noddy Holder – lead vocals, guitar
Jim Lea – guitar, bass, backing vocals
Don Powell – drums

Additional personnel
Chas Chandler – producer
Gered Mankowitz – sleeve photography
Jo Mirowski – sleeve design

Charts

References

1950 songs
Elvis Presley songs
Blues songs
Creedence Clearwater Revival songs
1977 singles
Slade songs
Song recordings produced by Chas Chandler

redpajama_set_name: RedPajamaWikipedia


An experienced team picked from the East Anglian food production industry is giving a new lease of life to a struggling factory which was saved from liquidation.
The four strong senior team at the former Frank Dale Foods facility has laid out plans to turn around the party food and canapes producer by running it "as a frozen foods business should be run" - and has brought the loss-making firm, now rebranded Finedale Foods, back to profitability in just six months.
Managing director Ed Miles, who put forward a bid to buy the assets of the producer in Bunwell near Attleborough, has been joined by commercial manager Helen Lynn, formerly of Premier Foods, Bernard Matthew and the Tulip Group, factory manager Graham Buckley, also of Bernard Matthew and Linda McCartney products producer Hain Daniels and technical manager Robert Smith, formerly of Kettle Foods.
The board of Frank Dale Foods called in liquidators in February after losing more than £500,000 in the previous financial year. Mr Miles was involved with the company before its liquidation, looking at rescue models. "But the losses announced at the end of January were too great to be able to save the previous business, so I put together a plan of how we could turn it into a new company," he said. "Purchasing the assets of a liquidated business and injecting them into a new business is not for the faint-hearted. It was the strength of the Frank Dale brand and the staff they had here which gave me the confidence to believe the business was worth saving." He added: "I knew the business needed to be completely unpicked and sympathetically put back together."
Mr Miles secured funding from co-investment fund New Anglia Capital for the purchase which was was supported by South North Council. In the first six months under its new management revenue has reached 90% of the previous board's forecast and the team hopes to secure as much of the forecast £4m full-year turnover as possible.
However, around £1.15m is still owed to more than 100 creditors. Andrew McTear of McTear Williams & Wood which managed the liquidation said payment of 20p in the pound was expected by Christmas. He added: "This is a great example of the insolvency process being used to rescue a business to provide a fresh start and future return for creditors."


On behalf of Gregory W. Stevens, Attorney at Law posted in blog on Tuesday, April 17, 2018.
Most married couples do not split amicably but have negative feelings such as hostility and resentment toward each other. Often, the cause of the divorce, such as infidelity or addiction, is what makes this life event so emotionally intense and contentious. The things that happened may cause you not only to want to avoid your ex but also want your kids to avoid being with him or her.


I'm a bit behind on posting all the things I want to post. Sadly, the LJ website has not been cooperating, and I'm not a huge fan of the MFC client.
We expected a larger than usual crowd for dinner that night, since Paul and Mary would bring the group up to nine people. Lori had lots of schoolwork to do, so we wanted to keep the dinner easy on us.
We wanted to serve Pumpkin Bread Pudding with Gingered Cream for dessert, and we didn't want to fuss with having to maintain the time separation for Monica. So we decided to go with something hearty and vegetarian. We settled on Hearty Multi-bean Chili from one of the Pillsbury Cookbooks, because it made plenty.
We had intended to serve Chili-Cheese Corn Muffins, but we couldn't find the muffin pan and we ran low on time. Dani very kindly went ou to the store to get us some Pillsbury biscuits instead.
After dinner, we cleaned off the table, put down newspaper, and carved jack-o-lanterns. We had bought nine pumpkins, enough for every one to carve their own.
Mostly we used steak knives and such; I did manage to find the pumpkin-carving tools we had bought years ago. They ended up working very well, but being a little easy to break. I had very good results with a plastic tool that was like an awl with wide chisel-like sides.
My first pumpkin was tall, narrow, and motled green and yellow, with a couple of diagonal creases. I turned those creases into an eye crease and a lopsided mouth, and added bolt-holes at the temples and a forehead scar to make a looming Frankenstein pumpkin. I was really proud; it might well be the best jack-o-lantern I've ever done.
We had two extra pumpkins since Deanna and Dani had chosen not to carve their own. My second pumpkin was so inclined to tip over that I wasn't it would stand on end. I put it on its side and carved eyes and a mouth, using the stem as a nose, after the model of the Play With Your Food book.
Other people carved great pumpkins too. I particularly remember Eli's random Cthulhoid thing, which did end up looking very spooky. I also remember the white pumpin that Paul turned into an enormous white eyeball.


text:
Regulatory Malfunctions in the Drug Patent Ecosystem
Ana Santos Rutschman
Patent protection for several of the world's best-selling and most promising drugs—biologics—has begun waning. Over the next few years, many other drugs in this category will lose critical patent protection. In principle, this should open the United States market to competition, as more manufacturers are now able to produce relatively cheaper versions of these expensive drugs, known as biosimilars. That, however, has not been the case. This Article examines this problem in the context of the articulation between anticompetitive behaviors and regulatory interventions in the biopharmaceutical arena and argues for a novel solution: a timelier response provided by the U.S. Food and Drug Administration (FDA) in the form of license revocation when follow-on innovators fail to compete. In one significant case, the FDA approved several biosimilar versions from different manufacturers that would in principle compete with the biologic drug Humira—the largest-grossing drug in the United States and worldwide—but the manufacturer of Humira entered into multiple agreements with biosimilar manufacturers to keep the drug out of the U.S. market until 2023, while making it available elsewhere from 2018 onward. An abundant stream of scholarship has examined the relationship between pharmaceutical markets and antitrust mechanisms to curb anticompetitive behaviors. This Article moves the debate in a new direction. Because antitrust responses generally face a time lag, this Article posits that an additional regulatory intervention is needed outside antitrust law, and it argues that the FDA is institutionally well-placed to provide a first-line checkpoint for anticompetitive agreements that result in non-commercialization of approved drugs. While novel, this proposal incorporates a solution that has been hiding in plain sight: the FDA regulatory framework allows the Agency to revoke licenses under certain circumstances, including some forms of inaction on the part of the licensee. This Article shows that the FDA not only has the authority, but also the statutory obligation, to revoke the licenses of biosimilar manufacturers who deliberately fail to bring their products to market within a reasonable period of time. Many of the biologics slated to lose patent protection in the first half of the 2020s are routinely used in the treatment of some of the most challenging medical conditions, including certain cancers and auto-immune diseases. At a time when concerns over drug prices are at the forefront of political and social debates, finding ways to instill competition into post-patent markets remains a crucial task. The solution put forth in this Article furthers the interests of different parties, as it clears the pathway for motivated biosimilar manufacturers to bring their products to a profitable market while bringing down overall costs for health systems and, in particular, for patients in need of extremely expensive pharmaceuticals.
Ana S. Rutschman, Regulatory Malfunctions in the Drug Patent Ecosystem, 70 Emory L. J. 347 (2020).


text:
"Going Cold Turkey without the Turkey: Karen and George Heitman watched Forks Over Knives and knew immediately what they wanted to do." by J. Lanning Smith
"Freedom from IBS & Obesity after 44 Years: The China Study and TrueNorth led me to amazing health and freedom from debilitating IBS." by Joan Ransier
"'We Cannot Not Do This!' After hearing a lecture by Dr. Esselstyn, Leslie Haas and Richard Crofton-Sleigh knew they had to make a change." By J. Lanning Smith
Mary Lou and Wes Beavers (By J. Lanning Smith) "Forks Over Knives Got the Ball Rolling to Better Health: Mary Lou and Wes Beavers belong to the Eat Smart, Live Longer Club, with over 600 members!"
Judy Cote (Summer 2018) "The East Smart Live Longer Club Saved Her Health: Battling extra weight, high BP and thyroid issues, Judy Cote's health answers were found in Hilton Head, South Carolina." (by J. Lanning Smith)
Ellie Dixon (Spring 2018) "My Journey into the Whole-food, Plant-based World: How my husband and I found healthy eating, weight loss, and improved health."
Shayda Soleymani (Winter 2018) "Climbing Up from Rock Bottom: I was 240 pounds, prediabetic, and on medication for high cholesterol, high triglycerides and diabetes"
Dillon Holmes (Fall 2017) "Why Is Finding Health So Hard? How I discovered true health and now support others."
J. Lanning Smith (Summer 2017) "It's Never Too Late: How I turned around my long list of health issues starting at age 67."
Jason and Sarah Ramos (Spring 2017) "Going It Together: NHA couple lost half their combined weight on a plant-based diet."
Wanda Huberman (Fall 2016) "Taking Control of My Life and Health: I knew the elements of truly good health but needed help putting them into action."
Sarita Bhola (Summer 2016) "Finding Good Health after Losing 85 Pounds: How I went from 21 different health diagnoses to feeling vibrant and alive!"
Christina Gore (Spring 2016): "Resolving a Sixteen-year Headache: After Exhausting all Possible Medical and Drug Therapies, Water Fasting was Key."
Steve Bernstein (Fall 2015): "The Unhealthy Vegan: How I Discovered that There's More to Health than Being Vegan."
Ivonne Vielman (Spring 2015): "Changing the Course of Cancer: How I Reversed Stage III Lymphoma through a 21-Day Water Fast."
Jamie Ottesen (Winter 2015): "Healing Food Addiction and Bulimia: How I Found My Way Back to Health after 38 Years of Hiding My Secret."
Susan and Ralph Staffier (Fall 2014): "Prognosis Denied: A Medicated Life was Not Acceptable to This Husband and Wife Team."
Bill and Marilyn Kellar (Fall 2014): "Keeping the Faith: Bill and Marilyn Have Practiced Natural Hygiene for over 50 Years."
Dan and Trudy Regan (Spring/Summer 2014): "Discovering the Missing Link to a Sucessful Natural Hygiene Life after 50 Years of Research."
Janet Carter (Spring/Summer 2014): "Health Comes from Healthful Living."


To get more community feedback I've made public my fellowship idea - submitted earlier with my fellowship application.
Editor loss, the gender gap, article quality improvement and low editor engagement are not isolated problems. They are form an interrelated hierarchy and share three main underlying causes.
Defective media architecture — the most precious resource in a wiki is human labour. Yet the MediaWiki software is highly deficent when it come to minimising to the bulk of both social & editorial tasks of building and maintaining Wikipedia. This creates both a steep learning curve and labour crunch and introduces social and technological barriers to new participation. [note 2]. Partial solutions based on user scripts, gadgets, robot and third party software only handle one facet of the problem and ulimately increase the devide between the core contributors and the new comers - a source for Xenophobia.
The chief contributing defect of MediaWiki is unplanned social scaling . The piecemeal development of governing of editorial policy "has led only to the use of violence in place of reason, and if not to its own abandonment, at any rate to that of its original blueprint" . The violence is deletion of good faith work by domain experts and novice editors. Research shows that over half of articles deleted daily using a unilateral CSD article A7 "no indication of importance" are good faith work where as bad faith work such as spam, patent nonsense and vandalism together only account for less than 20% percent of articles deleted by the CSD.  Both Social and personal anarchy, anachronistic vestiges from the early days of the web which have consistently brought about the destruction of societies which have embraced them as values.  With the rise of social networks and blogging these values have undergone a reversal — as identity has played a central role in promoting transparency in the social age of the web and for the first time curing Gender Gap in virtual societies.
Of the three factors MediaWiki software is the easiest to change in particularly using a small stand alone robot. Editrial Policy, the rules by which wikis are governed are the next most easily changed though it does require a wider much larger group of individuals. Social change is harder to produce as it involves large masses of people who are largely unaware of the issues at hand. Piecemeal change in policy is often reactionary, populist and counterproductive. However even at the social level change can be observed though it thousands of not millions of people who are the real stakeholder providing the bulk of funding, content and influence for WMF projects.
When problems are well posed their solution is much easier to find?
How can the loss of active editor, due to conflict over editorial concerns, be reversed?
How can women be encouraged to play a greater role in Wikipedia?
How can wiki increase user's engagement when greater involvement requires less editing and more drudgery?
How can articles quality be improved with limited access to domain experts?
Modify the media/editorial policy to cater for more editors.
Try to keep each editor for longer.
Since there are virtual communities where women participate more than men - they should be emulated.
Reduce non-editorial tasks using technological solutions and produce new ways to engage all level of users.
Provide a mechanism to allow a domain experts contribution to get have greater weight.
The tragedy here is that the most important requirement for a wiki's ongoing success — a large and diverse community is sacrificed in the name of quality. Luckily it is possible to untangle these crosscutting concerns and get the best of both worlds - quality content and new editors. To go ahead would inflict costs , risks and some impediments to the community but these would be offset by down the road the greater benefit. A wiki requires editors for many labour intensive tasks and so this rejection is not without a moral hazard.
However the editors dilemma is a strategic problem occurring over a long-term - to address it the tactical version must be resolved, this is the reviewers dilemma.
As the information asymmetry increases the bias towards option one increases — reverting is a confirmation bias. Instead of making a potentialy erronius decision by reverting they restore a status quo. To support such a choice any editorial defect is cited . Though in a xenophobic situations standards for rejection are very low and arbitrary - "grammatical errors" or "too many red links". The domain expert will only see the default in response to his co-operation. If it happens a few more times he will learn that his work is not welcome, and tell his friends . The simple statement of this dilemma is at every edits machine and human reviewers must choose or reject domain based edits (and resolve human conflict) based only on their expertise of editorial policy . In almost all cases of good faith work — rejection of edits will occur due to editorial concerns and not due to domain problems. Wikipedia's growing popularity means its errors will often be repeated in print, and on-line.
are the worst conditions for cooperation to evolve[note 7]. This theoretical warning is directly mirrored by conditions in the field - the requirements that editors work in the isolation on new articles in their private spaces.
Reputation & Face - built overtime and lost though conflict.
Correcting payoffs so that even individuals pursuing their own selfish interests will prefer to cooperate. The way to change incentive is to either to provide greater rewards or to reduce the cost of for prefered behaviour. Negative reinforcement of bad behaviour is also possible. We can reduce the communication and coordination cost using technological solutions. See their benefits exceeds their costs in time, and work, coordination, and communication. So that good faith work remains a rational choice while still being able to address bad faith work effectively. The focus shifts to of cost of coordination, copy editing is put on the reviewer (for whom it is easy) and the cost of communication is shared.
making results more visible (information contributed * usage as opposed to edit count).
Reducing coordination costs - the costs of arranging different people to do sub tasks in a complex goal. Good editing work can be done by a domain expert cooperating with an experienced editors. Yet long before a good editor will come along the newcomer will have to deal with CSD Afd and other notices. Simone can act as a matchmaker by engaging good editors in subjects they deeply care about, and by sending domain experts to articles where they are most needed and can best contribute.
Reducing communication costs - the cost for SD and other a social actions has been reduced to help patrollers but the more complex task of communication remains a costly task. By making good communication almost trivially to launch an improvement protocol for an article.
Reducing the asymmetry between experienced and inexperienced users. For example every day most new user's article's are deleted yet at Afd discussions where deletion can be contested, new comers are practically absent..
Wikipedia has a problem to provide users with credit to editors. By tracking contributions it would be possible to determine and acknowledge a user's higher level contribution. So while we could make a leader board for biters and serial biters and provide them with sad kittens - we should also track good collaborators great communicators as well as coaching assistants and provide them with rewards and acknowledgments. For instance providing an executive coaching opportunity.
3-5 inline tags must be introduced into the article by the reviewer.
Notice allowing editors a week to respond by indicate willingness to correct the problems.
Notice requesting the editor demonstrate his domain expertise by taking a quiz. (could be fun within the scope of user engagement).
The editor may request a peer review for a second opinion.
If the edit is not illegal the un reverted a copy or link to the edit will be given to the editor in his user space.
Reviewers who do not comply will lose his privileges for 2 weeks. (cooling off).
Increasing visibility - article deletion effectively hides the users edits while reversion hides the editorial problems. Both these allow a moral hazard of reducing potential penalties to the reviewer.
Reducing anonymity - reputations cannot develop in a truly fully anonymous environment.
Simone will assign users under coaching a unique avatar and advise how to link it to their signature.
Simone will allow users to use a Facebook id to identify.
Using a social network identity would be even better to avoid deception.
Repeated encounters between the same individuals are important to evolve from a reviewer's dilemma to a bargaining game.
an increase in circles of social and intellectual relatedness will improve capabilities of co-operation within each group.
No more speedy deletion of for good faith work - speedy is unsuitable for good faith work. It send a bad messages to editors and reviewers.
Restrict reviewing of non spam to categories which they have edited. This will coordinate reviewers and editors better and keep interaction within circles of greater relatedness.
Invade the community with a new breed of editor who can dominate though co-operation.
Some of these ideas would create a gap which is where Simone's comes into the picture. It will be possible for a reviewer to request it to intercede in such situations.
Provide an example of software agent whose goal is positive social engineering rather than negative editorial automation.
Not just increase the number and life span of editors but increase the domain expertise will reduce the high cost or reviewing edit.
Reduce the need for subjective editorial decisions - which are usually handled badly by human expert.
Create a minimal learning curve for acquiring editorial, social, technical and administrative skill.
I propose to provide positive alternatives to for instance templates for section and article under construction work easier use of problem tags, wider usage of incubation and requested article features. As these come to effect there would be far less need for a police state mentality and a return to the early meritocracy. I envision this happening socially in more and more places over time using technological means. This would make participating less stressful and more productive.
Certain of the early instigators of the more esoteric policies on Wikipedia have voiced regret once the protocols they innovated got wider and wider usage[note 11]. Other policies[note 12] solve localized problems by imposing unnecessary criteria on the whole community.
Wikipedians have been described as xenophobic in their attitude to new comers. Not surprisingly the Wikipedia jargon for this behavior is biting the newcomers. The roots of this asocial dynamic can be understood using simplified models like the reviewer's dilemma. This law of the jungle behaviour with its mad logic, brutish cunning and has evolved in countless encounters has. But this begs the question - could a new 'species' of Wikipedian invade and dominate the population? Considering that such invasion have been described by Sue Gardner in her address at Wikimania 2011.
To answer this question eloquently it is best to use a powerful social metaphor for the wiki and it is the beehive. Within the lens of beehive it becomes preeminently clear that a change of the asocial paradigm to the eusocial one is required. In the real world it means increasing userrelatedness and changing the form of conflict.
Like a real hive, a wiki requires constant policing to ensure that drones are not pursuing their own agenda at the cost of precious shared resources. In the hive these freeloaders once identified are restrained or destroyed and their progeny eaten. In the wiki sock puppets are unmasked using a check user and are then banned and their works systematically purged. The hive must deal with parasites (COI) and invaders (Paid Editors), and a degree of anarchy (ArbCom). Each generation is very closely related and the oldest, most senior maintains the status quo.
So one may argue that this is the natural order of things. New editors should be viewed with great suspicion -- Are they foreign agents? (Paid Editors) trying to subvert, or perhaps self-serving parasites? (COI). The default solution is one of extreme hazing - the old generations retaliate against individuals who might be suspected of hurting the group, until they learn to walk the line or depart. And the few who graduate will maintain the asocial dynamic. This is a form of total war — it is extremely expensive to wage and is uncommon in nature.
However such solutions are unnecessary and no longer acceptable — it is time to groom another breed of Wikipedians who default to settling differences sporting within a "limited war" paradigm rather than the picric outcome of todays "total war".
In the early dates of Wikipedia it was a simple technology, it lacked experienced editors or an editorial policy. It had no established hierarchies of influence or personal stakes. All these things are signs of progress, yet they present impediments to contribution. Consequently the threshold cost of contribution was low[note 14]. However as the project matured it was modified piecemeal to address immediate concerns - without a guiding hand the changes have often been regretted in retrospect.
Marshal McLuhan in his seminal work understanding media and later text innovated the tetrad as a tool for analyzing the impact of new media. By providing a tetradic analysis for Simone, it is possible to forcast the scope of her impact.
Enhances - review of good faith edits for: article quality, editorial standards; user recruitment, and coaching; group collaboration under peer review.
Reverses - editorial complexity, community reduction, coordination cost, recruitment of new editors, policy complexity.
Retrieves - organic editing , pay it forward editing[note 8] shorter learning curve. reduced cost of contribution.
Makes Obsolete - early selection of new articles; subjective human assessment of editorial level for articles.
Next Simone will be compared with some other media being utilised and developed today.
It is aimed at altering user's editing behaviour and not to fix or revert their edits.
It is planned to preempt future problems rather than react to old ones.
It is planned to rival human assessment of editorial issues.
Abuse filter provides negative options to a few admins. Simone chooses from many positive choices for many editors.
It will provide many options in the cooperate category rather than provide one options in the default category.
Abuse filter is intended for abuse, but Simone is planned to cover a grey area of good faith work that borders on "abuse".
On the other hand MediaWiki developers are working to reduce the complexity of editing via the Visual Editor. While a visual editor will reduce the technical level of editing, but does not address any of the social issues discussed above. This solution may have an unintended result of increasing new user hazing. This could happen because new editors will be harder to assess on using technical signatures and will be judged more harshly on policy and style — which will appear to be more arbitrary.
No other loss of functionality present a greater stumbling block than loss of Organic Editing . Organic editing is the ability to create sentence by sentence a new article in main space. Organic also refers to natural growth of the articles. Yet today anyone bold enough to attempt to do this will be censured by patrollers and administrators at every save and informed that her work is not welcome. It will be nominated for speedy deletion on grounds of context, content or non notability. However notability is not an objective assessment, it is simply the harshest dictum to defend for a new editors. When the one editor complains they will be informed that their article may be exiled to the user space. It could apply for a visa when it reaches maturity. Unfortunately user space is not a place for natural collaboration. Your work gets no exposure and other new collaborators are often reverted there.
I reverted your good faith edit because it had many red links.
Whenever a page is edited it will be analysed and stored into the index it with a list of current issues. Searching the index will allow Simone a greater level of intelligence. Running strategic queries it will enable planned proactive action rather than a reactive interventions.
Simone's explainable activities would be driven by different causes. However strategies will assist develop full and order behaviour and where multiple options exist it will allow choosing the option which has the highest priority.
Simone objectively advises new users how they could best contribute. New users will, once again contributing with at a near zero cost - on the assumption of good faith work and that they would pay their dues once they have ascended up the learning curve. They would be more rapidly progress in skill and join rank as the next generation of our community - a generation that is less obsessed with unwritten rules, one which would not require wiki-lawyers.
Expand the program to bring articles systematically to featured levels by providing editors with expert advice.
As the Simone matures it could be directed [note 16] by users to instruct users of policy infringement and by project to direct their members to collaborate on hot spots.
To reach a far greater audience and higher levels of engagement a reward based game mode would be developed.
The project is made of software elements unified into a bot I will refer to as Simone. It will either work as an external user or will be integrated into the editor. Work will begin with sensor modules which can check a given revision's merit in various dimensions. These include a comparison with Gold Stadard and a Minimum standard.
technically these can range from simple rules to search wisdom of crowds ranking algorithms to more traditional statistical discriminative models.
Next it will select the highest priority issue from its queue.
The bot will summarize the top issue in a one line human readable report.
Next it will offer advice on how to rectify the problem.
Finally it will offer some alternatives and ask for feedback.
The following figures illustrate a sequence of advice notices that would be generated by Simone as it coaches Hildur, a new user from Iceland working on her first article on Kafka's story The Trial. The UI element shown is a talk page/user talk page based system that would be inserted by Simone.
proactive detection of an anonymous editor / new article by a registered user.
reactive intervention based on a biting incident sensor.
invocation from Afd - i.e. a new suspended delete sentence. Either correct the quality issue within a week or be deleted. Simone will be used to carry out and enforce the probation - if successful the probation will end by removing the probation notice. If no action is performed the article will be deleted/userified.
invocation by Huggle, Twinkle or a similar tool with Simone integration.
Current Status: The last submission has some editorial problems and since you are unregistered it is likely to deleted soon.
If you are planing to further improve this entry you can save your work by improving it. If you are interested in advice on how to improve it to the threshold level of inclusion choose one of the options bellow.
Your Mission — Sign up for coaching.
the options used - for doing optimization of advice using the R stats package.
the last option is a User Interface option for doing simple A/B testing R stats package to.
Points out that there is a problem with the edit.
Advises the use to join sign the user.
Can allow measurement of interest in anonymous editing.
Option 2 will place an organic editing template in the page with one day expiry. It will also place a notice on the talk page.
This user element would be further customised for capturing new users based on stylometric analysis of their input. To consider gender and nationality.
Most of the options are just hooks to get the user to sign up. For example I've done all that I can will inform her that she can do much more - Wikipedia has mistakes she can correct and so on.
If in the submission loop the advice will expire immediately if ignored.
If it is just put into the IP user page - unregistered advice expires at is never clicked on would expire after 3 days and marked as a bounce.
Hildur, thanks for enrolling for wiki coaching.
Current Status: Your article is so short that it could be marked for speedy deletion under article A1 - which means that it does not provide enough context to justify its inclusion in.
Your article: on The Trial has been temporarily protected from speedy deletion. It is a good start – but 50 words is considered too short for a Wikipedia article. Once you add at least another 100 words, it would qualify this article as a stub article.
There are many ways to improve context.
Simone will be basing it context score on minimally unique word n-grams. This will quickly indicate if the article if covering something new or not. Even if there are no unique terms it will also use word vector cosines to identify the closest articles.
You are making good progress, the edit brings the content score to 4/100. But you article is an orphan.
Current Status: speedy deletion A1 - your stub lacks context.
To fix this all you need to do is add some internal links. We call this processes wikifying.
Syntax should be taught from simple to the more complex.
If difficulties arise for engaging users with pedagogically significant advice or goals Simone could review a user's edit history to gauge the existing skill set.
Current Status: Your article has low notability and may be marked for speedy deletion under article A7 or A9 - which means that it does not indicate the importance of the subject to justify its inclusion.
Your Mission — demostrate the article importance for inclusion in an encyclopedia.
note: at this stage we would like to teach the user an editorial skill set as well as a social one.
However there are probably more than 5 options to fulfil this mission. If we are able to collect 20 options and track each options according to its success — Simone can optimise this advice. I.e. She will pick 5 options at random out of the 20, respecting each option's probability of success.
how to use her talk page.
how to use the user space sand box.
how to customise their user space for eusocial communication.
how to view requests for creation.
how to interact with reviewers using wiki love.
the new article creation wizard.
how to improve their user page.
it will be restricted to situations where machine judgment is better than human Judgment.
it will miss on some of the greatest benefits that Simone can provide - discounting coordination and communication costs.
it will mean that experienced users will not be familiar with the possibility of invoking Simone to place new articles and users under probation.
I will present a some strategies for executive coaching, article improvement. Since there exist a very low activity admin coaching projects this is also a candidate for intermediate level of editors. It can stress finer points of policy.
Loss of seasoned users is the flip side of new user recruitment. Experienced users may run out of information to contribute or they may end up being promoted into role that are less satisfying and experience burn out. Recent studies now provide deep knowledge of this problem. Studies show that under the right conditions these users can be retained longer within the community.
Simone is goal and mission based. She will, based on feedback provide them with tasks. These will involve work that requires human touch and is therefore harder for Simone to do.
Peer review in their area of editing.
Peer review in their area's of expertise.
Crowdsourcing of articles for importance and quality[note 17].
AFC in their areas of expertise.
Translation missions based on criteria in the next section.
Missions will be varied, including technical task and social tasks.
Current Status: Your many contribution have singled you out as an outstanding community member.
Why not take it to the next level? If you join the executive coaching you will be able to fulfill your potential and join the editor elite. I will give you some high impact missions.
executive coaching will complement the new user coaching program in places where Simone is unable to assist.
report cards in executive coaching will be used to give a the tasks a game-like feel.
Article quality improvement is the primary driver of Simone's behaviour. However if user have completed new user coaching they can either select another module or stay with the quality improvement module which will give feedback on editing progress.
Simone will still detect problems and direct users to fix them.
Outstanding inline tags in the users previously edited articles.
Current Status: It's time to do some work on improving article quality!
Quality improvement is not only one of this wiki's strategic goal - it is a part of how community members view your contribution. If you help bring an article to good or featured will count in your favour in many situations.
Your Mission — Select an article to improve and upgrade it from C to B level to receive a QI Badge.
Quality improvements will be able to select Users who can translate sections from another language where the other language has a better article.
report cards in Quality improvement will also be used to give a the tasks a game-like feel. This include offering badges and barnstars for successful missions.
Simone develops a one on one relationship with the student.
It defines a specific goal to work on.
It provides feedback on previous activity.
It engages the users by providing intervention feedback in the form of advice.
A/B optimized for greater usability.
Streamlined to make better use of space.
Adding quiz widgets to get a tighter feedback loops with even more engagement.
Adding a IM chat widget for interaction with human coaches.
supplemented with a gadget to place the UI in a coaching tab to make access to coaching easier and more personal.
Later a more dynamic floating UI may be developed above and to the side of the editor/browse window.
This would allow Simone to inspect edits in real-time as well as show videos to user's while they edit.
More so when it comes to web-based applications and even more so in the context of extending MediaWiki. MediaWiki is years behind normative content management systems, which provide simple UI widgets and an easy extension mechanism. The WMF claims to be open source, and constantly solicits help from volunteer developers. However in recent years the practice has become increasingly less open, there is little trust in community submissions and therefore little help from volunteer developers. Recent discussion on wiki-techL has highlighted that it can take over two years to review 3rd party plugins -- long enough for them to become obsolete.
I have made some paper UI design but the Template above represent a second iteration of these ideas. While they could be vastly improved and streamlined this should be done within the scope of the project itself. As mentioned above I would propose short development cycles with testing using real against real users and getting feed back from active coaches.
Using a Message based U.I. and no integration.
It would be expedient to integrate into Simone a capability for collection information using forms. This is part of a use case for collecting feedback in surveys. Another use case would be administering tests to verify a user's progress before a graduation event. If this is identified as important such a component will be integrated into the UI.
Simone will also have an refferal mode. It would be possible to introduce a referral template into the page by a reviewer to invoke Simone's presence and ask her to present certain advice to an individual at a page. The rational for this is to allow quick integration of Simone into tools like Huggle, Twinkle etc. This will in effect introduce positive alternative into these tools. This will have the effect of changing the standard tactics from total war to limited war in the good faith cases.
Simone's information architecture is designed to grow organically with the MediaWiki community it advises. Technological scaling of this sort involves an increasing discrimination capability (more points in space); and using feedback to fine tune a sensor's activation threshold (e.g. gaugeing the notability of a Soap opera episode article is not the same task as an article on a war.
This type of scaling requires creating sensors that become more refined as the wiki grows.
Simone's response to the above strategy is to provide smarter data driven sensors. The data for these will come from sampling the wiki so they will be normative rather than proscribing what may become unrealistic utopian criteria. By considering more data and by clustering this data to more levels it is possible for the same basic sensor to track changing dynamics as wikis evolve over time. Both positive and negative feedback mechanism can then be used to adjust the behaviour signatures which it detects .
The sensor developer's goal is Pareto efficiency. With a robust detection of Context, Content, Notability, References , Style and Social behavioral signatures in user edit and talk Simone will to preempting 20% of the most socially damaging reversion/deletion events which should dramatically reduce community oversight by about 70-80%.
The handling of remaining incidents would require human intervention and provide greater engagement. If not then once such a milestone is achieved the method can be refined by adding sensors and refining existing sensors to track the top 20% of remaining issues. This is likely since deeper underlying problems (such as cultural and gender gap issues) may be obscured by more visible issues.
Sensors could also be added to address additional (non editorial) concerns so long as the phenomena is discernible using techniques of discourse analysis. This simplest should involve retention of experienced editors.
In cases where a rules and pattern are too weak to detect issues (Such as neutrality) it will be necessary to produce a collection of good/bad edits and train models to discriminate their issues. Building some "Gold standards" will be one of the project's mile stone since it will involve community expertise and feedback.
Also if such issues become a priority the community will be requested to assist by tagging problematic revisions. Though this can be accelerated by earmarking a budget to outsource corpus development by outsourcing the work online using Amazon mechanical Turk at a token cost per tagged revision. This approach has been reported to be successful in developing an anti spam corpus.
biting sensor - incidents of new user biting.
biter's leader board to mitigate biting and identify delinquent bitters.
determines quantitive the amount of information in this article.
Sensing problems is not enough – Simone needs to offer useful advice. Since this will be the most visible aspect of the project it needs to be developed with great sensitivity to users and community acceptance. Advice defaults will provided but this will only be a starting point. Again community input will be requested on this subject. Suppose the community solicits our projects with 3 advice notices for a certain issue - say lack of Citations. Simone would systematical test these messages and score them based on their success (i.e. check how each advice correlates with the sensor score for Citations in following edits.) Tracking advice - and correlating using R in a DB will be another Project milestone.
0.0625 Add the article skeleton using section titles.
0.03125 Add project description in talk page.
0.03125 Add an interview link to a version in another language.
Advice is offered in the scope of missions which are grouped under a single goal.
Goals are collected in strategies.
S5 Stub Add project description in talk page.
To speed Simone's' community acceptance, default advice will be provided to the initial project by the developer. This is perhaps the most labour intensive task -- primarily because Simone would like to support new user in their first thousand edits to bring them into relatedness with other Wikipedians. To provide meaningful and engaging advice different editing issues would have to be explained in text and video.
Making its sensors cross lingual.
determining a socio-editorial policy using the deletion/reversion history and deriving concrete list of violation.
sending out a Request For Advice to the project's community.
beta testing the behaviour on a control group.
Thus Each project could adapt Simone to its needs.
As already explained metrics are at the very heart of this projects - we call the sensors.
Simone will generate detailed logs of its activity.
Reporting will be generated from the logs.
Simone will be configured initially to have a control group which will not get the benefits of coaching.
incident (selected sensors correlating to high level events).
new editor acclimatization to the community.
editor under coaching mass action. The overall edit count * positive change due to these as seen by sensors.
No claims about the long-term of the project only suggestions. I hope it is taken over by the WMF development team and more tightly integrated into MediaWiki whose shortcomings it addresses. However, since it is not the traditional model for robot based tools, the more realistic community process will be explained in the different roles of different stake holder involved.
Today Bots developers are the most influential members of the community. Within the limited scope of their projects they provide more agile solutions than the WMF. They are also better aligned to the community's needs because not only must they get approval to run their bots from committee, they must then respond to issues raised by users.
Simone will be created in short development cycles as a MediaWiki based project - using git for source control, labs for test deployment, Bugzilla for bugs, code review for reviewing external patches once these are provided, translate wiki for internationalization.
Bots are mostly constructed from a few exiting frameworks and thus there exist a possibility of a high mobility within the community if a better technology is introduced. It some areas, such as ranking articles for completion and importance, Simone would provide a significant technological edge. This suggests that there is potential for pooling resources with exiting robot operators.
She will be deployed and start collecting data early on and generating reports. Her nature is planed to be extension. This means that the community will be given freedom to contribute to this project.
Her code will be available as open source.
Data analysis scripts will be provided.
Documentation will be provided on installation.
Evangelism at Wikimedia, and Hackathons and other conferences would boost this community.
After the end of the fellowship the volunteers will be found to take over and maintain the project.
The stake of administrators in running Simone - is that she will oversee editing in a the grey area between spam and good edits. This will provide a massive reduction in patrolling.
After undergoing the robot approval process Simone will be operated on Wikipedia. As usage will increase responsibility to operate it will be transferred to qualified Administrators.
fine tuning its sensors and their thresholds.
add remove or change defining goals, mission, and advice hierarchies.
There is a number of suggestions proposed to policy in this proposal. These changes will be performed informally by Simone. As well-tempered users invade the community these policies will gain weight and gradually replace the existing practices.
A key assumption is that as Simone influence will be felt by policy makers. In this view when they decide to repel anti-social policies Simone will be reconfigured to fill in the resulting vacuum. This will allow to reform current policy to a shorter and clearer set of guidelines — more suitable for a larger more diverse society of contributors.
Human Coaches will be asked to provide expert advice on coaching and help for debugging based on the open source doctrine of many eyes find bugs faster. Thiers stake in Simone is that it will make coaching more fun and productive. For humans the tasks will be less technological and more of a social activity.
These will be use by developers and administrators.
Domain experts can be paired with more seasoned editors to work as pairs. One contributing domain knowledge, the other providing wiki know how. This is another situation of changing the game from zero-sum to win-win rule.
Specific project in Wikipedia such as biography of living persons have their own needs. Simone will be able to address these projects as a group, recommend new users to join the projects teach people the rules required in these and arrange collaboration on top priority articles. This coordination will allow a participating project to get boost in personal and to focus them on work in teams on the articles of greatest importance. This is something of a lost capability now that matching articles to individuals. Simone's user Soliciting module could be fine tuned from the start to training users in their areas of expertise in a socially acceptable way.
Simone will provide reports on its activities. Its high level strategies would have better results of based around research carried by experts in this field. By providing better answers to the key theoretical questions it will be possible to define better goals and sensors and preemption strategies for Simone to pursue.
For example if there is more knowledge on conflict situation Simone could be instructed to preempt conflict [note 20]; existing user retention.
life span in days/edits of editor generations.
percentage of new articles deleted under each SD clauses.
percentage of new articles deleted under other clauses.
degree of communication before reversion event.
time from first edit to becoming an administrator.
The most important role for Simone is that of community interaction. As users work with her she will become wiser and able to give better advice. Maintenance of advice as Wikis' policy changes is one major role of the community.
↑ this and other avatars used for Simone are based on Wikipe category are taken from commons and were contributed by their respective creators.
↑ These are much harder and slower to change as these involve about two to twenty thousands active community members every month and a process that relies distributed process that is unpublicised and is consensus based.
↑ Social problems exist at a level where there is too much friction and too small opportunities for communication to effect change by individuals.
↑ Value in the form of new or improved articles is immediately available for all. An increase in community size affects the community members indirectly though allocation of tasks and resources. New editors do not perform much communal tasks. Because each member only does as much work as they wish to they can personally avoid the consequence of a reduced population. The brunt of the cost is paid by the community.
↑ a nieche wiki dedicated to covering a specific knowledge domain or an alternate community lacking the social complexity required for editing Wikipedia.
Kin Selection - individuals whose interest are closely related, whose cooperation brings them even closer based on mutual interests.
Direct reciprocity - trading favors in paired relationships within a multi-round games with a capability for individuals to punishing a defector.
Indirect reciprocity - multi rounds under anonymous conditions.
↑ Without research on the subject, my own informal tests indicate that coordination is the greatest stumbling block to cooperation. Followed by communication.
↑ One has to develop a user page, learn to respond to policy challenges laced with Jargon in like kind and develop an edit count.
↑ autamated quality assessment can be done faster and at a higher level of objectivity by machine. Importance is contextual and thus less suited for machine assessment. But capturing both it is possible to make use cross validation in a repeated article rating game in which editors get a reputation by self select though accurate ranking in a knowledge domain. Accordingly their votes on importance are boosted or discounted accordingly.
↑ a list of same game theoretic motivated questions on wiki editing behaviour together with raw Simon data would be provided if the project is funded.
↑ a b The Tyranny of Structurelessness by Jo Freeman (1970).
↑ Understanding Media: The Extensions of Man — Marshall McLuhan McGraw Hill, NY, 1964; ISBN 1-58423-073-8.
↑ E. Goldman. Wikipedia's labor squeeze and its consequences. Journal of Telecommunications and High Technology Law, 8, 2009.
This section is for endorsements by Wikimedia community volunteers. Please note that this is not a debate, vote, or poll, but is rather a space for volunteers to describe in detail why they think a project idea is of value. If you have concerns or questions rather than an endorsement to make, please use the idea Talk page. Endorsements by volunteers willing to work in collaboration with a fellowship recipient on a project are highly encouraged.
This page was last edited on 25 July 2012, at 19:38.


the unprocessed sound file, which is the signal captured by the front microphone of the right hearing aid. The front, middle and rear microphone signals of the right hearing aid are the inputs to the SP-SDW-MWF algorithm.
the processed sound file, which is the output of the SP-SDW-MWF algorithm.
As can be observed, beamforming algorithms suppress directional noise sources very well in a lowly reverberating room.
Despite the more difficult scenario due to a lower SNR and more room reverberation the amount of noise suppression is still considerable. Observe that the quality of the desired speech signal is hardly affected by the processing.
This is the most challenging scenario : a highly reverberating room and diffuse background noise. Note that the amount of noise reduction is now clearly lower than in the first, low-reverberant scenario. Nevertheless, the algorithm is still capable of enhancing the signal without too much affecting the signal quality.


text:
MMSD Moves for Greatness as New Ministers Resume Duties
Today marks the beginning of a new era in the history of Ministry of Mines and Steel Development as the management and staff of Ministry of Mines and Steel development regard the deployment of Architect Olamilekan Adegbite and Dr. Uchechukwu Sampson Ogah as the round pegs in round holes. The ministry hopes that with the caliber of ministers sent to it, there is no doubt going to be total transformation to meet its expectation by the present administration
The Minister, Ministry of Mines and Steel Development, Arch Olamilekan Adegbite as well as Dr. Uchechukwu Sampson Ogah has identified team work as panacea to the success of their work in the ministry. The ministers said this while resuming duties in the ministry.
Adegbite said that for the ministry to achieve greatness, there is need for concerted effort and cross breeding of ideas. He emphasized the multi nature of corruption and the need for the ministry to be outstanding in the fight to curb the menace in the society. According to him the Present administration has taken the challenge of bringing up to hundred million Nigerians out of poverty in ten years which the president and his team are resolved to achieve above forty percent of it within four years through inclusive efforts.
The Minister of State for Mines and Steel Development Dr. Uchechechukwu Sampson Ogah in his remarks said that thesame uniqueness and brotherhood that the ministry is known for will still remain their watchword. He urged the management and staff of the ministry not to look at them as depository of knowledge rather to present their technical and professional know how to move the ministry forward.
Earlier the Permanent Secretary Dr. Abdulkadir Mu'azu while welcoming the Ministers in the ministry said that one peculiar strength that the former ministers had was the 'brotherhood' that existed among them. He said that no doubt Dr. Fayemi and Hon. Bawa did their best by injecting life into the ministry but with the antecedents of the present ministers the ministry is geared towards total revolution for better results.
Mu'azu reiterated the commitment of the management and staff of the ministry to aid the ministers to achieve greatness during their tenor as umpires of the ministry. He emphasized on the strategic nature of the ministry and its key role in the economic diversification policy of the Mohammadu Buhari-led administration.