Master Index: Difference between revisions
Jump to navigation
Jump to search
(→Proposal (February 2015): add discussion section) |
m (Fix link →Discussion) |
||
| Line 25: | Line 25: | ||
Pro: | Pro: | ||
* Central point of reference for all modules | * Central point of reference for all modules | ||
* Machine-readable -> can be further improved by using some open standard like xml | * Machine-readable -> can be further improved by using some open standard like xml with nice frontend | ||
* More structured than Dozuki | * More structured than Dozuki | ||
* Better overview than with Dozuki -> or can Dozuki be improved to provide this sort of meta data and dependency graph? | * Better overview than with Dozuki -> or can Dozuki be improved to provide this sort of meta data and dependency graph? | ||
Cons: | Cons: | ||
* No visual rendering -> Can be solved by adding nice frontend (e.g. Dependency graph using [www.graphviz.org | * No visual rendering -> Can be solved by adding nice frontend (e.g. Dependency graph using [http://www.graphviz.org Graphviz]) | ||
* Some redundancy with Dozuki -> Can this information be extracted in an automated way from Dozuki? Or vice-versa? Discuss with dozuki developers? | * Some redundancy with Dozuki -> Can this information be extracted in an automated way from Dozuki? Or vice-versa? Discuss with dozuki developers? | ||
Revision as of 14:30, 10 February 2015
Overview
An index of all raw material, parts, and assemblies in the Fabrication Diagram method of collaborative production.
The term "master index" has been used for years, although no central index is known.
Proposal (February 2015)
A central database is proposed in accordance with Naming and Identification.
The current proposal consists of a simple spreadsheet with three tabs:
- Module Index: List of all modules with unique, unchangeable moduleID. Provides lookup for the other lists.
- Version Index: List of all versions with meta info such as date, person, description. (Similar to git commits.)
- Dependency Index: List all dependencies of the dependency tree (see below)
Discussion
Pro:
- Central point of reference for all modules
- Machine-readable -> can be further improved by using some open standard like xml with nice frontend
- More structured than Dozuki
- Better overview than with Dozuki -> or can Dozuki be improved to provide this sort of meta data and dependency graph?
Cons:
- No visual rendering -> Can be solved by adding nice frontend (e.g. Dependency graph using Graphviz)
- Some redundancy with Dozuki -> Can this information be extracted in an automated way from Dozuki? Or vice-versa? Discuss with dozuki developers?