You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the plan as described is just about perfect.
You can alleviate the broken import file a bit by providing a csv code snippet of the new formats for the old structure. That way I can just copy and paste it into my old file overwriting the old headers. After that's sorted, I can add in other headers, move columns around, etc
I've read through the proposal and I think it looks great. Because I have So. Much. Stuff. to add into HomeBox, I haven't gotten started yet because I haven't felt the current format has the robustness it needs.
I started building my home inventory in the previous import format - by the time I actually got to a point where it could be uploaded, you overhauled it!
The new import schema is MUCH better. Thank you for such an awesome project.
Problem
The current import format is brittle and is not extendable beyond what is concretely supported.
Proposed Changes
Predefined Column Headers
Instead of relying on ordered imports use a
.
separated syntax for HomeBox values. SoHB.name
would map to the Name field for the item.This has numerous benefits
HB.field.<name>
which would eliminate the need for another syntax like tags where we use;
separated entries.Implementation Notes
HB.warrant_expires
replacesWarranty Expires
HB.field.<name>
will split on the second . and take whatever left as the field name soHB.field.Amazon URL
would map toAmazon URL
Add Parent Item Support
Add
HB.parentItem
column that takes a ImportRef to the parent item type. Child items will be linked to parent items.Add Support for Nested locations
The
HB.location
column would now support a/
separated syntax allowing for specifying nested locations.Example:
Storage Unit 117 / Left Shelve / Row 2 / Box A
Would create 4 locationsThe item would then use
Box A
the last location as it's location.Other Considerations
The text was updated successfully, but these errors were encountered: