Open falexwolf opened 5 days ago
Simple things:
.get()
.backed()
to .open()
.from_values()
and add Curator
.save()
and curator.save_artifact()
because these are the two fundamental ways of saving plain & annotated output data.Rather than calling it "Access", we could call it "Query" if we wanted to more immediately convey that Lamin allows queries rather than more naive forms of access.
The issue is that often times, with query we mean .get()
and .filter()
; and .search()
and .open()
on an array with subsequent subsetting are referred to as "search" and "slicing".
One could say "Iterate" instead so that it's clear that you're supposed to go "round & round" many times. Because the function is called "track()", this might be clear already.
Ref: https://lamin.ai/laminlabs/lamin-site-assets/artifact/BunYmHkyFLITlM5MYQTN
I think it's been a great graphic for a year, but we can improve. This issue collects suggestions for improving it.