Bug 1466134 - Merge 3 sections about adding/modifying/deleting entries/attributes
Summary: Merge 3 sections about adding/modifying/deleting entries/attributes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide
Version: 10.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-29 07:15 UTC by Marc Muehlfeld
Modified: 2017-08-10 07:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 07:36:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marc Muehlfeld 2017-06-29 07:15:37 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/creating_directory_entries-managing_entries_from_the_command_line


Section Number and Name: 
3.2. Managing Entries from the Command Line
3.3. Using LDIF Update Statements to Create or Modify Entries
3.4. Renaming and Moving Entries


Describe the issue: 
These 3 sections have a very unclear structure and are crosslinked. Merging the sections would allow us to have all the information about one operation in one place. Additionally we could remove unnecessary and duplicate content.


Suggestions for improvement:
* We should merge the three sections. 3.2 only tells the command and then refers to the subsections in 3.3 for the details. Additionally 3.3.2 is only an introduction and refers for the details to 3.4.
* Remove the tables with ldapadd|ldapmodify|ldapdelete parameter descriptions. They are duplicative and we can refer to the man pages or describe them in one place (e. g. at the beginning of the section).
* The LDIF examples should be shorter. It should be clear when having 1 or 2 examples in the file. We don't need to add 10 entries to show how it works. :-)

Comment 2 Marc Muehlfeld 2017-08-10 07:36:48 UTC
The update is now available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.