DD 2.0 Lookup Ids missing about web-api-commander

[darnjo]

Hi. Thanks for opening a ticket.

This is more of a support question than something related to the Commander. For non-Commander issues, please reach out to dev at reso.

We still use LookupId and all the other ID fields.

If you look at A-Frame, you can see both LookupID and LookupNameID are present.

Similar with Pickleball:

We have, however, deprecated the old IDs in favor of hashes. The old IDs are now in the LegacyLookupNameId and LegacyLookupId columns in the DD reference sheets.

[tlingard]

I wasn't sure where to send this, but saw updates and changes to the spreadsheet on here. We were pulling schema out of the spreadsheet, and using the hashes, then came up against the missing ones. Will get the missing ones from the website. Thanks!

[darnjo]

Nice to hear you're using the reference sheets for schema generation. We do similar for Certification. We have some reference JSON Schema if that's helpful (though it sounds like you're using more than what might be there).

In that case, feel free to open tickets on this repo when you see anything awry. The feedback/QA is much appreciated and helps us address potential issues.

I'm guessing you got an intermediate update before the DD Wiki had been regenerated, as the lookup name IDs and lookup IDs come from that process. Working on adding it to the build process so it happens automatically but need to do a little work there first.

We probably need to update the definitions a bit in the DD Wiki to reflect the current items in the sheet. There are also some schema changes to the reference sheets for DD 2.1 starting this Fall FYI.

[darnjo]

As a side note, the current DD 2.0 reference sheet shouldn't have any blank lookup name IDs or lookup IDs, so I don't think you need to get them from the website.

[tlingard]

The sheet was from a month or so ago. We're doing mostly exploratory work to get a small subset of fields set up with Datomic/Datascript (mostly flat entity/attribute lvl schema db).

There are a few things that cause snags using the RESO reference sheet to normalize it for Datomic. Mostly, inconstant naming and missing reference fields (SourceResource etc). There were a couple of fields that appear out of place/redundant; it could also be a misunderstanding of it's purpose on my part.

Added some notes I had to a nextjournal clojure notebook. The visual data of snags, and questions, may be more helpful than opening tickets for what may amount to a discussion more than an issue. Such as the redundancy of the resource/group Association/Association

Is there a public place to keep up with current discussions, such as schema changes to the reference sheets for DD 2.1? Or, is it more of an internal process?

The Nextjournal notebook if interested - remix it to explore the data further.
https://nextjournal.com/a/T1ki98aUmFJzPM7RNghnK?token=PQvAcWpGMQygNq5TiomDnU