Asset ID

[getavalon]

Asset ID

[mottosso]

Some progress on this.

Proposed database layout

{
	"f034a4b": {
		"type": "asset",
		"name": "Bruce",
		"path": "{projectdir}/assets/{name}",
		"parent": null,
		"children": [
			"b07deyha",
			"u02f0dyh"
			"046kdaog"
		]
	},
	"b07deyha": {
		"type": "subset",
		"name": "modelDefault",
		"path": "{parentdir}/{name}",
		"parent": "l35dsog3",
		"children": [
			"od45qffl",
			"l35dsog3",
		]
	},
	"l35dsog3": {
		"type": "version",
		"name": "v001",
		"path": "{parentdir}/{name}",
		"parent": "b07deyha",
		"children": [
			"dre0463f",
			"ked4g9af",
		],
		"metadata": "{parentdir}/{name}/.metadata.json"
	},
	"dre0463f": {
		"type": "representation",
		"path": "{parentdir}/modelDefault.ma",
		"parent": "l35dsog3",
	}
}

This would require..

1. Upon creating a new project, a new database is created
2. Upon creating a new asset, an entry is made
3. For each published subset, an entry is made
4. For each version and representation, entries are made

Requirements 1 and 2 are currently not possible due to both projects and assets being created by primitive Windows-specific .bat files. What would need to happen is for the Terminal API to be written in a higher level language with the ability to open and modify the database which would be JSON for starters, Firebase later and eventually a self-hosted equivalent such as MongoDB.

[mottosso]

Implemented in #116.

Every project, asset, subset, version and representation now have a unique address accessible via find.

from mindbender import io
asset = io.find({"_id": "unique_id_here}
asset["name"] == "Bruce"