Method and apparatus for implementing a corporate directory and service center

• US 7,979,433 B2
• Filed: 02/21/2008
• Issued: 07/12/2011
• Est. Priority Date: 08/23/1999
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ramamurthy, Prakash, Joshi, Vrinda S., Vora, Kumar, Stone, Adam C., Moatazedi, Shahram, Swadi, Praveen R., Shandony, Michael J., Raman, Rajesh
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US12/034,784
• Publication Number:
  US 20080147657A1
• Time in Patent Office: 1,237 Days
• Field of Search: 707/802, 707/736
• US Class Current: 707/736
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/947 Human resources
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A method and apparatus for implementing a corporate directory and service center is described. The method includes and the apparatus performs querying for common characteristics, displaying information in a varied manner of displays and switching between the manners of displaying, maintaining data integrity and changing data, and defining types of data with forms of display or treatments for handling the data. The method may be embodied in various media as instructions which a machine may execute to perform the method.

Claims

1. A method of searching a plurality of data entries, each data entry having a plurality of attributes comprising:

providing a common characteristic;

accessing the plurality of data entries using lightweight directory access protocol (“

LDAP”

);

searching the plurality of data entries for the common characteristic; and

organizing the data entries which have the common characteristic of the plurality of data entries.

2. A method of managing a plurality of data entries, comprising:

receiving, at a computer, a first request for a change in a data entry of said plurality of data entries;

accessing said data entry using lightweight directory access protocol (“

LDAP”

);

automatically generating, at the computer, a set of tickets in response to said first request, said tickets include tasks that are prerequisites to completing said change in said data entry; and

monitoring status of said tasks.

3. A method according to claim 2, wherein:

said tickets indicate an associated task to be accomplished and an entity which needs to accomplish said associated task.

4. A method according to claim 2, wherein:

said set of tickets includes a first ticket and a second ticket dependent on said first ticket.

5. A method according to claim 2, wherein:

said tickets indicate a service, a create date, a due date, comments, identification and status.

6. A method according to claim 2, wherein:

said tickets include unique identifiers.

7. A method according to claim 2, wherein:

said set of tickets includes a first ticket owned by a first entity and a second ticket owned by a second entity.

8. A method according to claim 2, wherein:

said change in said data entry includes adding said data entry to said plurality of data entries.

9. A method according to claim 2, wherein:

said change in said data entry includes modifying said data entry.

10. A method according to claim 2, wherein:

said plurality of data entries store information about organizational resources; and

said change in said data entry includes adding, modifying or deleting information about a particular organizational resource.

11. A method according to claim 2, wherein:

said plurality of data entries include information in a directory.

12. A method according to claim 2, further comprising:

completing fulfillment of said first request when said tasks have been completed.

13. A method according to claim 2, wherein:

said tasks do not include said change in said data entry.

14. A method according to claim 2, wherein:

said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry.

15. A method according to claim 2, wherein:

said tasks are assigned to be performed by different entities.

16. A method according to claim 2, wherein:

said plurality of data entries store information about organizational resources; and

said first request is to add a new person to said information about organizational resources.

17. A method according to claim 16, wherein:

said tasks include entering information about said new person.

18. A method according to claim 16, wherein:

said tasks include notification tasks.

19. A method according to claim 16, wherein:

one of said tickets requests an approval.

20. A method according to claim 2, wherein:

one of said tickets requests an approval.

21. A method according to claim 20, further comprising:

generating one or more additional tickets in response to said approval.

22. A method according to claim 2, wherein:

one of said tickets requests approval of said change.

23. A method according to claim 2, wherein:

said tasks are assigned owners; and

said step of monitoring includes a particular owner accessing a set of task assigned to that particular owner.

24. A method according to claim 2, wherein:

said tasks are assigned owners; and

said step of generating includes notifying said owners.

25. A method according to claim 2, wherein:

said tasks are assigned owners;

said step of generating includes notifying said owners by electronic mail.

26. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors, said processor readable code comprising:

code for automatically generating a set of tickets in response to a first request for a change in a data entry of said plurality of data entries, said tickets include tasks that are prerequisites to completing said change in said data entry;

code for accessing said data entry using lightweight directory access protocol (“

LDAP”

); and

code for completing fulfillment of said first request when said tasks have been completed.

27. One or more processor readable storage devices according to claim 26, wherein:

said set of tickets includes a first ticket and a second ticket dependent on said first ticket.

28. One or more processor readable storage devices according to claim 26, wherein:

said set of tickets includes a first ticket owned by a first entity and a second ticket owned by a second entity.

29. One or more processor readable storage devices according to claim 26, wherein:

said plurality of data entries store information about organizational resources; and

said change in said data entry includes adding, modifying or deleting information about a particular organizational resource.

