So that the web project can add an agency with all its details.

Run the procedure described in the README and make any corrections

Hi

Based on the url https://wildaid.github.io/build/2020/06/09/Data-Import.html. Following these commands:
mongorestore --drop --uri "mongodb+srv://[email protected]/" /Users/sheeri/wildaid_demo/o-fish-realm/WildAidSampleBackup When it is successful, you will see a message like: 6117 document(s) restored successfully. 0 document(s) failed to restore.

(Obviously I'm replacing the user specifics here, for my own setup)

My output for reference is:
2020-06-12T13:54:42.366-0300 preparing collections to restore from 2020-06-12T13:54:42.412-0300 reading metadata for wildaid.BoardingReports from WildAidSampleBackup/wildaid/BoardingReports.metadata.json 2020-06-12T13:54:42.453-0300 reading metadata for wildaid.ChangeHistory from WildAidSampleBackup/wildaid/ChangeHistory.metadata.json 2020-06-12T13:54:42.496-0300 reading metadata for wildaid.Agency from WildAidSampleBackup/wildaid/Agency.metadata.json 2020-06-12T13:54:42.559-0300 restoring wildaid.Agency from WildAidSampleBackup/wildaid/Agency.bson 2020-06-12T13:54:42.611-0300 no indexes to restore 2020-06-12T13:54:42.611-0300 finished restoring wildaid.Agency (3 documents, 0 failures) 2020-06-12T13:54:42.796-0300 finished restoring wildaid.BoardingReports (0 documents, 0 failures) 2020-06-12T13:54:42.796-0300 Failed: wildaid.BoardingReports: error creating collection wildaid.BoardingReports: error running create command: (Location40415) BSON field 'create.recordPreImages' is an unknown field.

It only results in 3 records being added to the Agency collection. The sampledata, also seems to be missing collection files. I only see files for agency, boradingReports and changeHistory. But the images on the aforementioned url seem to suggest other collections. If you could help with this, that would be great 😄

Thanks

This is currently defined in https://realm-dev.mongodb.com/groups/5e5f73d4b19df941b9221044/apps/5e60d0f82b41db10af8dca5c/functions/5ee2e7fd1c070cdb0fb8bca4

Should no longer store the actual image binary in the User collection

Write a basic contributor guide.

@Sheeri need to understand the functionality behind user groups. e.g.:

• Do all members of a user group need to be from the same agency?
• Can the same group name be reused by different agencies?
• What are the consequences of 2 users being in the same group?
• What are the consequences of 2 users not being in the same group?

When the mobile app adds a new headshot for the current user, it adds the photo to the Photo Realm Object (along with the email address of the user).

When that photo hit Atlas, we need a Trigger to copy the image to the User document associated with the email address.

Step 17 is obsolete as 19 covers the same ground, but in a better way.

The URL for the file in S3 currently contains the agency name - which may include spaces or special characters – resulted in a calculated URL which can't be used. Instead, just use the _id of the Photo document to uniquely identify the file.

Include a field called createdOn in the sample User document in the README. It should be set to an ISODate.

Include and overview of the project: goals, components, infrastructure. And probably a table of contents because it's getting long.....

The widaid.User collection should have a new group attribute which in turn contains attributes for group name (string) and whether they're an admin (bool)

To match the sample report documents, update the README to show the sample user having the agency set to "Parque Nacional Galápagos".

Change the realm schema

Firstly, please let me know if this is better suited to the Realm Forum at MongoDB.com

Just going through this realm application set up. I'm currently on this page https://wildaid.github.io/build/2020/06/09/Import-Realm-Code.html.

These are the steps and my steps

1. In the template, you have a field called “Path to Realm code”. Go to that directory - you should be inside a directory called WildAidDemo.
   Correct, I'm in that dir

2. Edit stitch.json change “name” to your “Realm App Name”
   Changed to my app name of "WildAidApp"

3. Edit services/RealmSync/config.json services/mongodb-atlas/config.json
   and change the value of “ClusterName” to your “Atlas Cluster Name”
   Changed to "O-Fish" my cluster name

4. If you are not using AWS, skip this step. If you are, edit the following files and fill in all the relevant details:
   values/awsRegion.json values/destinationEmailAddress.json values/sourceEmailAddress.json
   I'm not using an external AWS service as the previous page asks. My Mongo instance is a free tier on AWS however. Do I still need to complete this piece? I did update the awsRegion to us-east-1 after my ignoring it the first time I tried to import the realm-code

5. If you are not using AWS, skip this step. If you are, set accessKeyID if using AWS in the file:
   services/AWS/config.json.
   Same here, not using AWS, I did use the secret-key it makes you generate in the previous page, as I didn't exist it to make any difference

Do the import, confirm with ‘y’ when prompted to confirm changes. You will paste your Realm App ID into –app-id:
stitch-cli import --strategy=replace --include-dependencies --app-id=REALM_APP_ID

I adjusted this to realm-cli which I believe is correct and added my REALM_APP_ID too. The same one that was needed from the previous page.

But I get the error could not find realm app

So not exactly sure what I did wrong here?

Again, apologies if this should be in the forum 😄

This can be the image that the apps are using to denote that an avatar hasn't yet been added.

The web app's boarding page currently sends a query with an unlimited list of report IDs to be rendered on the map. That breaks limits on the size of http requests.

Instead, we should have server-side Chart logic that takes filter criteria, which it then uses to find all of the documents that should be rendered on the map.

Once that is implemented, raise a web ticket to use the new Chart.

Use the partnerAgencies attribute in an Agency document to indicate which other agencies this agency grants permission to read their boarding reports.

An Agency document should be able to contain an array of sub-documents containing a partner agency name and (optionally) a start and/or end date.

These attributes should be checked by the rule that controls whether a user can read a BoardingReports document.

When creating a Boarding report from the mobile apps (containing Lists such as the crew), this is converted into an INSERT and then a REPLACE into the Atlas collection – causing the trigger to be hit twice.

Need to ensure that the triggers are run sequentially or else the INSERT trigger can fail with a duplicate key (_id) error.

realm-cli has replaced stitch-cli

To support WildAid/o-fish-android#26 and WildAid/o-fish-ios#30

When a Photo document is modified, the newPhoto trigger should replace the existing image in S3 with the new one (if one is there). The URL can stay the same or a new one can be created (which would then be stored in the document).