1. Insta-Edit
1.1. Basic Concepts
1.1.1. Insta Correct is only for issues we can identify for certain - Author can still reject.
1.1.1.1. Allow author to bypass correction, flag for review
1.1.2. Insta Prompt is for uncertain "you might wanna check" values. Author can reject.
1.1.2.1. Allow author to bypass correction, flag for review
1.1.3. ErrorText = specific comment from the Reviewer Comments table
1.2. Modules
1.2.1. assign $Content = text passed
1.2.2. assign $ErrorID as the Review Comments ID
1.2.3. Insta-Prompt
1.2.3.1. Specific Issues
1.2.3.1.1. Title too Short or not descriptive Enough
1.2.3.1.2. Byline in Title
1.2.4. Insta-Correct
1.2.4.1. Specific Issues
1.2.4.1.1. Title Not in Title Case
1.2.4.1.2. Decorative Lines in Title
1.2.4.1.3. Multiple Punctuation
1.3. Data
1.3.1. Store old and new values, until accepted by Author. Discard old.
1.3.1.1. Author Accepts
1.3.1.1.1. Discard old value
1.3.1.1.2. Move to next
1.3.1.2. Author Rejects: Discard new value
1.3.1.2.1. Discard new value
1.3.1.2.2. warning message
1.3.1.2.3. Flag article for Reviewers
1.4. Interfaces
1.4.1. Post-Submission Form
1.4.1.1. One Moment Please... reviewing this article now... (animation)
1.4.1.1.1. Formatting issues
1.4.1.1.2. Grammar issues
1.4.1.1.3. etc (see"am_problem_type" table)
1.4.1.2. Display error list
1.4.1.3. All errors must be cleared or rejected before moving to Human_Edit
1.4.2. Edit Form
1.4.3. Review Form
1.5. Processes
1.5.1. Reviewers - make a note of "false positives"
2. Account Features based on Account Parameters
2.1. Constant Distribution
2.1.1. Launch Values
2.1.1.1. True/False
2.1.2. Interfaces
2.1.2.1. None
2.1.3. Modules
2.1.3.1. Runs when new sites join list requesting all articles
2.1.3.2. Calculate which articles to distribute
2.1.3.2.1. $Plans()= array of all plans where Constant Distribution = True
2.1.3.2.2. $CurSubs()= array of all current subscribers in $Plans()
2.1.3.2.3. $ConstDist() = array of all articles belonging to $CurSubs() where start_date before now() and end_date after now()
2.1.3.2.4. Run "Queue" function for all articles in $ConstDist()
2.2. Articles
2.2.1. Interfaces
2.2.1.1. Joomla Menu
2.2.1.1.1. Runs when user clicks to "Submit Article"
2.2.1.2. DYA Features (Joomla Admin)
2.2.1.2.1. Time Parameter
2.2.2. modules
2.2.2.1. Calculate remaining articles
2.2.2.1.1. $days = Value of time parameter from account description
2.2.2.1.2. $articles = value of articles allowed from account description
2.2.2.1.3. $datenow = value of today's date (system)
2.2.2.1.4. Calculate $startdate =$datenow-$days
2.2.2.1.5. $articlesubs = Count articles submitted between $startdate and datenow (from articles table)
2.2.2.1.6. Calculate $remarts = $articles-$articlesubs
2.2.3. Data
2.2.3.1. Time Parameter
2.2.3.1.1. Store time parameter in account description in DB
2.3. Categories
2.3.1. Possible Values
2.3.1.1. Launch
2.3.1.1.1. For Launch, 1 or 2 or 3, no unlimited
2.3.1.2. Post-Launch
2.3.1.2.1. any number, or unlimited
2.4. Versions
2.4.1. Launch Value
2.4.1.1. true/false
2.4.2. Interfaces
2.4.2.1. Submission Form
2.4.2.1.1. Author enters article information
2.4.2.1.2. Author selects "Versions" on a field by field basis - check boxes on the form, yes/no
2.4.2.1.3. Submit Article button pressed
2.4.2.2. ContentBoss information gathering Form
2.4.2.2.1. Fields
2.4.2.3. Reviewer Form
2.4.2.3.1. Display Versionable Text Source (ContentBoss;Modified;Author)
2.4.2.4. Article Edit Form
2.4.2.5. Version Form
2.4.2.5.1. Fields
2.4.2.5.2. Button
2.4.2.5.3. Submit For Review
2.4.2.5.4. Submit and Hold
2.4.3. Module
2.4.3.1. VersionDeterminator() = (db lookup) Versions allowed in DYA Features for $PlanID
2.4.3.1.1. Triggered when submission form loads
2.4.3.2. ContentBossCredFind()
2.4.3.2.1. DBLookup: Credentials in system?
2.4.3.3. Get CBVersionables()
2.4.3.3.1. Triggered by CB Module
2.4.3.4. Process Versionable Text from ContentBoss and display on (???)form
2.4.3.5. Determine Versionable Text Source
2.4.3.5.1. Compare submitted text to stored Versionable Text (Each Field)
2.4.3.6. SpinNewVersion()
2.4.3.6.1. CB provided code
2.4.4. Data
2.4.4.1. Store VersionableText from ContentBoss in db
2.4.4.1.1. CBText Columns
2.4.4.2. Store Versionable Text source in article record
2.4.4.2.1. Versionable Text columns
2.4.4.3. store CB Creds from ContentBossCredFind()
2.5. Pen Names
2.5.1. store password in plain text for sending to dist sites
2.6. Auto-Pilot
2.6.1. true false
3. Site Specific Login
3.1. Interfaces
3.1.1. Site Specific Login Data Capture
3.1.1.1. Form Fields:
3.1.1.1.1. Site ID(dropdown - active sites on our list)
3.1.1.1.2. Username
3.1.1.1.3. Password
3.1.1.1.4. email address
3.1.1.1.5. Author First Name
3.1.1.1.6. Author Last Name
3.1.1.1.7. Date Entered
3.1.1.1.8. Date Updated
3.1.1.1.9. POST LAUNCH: iFrame of site, test credentials, display to user
3.1.1.2. does not allow multiple records for the same site+user - allows update. Do not store old values
3.2. Data
3.2.1. Store user ID + site ID + credentials in site_specific table
3.2.1.1. DB Fields:
3.2.1.1.1. Site ID
3.2.1.1.2. Username
3.2.1.1.3. Password
3.2.1.1.4. email address
3.2.1.1.5. Author First Name
3.2.1.1.6. Author Last Name
3.2.1.1.7. Date Entered
3.2.1.1.8. Date Updated
3.2.2. Site_Specific_Archival table
3.2.2.1. DB Fields:
3.2.2.1.1. Site ID
3.2.2.1.2. Username
3.2.2.1.3. Password
3.2.2.1.4. email address
3.2.2.1.5. Author First Name
3.2.2.1.6. Author Last Name
3.2.2.1.7. Date Entered
3.2.2.1.8. Date Updated
3.2.2.1.9. Date Archived
3.3. Modules
3.3.1. Fires when button pressed on site specific login form
3.3.1.1. Gather all values as variables
3.3.1.2. Connect to site, display in iFrame on form
3.3.1.3. Pass variables to site
3.3.2. Fires during distribution process
3.3.2.1. Get Credentials
3.3.2.1.1. Get $userid
3.3.2.1.2. Get $siteid
3.3.2.1.3. Seek $userid + $siteid in site_specific table
3.3.3. Fires based on Cron Job
3.3.3.1. Cleanup SiteSpecific table
3.3.3.1.1. Reason: keep this table as small as possible to minimize seek time
3.3.3.1.2. $SSLog_Plans() is arrayof plans allowing site specific login
3.3.3.1.3. $userplans() is array of users in the site_specific table and their current plans
3.3.3.2. Multiple email warnings
3.3.3.2.1. Your subscription has lapsed. You have xx days to reactivate your account before all of your site specific records are erased and cannot be restored.
3.3.4. Fires based on Cron Job
3.3.4.1. Cleanup SiteSpecificArchival table
3.3.4.1.1. Run Delete Query on all records where archival date is greater than 40 days ago