30. One or more processor readable storage devices according to claim 26, wherein:

said tasks do not include said change in said data entry.

31. One or more processor readable storage devices according to claim 26, wherein:

said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry.

32. One or more processor readable storage devices according to claim 26, wherein:

one of said tickets requests an approval.

33. A method of managing a plurality of data entries comprising:

receiving, at a computer, a first request for a change in a data entry of said plurality of data entries;

accessing said data entry using lightweight directory access protocol (“

LDAP”

);

in response to said receiving, automatically generating, at the computer, a set of one or more tasks that do not make said change in said data entry, said tasks are prerequisites to completing said change in said data entry; and

completing fulfillment of said first request when said tasks have been completed.

34. A method according to claim 33, wherein:

said set of tasks includes a first task and a second task dependent on said first task.

35. A method according to claim 33, wherein:

said set of tasks includes a first task owned by a first entity and a second tick task et owned by a second entity.

36. A method according to claim 33, wherein:

said plurality of data entries store information about organizational resources; and

said change in said data entry includes adding, modifying or deleting information about a particular organizational resource.

37. A method according to claim 33, wherein:

said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry.

38. A method according to claim 33, wherein:

said plurality of data entries store information about organizational resources; and

said first request is to add a new person to said information about organizational resources.

39. A method according to claim 33, wherein:

one of said tasks is to provide an approval.

40. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors, said processor readable code comprising:

in response to receiving a first request for a change in a data entry of said plurality of data entries, code for generating a set of one or more tasks that do not make said change in said data entry, said tasks are prerequisites to completing said change in said data entry; and

code for accessing said data entry using lightweight directory access protocol (“

LDAP”

);

code for completing fulfillment of said first request when said tasks have been completed.

41. One or more processor readable storage devices according to claim 40, wherein:

said plurality of data entries store information about organizational resources; and

said first request is to add a new person to said information about organizational resources.

42. One or more processor readable storage devices according to claim 40, wherein:

said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry.

43. One or more processor readable storage devices according to claim 40, wherein:

one of said tasks is to provide an approval.

44. An apparatus for managing a plurality of data entries, comprising:

one or more processors; and

one or more storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming said one or more processors, wherein said processor readable code comprises;

code for receiving a first request for a change in a data entry of said plurality of data entries,

code for accessing said data entry using lightweight directory access protocol (“

LDAP”

),

in response to said receiving, code for automatically generating a set of one or more tasks that do not make said change in said data entry, said tasks are prerequisites to completing said change in said data entry, and

code for completing fulfillment of said first request when said tasks have been completed.

45. A method of managing a plurality of data entries comprising:

receiving, at a computer, a first request for a change in a data entry of said plurality of data entries;

in response to said receiving, automatically generating, at the computer, a set of one or more tasks that are to be performed as a prerequisite to completing said change in said data entry, said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry;

accessing said data entry using lightweight directory access protocol (“

LDAP”

); and

monitoring status of said one or more tasks.

46. A method according to claim 45, wherein:

said set of tasks includes a first task and a second task dependent on said first task.

47. A method according to claim 45, wherein:

said set of tasks includes a first task owned by a first entity and a second task owned by a second entity.

48. A method according to claim 45, wherein:

said plurality of data entries store information about organizational resources; and

said change in said data entry includes adding, modifying or deleting information about an organizational resource.

49. A method according to claim 45, wherein:

said plurality of data entries store information about organizational resources; and

said first request is to add a new person to said information about organizational resources.

50. A method according to claim 45, wherein:

one of said tasks is to provide an approval.

51. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors, said processor readable code comprising:

in response to receiving a first request for a change in a data entry of the plurality of data entries, code for generating a set of one or more tasks that are a prerequisite to completing said change in said data entry, said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry;

code for accessing said data entry using lightweight directory access protocol (“

LDAP”

); and

code for completing said change subsequent to performing said tasks.

52. One or more processor readable storage devices according to claim 51, wherein:

said set of tasks includes a first task and a second task dependent on said first task.

53. One or more processor readable storage devices according to claim 51, wherein:

said plurality of data entries store information about organizational resources; and

said first request is to add a new person to said information about organizational resources.

54. An apparatus for managing a plurality of data entries, comprising:

one or more processors; and

one or more storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming said one or more processors, wherein said processor readable code comprises;

code for receiving a first request for a change in a data entry of a plurality of data entries,

code for accessing said data entry using lightweight directory access protocol (“

LDAP”

),

in response to said first request, code for generating a set of one or more tasks that are to be performed as a prerequisite to completing said change in said data entry, said tasks are assigned to be performed by one or more entities other than an entity making said change in said data entry,

code for monitoring status of said one or more tasks, and

code for completing said change in said data entry.