Digital Art Zone

Whoops, all gone.

Whoops, all gone.

Whoops, all gone.

A couple of quick comments from my first read-through—I’ll try to go through it more carefully later.

1) I don’t like having a separate category for Earrings—they should just be accessories for Ears.  Similarly, Rings should just go under Hands, or if they must have their own category, then a category for Fingers would make more sense.

2) I don’t think you should have separate categories for PZ2 or MC6 under Materials—it should be irrelevant for the purposes of metadata whether the actual files are in a folder with .pz2’s, .mc6’s, or in a DS-format content folder.

Whoops, all gone.

cridgit - 11 September 2012 04:41 PM

The reason I have put .DS, .PZ2 and .MC6 in separate folders is that DAZ Studio shows all three and if they are all in the same folder I’d only know which one to use based on the extension (which would have to be set to visible in DAZ Studio). If DAZ Studio would recognize these three as the same and only display one of them, we wouldn’t need to do this. I know this happens already for DS and PZ2 in the same folder but often these files are in different folders and the user would need to rearrange the files (which I think is a bad idea for 99% of the community).

I don’t mind putting them all in the same folder, but we need to be aware of the implication. What do other people think?

Cheers

Ah, okay, makes sense.  I always install to dummy folders and only keep the sets I need, but you DO need some way to indicate the ‘preferred’ set if you keep them all.

I understand, If I want to change root category grouping much,it cause more problems.
(so I thinki it is better the root grouping is more strictly divided,  obj and other files,
we can not talk about obj and many preset files at same time)

Now I think,,  I can talk about how assigned files to the category which decided already,
or about new child category.

and my interesting is almost about wardrobe and accessory ,attachemet categorize.
they decide how my character look.

these items are in category about character appearance.

and the most important things for me to categorize wardlobes,
is how cordinate figure easily from many suitable choise.
in other word how cordinate and cover parts of body is first decided.

each innner parts>> outer parts>> then apply accessory.

my suggesiton.

Glove should be child of wardlove category.

if glove is accessory has sense in real life categorize, but I think it is better in wardlove category.
because I cordinate as body parts, first I set almost every item which coverd body.
Gloves has many type, but it covered most of hands and arms part.

I think accessory category should be small item and it can easily changing as you feel.
rings, bungles, or neck,,

but gloves decide about how your arms parts looks. if you change it, the looks
change significantly.

and it covered a most of hands or arms.

eg abiout game character, glove is one parts of costume.
of course the glove category need child category full arms or hands.

I want categorize how I can easily cordinate.

and one more thing,,,

there is scene and sets category for each props .
I think everytime, why there is not full-set for wardlobe category?

that means it is category for full cordinate sets of the products.
if you click the pointer file,  it load every items for cordinate figure of the products.
now we have sub sets files.so if vendor make the sub sets file for their products,
I think we can load it at once.

it is pity that I can not fit-to ore parent every items when I load sub sets now,
but I think it seems easy to auto-fit some items and parent items at once
by other preset files (or script).

so if bendor provide sub sets for all items, and for auto-fit files,
we wil categorize them in smart contents.
If I choose products sets and one click icon, which can load all items of the products,
it seems great,,,

edited
(now I find the way to make sub-sets with auto-fit!!)

Whoops, all gone.

Thank you ^^

then, I understand I can make category freely, but if every user change category as they like,
vendor products information and their categorize items,seems difficutl I think,,
(I hope, not so tweak meta-data or categorize by myself^^;
if the products was good categorized with rule,, and have right
meta-data,
and without no bug,,)

before I hope layer looked products series.

that need strict categorize and the category decide maybe basic size or length or thickness of the each item.

I hope if I choose one category, I can change more freely
without big poke through, that is like character making in 3D games.

I can freely change and choose items if I keep category,,
now if I change underwear,, it may cause big poke through,,,

so I think if user so many change category by himself, it can not decide
guide line for layer look,,
(though it is only one who hope the layer look costume series,,)

but I thought if vendor make each items in the size, with guideline of categorize for layer look products series,
if DAZ can make new line up,,,,

