Skip to content

[Cookbook] CSV formats, attribute data structure #298

Open
@a2xchip

Description

@a2xchip

I'm requesting enhancement

Story

Attribute data structure page was introduced and updated recently by @fitn and merged in branches by @juliensnz

As @jmleroux mentioned during commit conversation: it was created for current stable 1.5 branch.

I

After merging PR we got the same page version for master. But as I mentioned during conversation its information must be updated according to pim-community-dev master branch to correspond to the structure we have i.e.:

  • type
  • allowed_extensions
  • available_locales
  • code
  • date_max
  • date_min
  • decimals_allowed
  • default_metric_unit
  • group
  • label-locale
  • localizable
  • max_characters
  • max_file_size
  • metric_family
  • minimum_input_length
  • negative_allowed
  • number_max
  • number_min
  • reference_data_name
  • scopable
  • unique
  • useable_as_grid_filter
  • validation_regexp
  • validation_rule
  • wysiwyg_enabled

II

Currently I'm trying to finish Product information page see #295 and issue #267 , that describes how all product related data is kept and organized in PIM. And there is topic about product attribute types and table describing native attribute types, and as i see now this table is pretty close to that on Attribute data structure page. To make documentation clearer we need to avoid duplication and decide where is the place for attributes native types listing table. Anyway I don't think that page describing attribute data structure must contain information about attribute types at least in that part related to next PIM version tech doc, and the reason it is located there is because there was no dedicated page describing attribute types.

Now as i found updated Import/Export documentation in master I will update my PR for Product Information page with note-references to import/export pages apart for each product related entity described.

Task

  • Update Attribute data structure page on master to the actual master structure as in issue description above;
  • Avoid content duplication: to decide where is the best place for attribute types listing table and remove duplication.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions