Add staging back in

models/docs/sources/history_assets.md

@@ -1,6 +1,6 @@
 [comment]: < History Assets -
 
-{% docs history_assets %}
+{% docs history_assets_staging %}
 Table reports which assets are used during the batch interval, which can help identify periods of time of large activity for an asset. The table **does not** have a primary key and assets are duplicated in the table as they are used during different periods of time. To get a distinct count of assets on the network, please refer to the history_assets table. Table not widely used.
 {% enddocs %}
 

models/sources/src_history_assets.yml

@@ -4,8 +4,8 @@ sources:
   - name: crypto_stellar
     database: 'crypto-stellar'
     tables:
-      - name: history_assets
-        description: '{{ doc("history_assets") }}'
+      - name: history_assets_staging
+        description: '{{ doc("history_assets_staging") }}'
         columns:
           - name: assets_id
             description: '{{ doc("asset_type") }}'

models/staging/stg_history_assets.sql

@@ -7,7 +7,7 @@ with
             , row_number() over (
                 partition by asset_id order by batch_run_date asc
             ) as dedup_oldest_asset
-        from {{ source('crypto_stellar', 'history_assets')}}
+        from {{ source('crypto_stellar', 'history_assets_staging')}}
     )
 
     /* Deduplicates the new batch assets, guaranteeing they are unique within the batch */