Lawrence:

Have you considered deleting the resource objects before you deploy a new one?

Check out DeleteObject[].

Your assumption about multiple rows in the ResourceSearch results is correct. If you deploy the same content multiple times to cloud, if can appear multiple times in the search results.

To be clearer, each time you evaluate ResourceObject[<|...|>] it creates a new ResourceObject with a unique uuid (use ResourceObject[...]["UUID"] to see the uuid). ResourceObjects with different uuids are treated as unique resources and will appear separately in search results.

DeleteObject[ResourceObject[...]] removes the stored content of only that specific ResourceObject, identified by its uuid. It will not delete other deployments of the same name. It should remove both local and cloud caches. Based on your "I've also tried several ways..." paragraph, it is possible there is a bug, either in DeleteObject or ResourceSearch, which maintains its own local cache of cloud metadata. Which $Version are you using?

Looking at the big picture, if your goal is only to make this data available for yourself in multiple environments, I agree with Jan that CloudPut or CloudExport are more straightforward.

If the goal is to make something to share with others and includes documentation with examples and metadata, then ResourceObject is the way to go. In that case, I encourage using the definition notebook interface CreateNotebook["DataResource"]. That notebook was overhauled in version 12.1 adds a lot of explanation that is missing in the programmatic CloudDeploy[ResourceObject[...]].

If you are dedicated to your current workflow, I recommend using ResourceData@ResourceObject[CloudObject[...]] with the CloudObject returned by CloudDeploy in order to ensure that you are using the correct deployment.

Hi Lawrence,

Is there a reason for not using CloudPut and CloudGet as suggested by @Jan Poeschko

So, I'm now trying use ResourceData to push my data into the cloud. Then I want to reference that data in another NB to process it. Seems simple enough.

importSpreadsheet[] := Module[{items, names, data, assoc},
   items = 
    Import["/Users/wkr/Documents/Elections/Closing Graph.csv", 
     "CSV"];
   names = items // First;
   data = items // Rest;
   assoc = AssociationThread[names, #] & /@ data;
  Dataset[assoc]
   ];
buildDataResource[ds_] := Module[{},
   ResourceObject[Association[
     "ResourceType" -> "DataResource",
     "Name" -> "ElectionCloseDataset",
     "Content" -> ds,
     "Description" -> 
      "Dataset created from the Closing Graph Spreadsheet"
     ]]];
storeGraphDataset[] := Module[{ds},
   ds = importSpreadsheet[];
   buildDataResource[ds]
   ];

Now, generate a resource object and deploy to the cloud

ro = storeGraphDataset[];
CloudDeploy[ro, "ElectionCloseDataset"]

The above seems to work.

Now, in order to use this resource, I want get back the dataset portion of the resource, with code in a different NB.

ro = ResourceSearch["ElectionCloseDataset", ResourceObject]

I get back the resource object but none of my attempts to return the dataset that should be in the ResourceObject works.

What is the correct syntax?

I've been playing around with WL ResourceObjects and related functions. I'm guessing I might need a notebook to pull in the data and push it out to the cloud. Then a notebook to find the resource objects in the cloud, pull it in and run the processing.

I think I made a mistake using New -> Repository Item -> Data Repository Item to create a resource object. Seems too complicated for what I wanted. It's a notebook template for documentation of the data, and there is a button to deploy and another to submit. The submit became a request to ask Wolfram to make the data available to others as though my data would be of interest to anyone but me. I really didn't want to do that.

Simple and stupid is all I can muster at the present.

With Mathematica, I'm not yet much of a risk-taker to just try something and see if it works. I don't have the knowledge to know what problems I could be causing when stuff doesn't work and how to debug it when stuff doesn't work. I don't want to clutter up Wolfram's cloud with my poor decisions.