Article database

Question

Hello,
I want to develop an article management (users can upload a pdf and input informations about the resource like author, category, year, publisher, ... ).
I have a resource and for this resource several customer properties like author, category, year,... I have posted before and one of the replies was to watch the tutorial for the bulleting board. I did it and got an overview about the possibilites. Unfortunately I don't get the whole picture and there are some informations not fitting in my brain. Maybe someone can help me how to realize the steps:
- First of all I would like to create my customer properties for a resource. The path should be /documents/articles. The attributes author, category (technical documentation, summary, ...), year, tags (web dynpro abap, web dynpro java, ... ).
What do I need to see this attributes in an dialog to upload an resource.  The properties in the bulletin board tutorial are not associated with a resource. There I don't get the point with the several steps I have do in order to see the properties. Can I use the default namespace (like it is in the bulletin board tutorial) or should I create an own? Is there somewhere a step by step guide?
- To a resource could belong another resource (like a practice). How can I associate the main resource to other resources? If there is no possibility I would just put some fields as resource properties for the urls to the resource.
Sorry for asking about this stuff again, but like I told. I don't get the point with all this.
Thanks, Vanessa

Answer 1

Hi Vanessa, I haven't checked the tutorial you mentioned so I'm not sure what possibilities
you've seen so far, anyways here goes my solution:
First thing to do is create the properties (author, year, document type, etc). Have a special
attention to the following properties:
Folder Validity Patterns: you wanna classify documents, so it's unlikely any of your properties
will apply to folders, if that's the case leave this field blank (!! default value is /** so change it)
Document Validity Patterns: make this something like /documents/articles/** so every document
below this path will have the metadata you're creating
That should answer the resource association with property question
It's up to you to use a default namespace or a create one, it's good to have a custom namespace so you
have your customers' metadata organized, also avoid conflicting names (eg: author already exists
in default namespace)
By now it should be already possible to set the properties when uploading documents, if you
used default configuration the properties should be on the Miscellaneous tab, depending on your
requirements checking the Mandatory option on the properties would make sure no document is
uploaded without proper definitions.
Having your own tab, groups, and friendly labels with tooltips and all requires more effort, please
refer to the following document to in depth details regarding propreties:
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/de31ec90-0201-0010-be95-f501d25027a8
It's not possible to bind a document to another on stadard way, i'd suggest to have a property like
"see also" or "related documents" where you put a link to document (There is a See Also
KM command but I never used it so dunno how it works)
hope it helps,
Rafael