ha-overall-progress.md

@@ -43,6 +43,10 @@ This looks like a long list, but hopefully it isn't in reality. I've just broken
 
 1 - Delete API is questionable
 
+> suggested input: HouseAdID
+> Suggested output: 200OK
+> process: update HouseAd with HouseAdID given to have HouseAdStatusID=0. reload the page or remove the object from the user's current data set and move on.
+
 1 - Duplicate functions as if it were a normal edit. Forwards to template which doesn't make sense IMO. We probably just want to pass data with the ID's and UIDs stripped and have edit key on empty IDs
 
 2 - A Date of "NEVER" is indistinguishable from the user actually choosing that date. We display the date instead of "NEVER" which probably will confuse the user.
@@ -71,10 +75,27 @@ This looks like a long list, but hopefully it isn't in reality. I've just broken
 
 1 - API For submisision is questionable
 
+>>> Proposed input: entity_id, entity_type, file stream of asset, compositionTitle, templateID
+>>> Output: one FULL house ad object reccomended, but minimum is houseAdID.
+>>> See info bullet below for steps.
+
 5 - Page retains old data and preloads that before loading current. is mildly jarring
 
 * The file uploaded as the asset should be the key-value pair of template text value -> new text value. This is inconsistent with some old documentation. As of my exit, this change has already been planned but not tested or prototyped.
 
+* The submission of a completely new house ad here is a highly orchestrated set of steps presented roughly here: 
+```
+1. copy the file stream to the content server. (done first since this takes ~2 minutes to trigger normally, give it the biggest head start)
+2. create the manifestFile for this object.
+3. create a HouseAd Object using the title from the request params. Stub out duration=15, weight=n(predefined number, choose a value we can deprecate or work with later), HouseAdStatusID=1. record the HouseAdID
+4. Using entity_id and entity_type, link the HouseAdID from 3 to the entity.
+5. Create the composition Object, using the HouseAdID from 3 and HouseAdTemplateID from request params. Stub HouseAdCompositionTypeID=1. Save HouseAdCompositionID.
+6. Generate the Asset object, Using the ManifestFileID from 2, save HouseAdAssetID.
+7. Using HouseAdCompositionID from 5 and HouseAdAssetID from 6, link them.
+```
+
+* Updating an existing house ad should be the same as above, except we already have all the IDs from each step. so upsert is an update if IDs are present, insert if IDs are not present. This is important since it is a procedural/staged submission. URL should be idempotent when IDs are present.
+
 -----
 
 #### HA-71 Schedule:
@@ -89,6 +110,9 @@ This looks like a long list, but hopefully it isn't in reality. I've just broken
 
 1 - API for submission is questionable.
 
+>>> Proposed submission data:
+>>> input: houseadID, start date, end date, weekdays
+>>> output: none needed, can return entire ad, will likely be ignored.
 
 ---