and I made many products full costume sets, today,,why I do not hink that before^^;
iti is so useful!!!

yes,, I make category 1 under the wardlobe, as you say! of course!
and 2 under the my category> fullset

(I made it by subsets,, but it is same as sciene,, in ds 4.5)

and make compatibility with genesis,, so I can find it so easy,,

next I made reference in the original product , and make new comatibility base
under the product base then declare it as fullsets,
it seems goes well , I can serch my full preset in “product” too,

but some case the file name disappear in content database editor. why?
I am a little scared so I removed reference from the products.

kitakoredaz - 12 September 2012 07:29 AM

but some case the file name disappear in content database editor. why?
I am a little scared so I removed reference from the products.

Can you post a screenshot before/after it disappeared, so I can see what is going on?

sorry out of topic ^^; clear and delete image,,

I hope more people talk about meta-data ,how categorize is tbest for user.

==============
it seems better do not use this topic for my question,, (more important for another user
to talk about meta-data categorize,,)

I just stuck picture when the name has gone,,(before)
and change name and try again (once I closed ds,,) corrected

Hi Guys,

DAZ now has an official standard for metadata and we will be releasing all products, as well as updating current products to this standard.  We would like the community to be aware of this and I will be uploading documentation this week for you.  We have done extensive testing on the layout and categorizations and feel that this will allow us to put out metadata that is acceptable to most users.  Those who wish to categorize differently in their own database will also have documents teaching them how to do this.  Within the next day or so, I will be posting a link here for your reference.  In the meantime, you can see the Categories and the Content Types here:

Default Categories
Content Types

I am sure there may be a few things we have forgotten or left off, and can add these in as needed, but after working for over a year to standardize this, we will not be changing the base format.  We don’t have the time or resources to change the store content multiple times.    While I know these will not suit everyone, they have proven to be the most acceptable and intuitive to our test groups.

I will be glad to work with anyone doing metadata for the community.  I have noticed several people working on things and we appreciate it.  It is my goal to get the tutorial we have online ASAP (Thanks to one our community members for helping with this), and this will allow anyone to learn the ins and outs of Metadata and how and why things get set as they do.    There are actually several technical reasons behind typing and categorizing content to ensure a well organized database and metadata that works. 

As soon as I have the link live, I will post it in here.  Thanks again for all your interest and help so far.  It is very much appreciated.

Kat

DAZ_KatBriggs - 12 September 2012 10:28 AM

Hi Guys,

DAZ now has an official standard for metadata and we will be releasing all products, as well as updating current products to this standard.  We would like the community to be aware of this and I will be uploading documentation this week for you.

This is very interesting news. Especially having official information and instructions available for everyone will help giving a better understanding why things are done the way they are.

- - -

Since the products are being updated I believe it is also very important that detailed instructions about those topics closely related to metadata are included:

- What is considered “User Data”?
- What is considered as the “Local Database”?
- What is considered as the “Product Database”?

- What is the exact functionality of the “Keep user data” checkbox that can now be found when importing metadata.

- Which data is saved in the local database and which in the product database.

- How are the “local database”, “the product database” and the “User Data” linked together?

I have posted more detailed question in another thread that still have not been answered by anyone:

http://www.daz3d.com/forums/viewthread/6123/#80081

A complete understanding of the process needs to be there to be able to answer questions like:

How is the checkbox “synch local and product database” in the content DB editor linked to the checkbox “Keep user Data” when new metadata is being imported.

Are there options to declare metadata on a product level as user data? Is there a toggle off or on switch somewhere on a product level that I can say keep the changes I made to this product put please replace the changes for that product with the new updates the DAZ team made?

- - -

Can someone of the DAZ metadata team please have a look at them to see if they are covered in the guide you plan to make available.

I hope you guide will cover this topics. If not I hope it can be updated to cover those questions.

Only if the community gets a a complete understanding how metadata is tied into DS4.5 it will be able to use it efficiently.

I’ll make sure those get answered in the document.  My team is working on the metadata updates, so I am involved in the whole process as well. 

Kat

Whoops, all gone.