JP6367774B2 - Item management program, item management method and item management system - Google Patents

Description

  The present invention relates to an item management program, an item management method, and an item management system for managing creation of items used in an application.

  In system development, etc. consisting of tasks related to each other, it may be implemented by a project in which multiple organizations participate. A project management system that visually expresses the progress of the project has been studied (for example, see Patent Document 1). In the project management system described in this document, a reference document that is referred to when a project is executed and a document management database that manages an output document to be created are used. Furthermore, when planning a project, an empty entity of an output document to be created in each process of the project is registered in the document management database. The registered empty entity and link information to the reference document are registered in association with the process, and the progress of the project is managed. This project management system displays, for each process, a process name, a title bar that matches the schedule length of the process, and a progress bar that indicates the progress of the process, in correspondence with each other. Visually output the progress status that is in charge of.

  In addition, today, a technique for providing various games has been studied (see, for example, Patent Document 2). In the technique described in this document, a plurality of unfinished items up to a completed item are prepared instead of a completed item, and the plurality of unfinished items are presented to the user. Motivation is improved, thereby reducing the user withdrawal rate of the card game.

JP 2003-141320 A Japanese Patent No. 5401627

  As described above, many items are used in applications such as games. Furthermore, the form may change due to the evolution of the item. When developing such an application, delays in the preparation of some items can affect the overall development. Therefore, it is necessary to accurately manage the creation status of images and the like of each item. Also, similar items and items in evolutionary form are related to each other and need to be created in consideration of the balance of each item.

  The present invention has been made in view of the above-described problems, and an object thereof is an item management program, an item management method, and an item management system for efficiently and accurately managing creation of a plurality of items used for an application. Is to provide.

  (1) An item management system that solves the above-described problem includes, for each project that creates a plurality of items, according to an item creation step, an item image of an item associated with a search key, a storage unit that records a posting date and time, A control unit connected to the client terminal, wherein the control unit obtains information and a search key relating to a project for displaying a list of item images from the client terminal, and associates the search key with an item belonging to the project The obtained item image is acquired from the storage unit, a display screen for displaying a list of images with the latest posting date and time among the item images is generated, and the display screen is output to the client terminal. This makes it easy to grasp item images belonging to the same aggregate.

  Furthermore, even when a plurality of item images are registered, it becomes easy to grasp the latest state.

  (2) In the item management system that solves the above problem, the item image is associated with an item code indicating an aggregate and a viewing authority, and the control unit acquires information on the item code from the client terminal, When the item image associated with the item code is acquired from the storage unit and the browsing authority of the client terminal is the first authority, a display screen that displays the creator together with the acquired item image is generated, When the browsing authority of the client terminal is the second authority, a display screen that displays the acquired item image without displaying the creator is generated.
  (3) In the item management system that solves the above problem, the item image is associated with an item creation step for each project for creating a plurality of items, and the storage unit indicates the degree of progress of the creation step. Step information is recorded, the control unit obtains information about the project from the client terminal, specifies an item image belonging to the project as a parent item, and associates it with the step of creating the parent item.
Based on the step information, a screen showing the progress of the child item and the progress of the parent item that integrates the progress of the child item is generated.

( 4 ) In the item management system, it is preferable to specify an evolution form for each item and associate items with different evolution forms. As a result, images can be listed in consideration of evolutionary forms.

  According to the present invention, creation of a plurality of items used for an application can be managed efficiently and accurately.

The system schematic of this embodiment. Explanatory drawing of the data used by this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of other embodiment. Explanatory drawing of the output screen of other embodiment. Explanatory drawing of the output screen of other embodiment.

Hereinafter, an embodiment of the item management method will be described with reference to FIGS.
As shown in FIG. 1, in this embodiment, it is assumed that an item used for an application is created using a plurality of client terminals 10 and a management server 20 connected via a network such as the Internet. Here, an item is a unit for managing deliverables, and includes, for example, a plurality of characters used for game applications. In this case, an administrator, a developer, and a creator are involved in creating an item.

  The administrator belongs to an application management company, and creates an application concept, manages the entire application, performs operations, and confirms quality. The developer belongs to an application development company (developer), and creates an item used for the application together with the administrator. The creator (designer) belongs to the content creation company, and creates an item image (asset) of the created item together with the developer. When creating an item image, for example, a rough image, line drawing, coloring, finishing, inspection, delivery, and the like are performed. In each step, the creator creates an item image (check file) and posts it to the management server 20. Then, the developer confirms the posted check file using the management server 20 and feeds back the confirmation result. In this feedback, the developer makes a determination of “OK (approval)” or “retake (redo)”. The creator modifies the item if necessary based on the developer's feedback. Note that the roles of administrator and developer can be changed according to the situation. For example, when an administrator produces an application in-house, it has a role as a developer.

  In order to create an item, an administrator, a developer, and a creator use each client terminal 10. The client terminal 10 is a computer terminal used by each user (administrator, developer, creator) to access the management server 20. The client terminal 10 includes a communication unit, an input unit, and an output unit (such as a touch panel display). Furthermore, the client terminal 10 includes a control unit including a CPU, a RAM, a ROM, and the like. In the present embodiment, each client terminal 10 includes a browser program, and accesses the management server 20 using a browser activated by this program.

  The management server 20 is a server computer that supports application development. In the present embodiment, creation of game application items is supported. The management server 20 includes a control unit 21 including a CPU, a RAM, and a ROM, an authority information storage unit 22, an account information storage unit 23, an item management information storage unit 24, and an image storage unit 25. The control unit 21 functions as an authority management unit 211, an item management unit 212, a display control unit 213, and a history display unit 214 by executing a management program.

The authority management unit 211 specifies an access user and executes a process for specifying the authority of the user.
The item management unit 212 executes processing for managing an item creation process used for an application.

The display control unit 213 executes various output management processes related to the item image.
The history display unit 214 executes a process of changing and outputting the item image based on the item image creation history.

  In the authority information storage unit 22, authority information relating to functions and authorities that can be used is recorded according to the attributes of each account. This authority information is recorded when the authority is registered. In this authority information, data relating to affiliation and authority is recorded.

In the affiliation data area, information for identifying the affiliation (in this embodiment, administrator, developer, creator) is recorded.
In the authority data area, information on functions and authorities that can be used in each attribute is recorded. In the present embodiment, the administrator has authority to create and delete items, edit items, post comments, post reference materials, and the like. Developers have authority to edit their own items, post comments, and post reference materials. The creator has the authority to edit their own items, post comments, post reference materials, post file checks, and deliver files.

  In the account information storage unit 23, account information related to a user involved in creating an item is recorded. This user information is recorded when a user is registered. In the account information, data relating to an account ID, account attributes, and contact information is recorded.

Data relating to an identifier for identifying each user is recorded in the account ID data area.
In the account attribute data area, data relating to an identifier for specifying the affiliation (management company, development company, creation company) to which the user belongs is recorded.
In the contact data area, data relating to the contact information of the user is recorded. In this embodiment, an e-mail address is used as a contact address.

  The item management information storage unit 24 records item management information for managing each item. This item management information is registered when an item to be created is determined, and is updated according to the progress of item creation.

  The item management information will be described with reference to FIG. In item management information, project information D10 is associated with company information D01. In the company information D01, data relating to an identifier for specifying a development company that creates an application is recorded. In the project information D10, data relating to an identifier (here, a title) for specifying an application created by the development company is recorded.

  The project information D10 is associated with a plurality of custom field information D15. In the custom field information D15, various items (for example, character attributes, rarity, etc.) of items used in this project can be arbitrarily set. Here, the character attribute is a parameter relating to the property to which the character belongs, and “fire”, “water”, “darkness”, “light” and the like are set. Based on this character attribute, compatibility with the opponent is determined. The rarity is a parameter representing the rank (for example, scarcity value) of the item. For example, when the appearance rate of the character is low, the rare degree is increased.

  Category information D20 is associated with the project information D10. The category information D20 is information for specifying a group for grouping items. The category information D20 includes information on the person in charge and contact information of the management company, the person in charge and contact information of the creation company, and the person in charge of the development company.

  Furthermore, the information regarding the browsing authority in the person in charge of a preparation company is included. This browsing authority is information for determining the presence or absence of an item and the availability of browsing of item information among other creators in charge of the category. The browsing authority includes a normal mode, a name hiding mode, and a non-display mode. In the normal mode, the names and items of all creators are displayed. In the name concealment mode, items of all creators are displayed, but names of other creators are concealed. By this name concealment mode, images of different creators can be confirmed, and consistency such as style can be achieved. On the other hand, there is a merit that personal information is not known to other creators. In the non-display mode, only the company items are displayed.

Furthermore, the category information D20 includes a notification setting for each person in charge. This notification setting is information for determining whether or not notification is necessary when a comment or image is posted.
Group information D30 is associated with category information D20. In the group information D30, information on the step group used for this category is recorded. The step group is information for specifying a process when creating an item. For example, it is possible to specify a step group including each step of “not started, rough drawing, line drawing, coloring, finishing, delivery” in item creation.

Item information D40 is associated with this group information D30.
Item information D40 includes information related to item ID, number, evolution level, character name, and memo. In the present embodiment, each item (for example, a character) is identified based on an item code in which “item ID” and “number” are combined. Furthermore, the transition of the character is identified based on the “evolution level” in the set of “item ID” and “number”. This evolution level is originally the same character as in the first level, the second level, and the third level, but an identifier indicating the degree of evolution is recorded. As the level of evolution increases, character growth (transition from children to adults, etc.), various parameters (attack, defense, and weapons) related to battles are enhanced, character images and background images are enriched (multicolor, depth, A glossy color scheme) is performed. When various items are set in the custom field information D15, information corresponding to these items is recorded.

Ball information D50, comment information D60, image information D70, status information D80, and step information D90 are associated with item information D40.
In the ball information D50, information (account ID) for specifying the current worker is recorded for this item.

  In the comment information D60, information related to comments posted regarding items is recorded. The comment information D60 includes information related to the posting ID, the step at the time of posting, the destination, the comment content, the poster, and the posting date (registration date). In addition, a flag for identifying unsuccessful or already read is recorded for the destination. An unread flag is recorded at the time of posting, and a read flag is recorded when the destination user views a comment.

  In the image information D70, information related to an image posted regarding an item is recorded. In this image information D70, a posting ID, a step at the time of posting, an image type, a destination, an image ID, a poster, a posting date (registration date) are recorded. The image type includes “check file”, “reference image”, and “delivery file”. The check file is an image uploaded by the creator of the item, and is an image for receiving confirmation from the developer or administrator. The reference image is a file other than the check file, and includes, for example, an image used as a reference when creating an item. A delivery file is an image that has been completed for an item and delivered by the creator. The check file D71, the reference image D72, and the delivery file D73 are recorded in the image storage unit 25 described later.

  In the status information D80, information indicating the situation at each step of the item is recorded. In the present embodiment, a flag indicating any one of “working”, “OK”, and “retake” is recorded. “OK” and “Retake” are recorded according to the confirmation result of the confirmer.

  In the step information D90, information for specifying the current step in the step group set for each category is recorded. As steps, as described above, for example, unstarted, rough drawing, line drawing, coloring, finishing, delivery, etc. are recorded.

  Furthermore, each step information D90 is associated with schedule information D91 and priority information D92. In the schedule information D91, information regarding the start time, the time limit, and the progress rate of this step is recorded. In addition, in the priority information D92, information regarding the priority for this step is recorded.

  In the image storage unit 25, a check file D71, a reference image D72, and a delivery file D73 are recorded in association with the image ID of the image information D70.

(Item management process)
Next, the item management process will be described with reference to FIG. When creating an item, the administrator uses the client terminal 10 to access the management server 20.
In this case, the control unit 21 of the management server 20 executes a login process (step S100). Specifically, the authority management unit 211 of the control unit 21 acquires an account ID from the client terminal 10 and specifies an access user and affiliation using the account information storage unit 23. Next, the authority management unit 211 uses the authority information storage unit 22 to specify the authority according to the affiliation of the access user. Then, the authority management unit 211 outputs a login screen on the display of the client terminal 10.

  As shown in FIG. 6, the login screen 500 includes an upper area 500a and a side area 500b. The upper area 500a and the side area 500b are similarly displayed on each screen described later. The upper area 500a includes a ball number display 501 and a comment number display 502. The ball number display 501 displays the number of items that the user has the ball. In the comment number display 502, the number of comments that are addressed to this user and have not been browsed yet is displayed. In the side area 500b, an icon 503 for designating a title set as a person in charge by this user and an icon 504 for designating each development company are displayed. The login screen 500 includes a ball content display 505 and a comment content display 506. In the ball content display 505, the content related to the item for which the user's account ID is set is displayed in the ball information D50. In the comment content display 506, an outline of a comment in which the account ID of this user is a destination in the comment information D60 and an unread flag is recorded is displayed.

  Next, the control unit 21 of the management server 20 executes a title creation process (step S101). Specifically, in the case of an administrator who has the authority to create items, the authority management unit 211 allows title creation. When creating a title, the application development company is specified using the icon 504 on the login screen 500 and the title creation is instructed. In this case, the item management unit 212 outputs a title creation screen on the display of the client terminal 10.

  As shown in FIG. 7, the title creation screen 510 is provided with a title setting field 511 and a custom field setting field 512. Enter a title (project name) in the title setting field 511. Furthermore, in the custom field setting field 512, various items (for example, character attributes, rarity, etc.) for items belonging to the title are set. When the creation button is selected on the title creation screen 510, the item management unit 212 uses the item management information storage unit 24 to display the project information D10 including the title set in the title setting field 511 as the company information D01 of the development company. Record in association with. Further, the item management unit 212 records custom field information D15 including various items set in the custom field setting field 512 in association with the project information D10.

  Next, the control unit 21 of the management server 20 executes category creation processing (step S102). Specifically, the item management unit 212 outputs a category creation screen on the display of the client terminal 10.

  As shown in FIG. 8, the category creation screen 520 is provided with person-in-charge information setting fields 521 to 523 for registering information related to managers, creators, and developers. In the person-in-charge information setting field 521, the user identifier of the person in charge of the management company and the mail notification setting are registered. In the person-in-charge information setting column 522, the viewing authority of the creating company, the creating company, the user identifier of the person in charge, and the mail notification setting are registered. In the person-in-charge information setting field 523, the user identifier of the person in charge of the development company and the necessity of mail notification are registered. Further, a step group designation field 524 is provided on the category creation screen 520. When the creation button is selected on the category creation screen 520, the item management unit 212 stores the category information D20 including the person-in-charge information set in the person-in-charge information setting fields 521 to 523 in the item management information storage unit 24. Record in association with the project information D10. Furthermore, the item management unit 212 records group information D30 including information on the step group specified in the category creation screen 520 in the item management information storage unit 24.

  Next, the control part 21 of the management server 20 performs an item setting process (step S103). Specifically, the item management unit 212 outputs a title screen for item registration on the display of the client terminal 10. This item registration title screen is output when an item related to the title is not recorded in the item management information storage unit 24.

  As shown in FIG. 9, the title screen 530 is provided with a search condition column 531 for searching for items included in the title. Further, the title screen 530 is provided with an individual item registration button and a plurality of item registration buttons. When registering items individually one by one, the individual item registration button is selected. In this case, the item management unit 212 outputs an individual item creation screen on the display of the client terminal 10. On the other hand, when registering a plurality of items together, a multiple item registration button is selected. In this case, the item management unit 212 outputs a multiple item creation screen on the display of the client terminal 10.

  As shown in FIG. 10, the developer, title, and category are displayed on the individual item creation screen 540. The individual item creation screen 540 is provided with setting fields 541 for item ID, number, evolution level, and character name. Further, an item setting field 542 designated in the custom field is provided. In the individual item creation screen 540, a character attribute / rareness setting field 542 is provided based on the custom field information D15. In the step column 543, the first step of the step group is set based on the group information D30. In the ball field 544, the developer user identifier is displayed based on the category information D20.

  Further, as shown in FIG. 11, the developer, title, and category are displayed on the multiple item creation screen 550. The multi-item creation screen 550 is provided with setting fields 551 for item ID, serial number, and number of evolution levels. Here, a serial number setting field 551 is used to specify a number range consisting of consecutive numbers according to the number of types of items to be created.

  Next, the control unit 21 of the management server 20 executes an empty item generation process (step S104). Specifically, when the creation button is selected on the individual item creation screen 540 and the multiple item creation screen 550, the item management unit 212 generates item information D40 (empty item) in which no image is registered, and the item Records in the management information storage unit 24. Here, when the individual item creation screen 540 is used, the item management unit 212 generates one item information D40. On the other hand, when the multiple item creation screen 550 is used, the item management unit 212 generates the item information D40 by the number obtained by multiplying the number of consecutive numbers and the number of evolution levels. Then, the item management unit 212 outputs a title screen including a blank item (thumbnail display mode).

  As shown in FIG. 12, when the individual item creation screen 540 is used, the display control unit 213 of the control unit 21 outputs a title screen 560 displaying a thumbnail image of one item.

  In FIG. 13, when the multiple item creation screen 550 is used, the display control unit 213 of the control unit 21 outputs a title screen 570 displaying thumbnail images of a plurality of items. On this title screen 570, the number of items obtained by multiplying the number of serial numbers and the number of evolution levels is displayed. Here, on the title screen 570, item IDs and numbers (item codes) are common, and items having different evolution levels are grouped and displayed in a grouped manner so that they can be distinguished from other groups. This thumbnail display processing will be described later with reference to FIG. At the stage where an item is registered using the individual item creation screen 540 and the multiple item creation screen 550, no image is displayed because no item image is registered.

  Next, display of items recorded in the item management information storage unit 24 will be described. An administrator, a developer, and a creator access the management server 20 using the client terminal 10.

  In this case, the control unit 21 of the management server 20 executes a login process as in step S100 (step S105). In this case, on the login screen 500 shown in FIG. 6, an icon 503 of a title (project) in which the user is registered as a person in charge is displayed.

  Next, the control part 21 of the management server 20 performs a title selection process (step S106). Specifically, an icon 503 having a desired title is selected on the login screen 500. In this case, the display control unit 213 of the control unit 21 extracts an item associated with the selected title from the item management information storage unit 24. Furthermore, the display control unit 213 narrows down the extracted items based on the access authority of the access user. Specifically, in the case of an administrator or a developer, all extracted items are targeted. In the case of the creator, the item to be displayed is specified based on the viewing authority set in the category information D20. When the normal mode is set, all the extracted items are displayed. When the name concealment mode is set, the names of other creators are hidden. With this name concealment mode, there is an advantage that images of different creators and the like can be confirmed to achieve consistency of style and the like, and personal information is not known to other creators. In the non-display mode, other creator's items are hidden.

  Next, the control unit 21 of the management server 20 executes a thumbnail display process (step S107). In the thumbnail display process, thumbnails of items belonging to this title are displayed as a list. This thumbnail display processing will be described later with reference to FIG.

  Furthermore, when the list display button is selected on the title screen, the control unit 21 of the management server 20 executes list display processing (step S108). In this case, the display control unit 213 of the control unit 21 outputs the title screen in the list display mode to the display of the client terminal 10.

  As shown in FIG. 14, a search condition column 581 and an item list 582 are displayed on the title screen 580 in the list display mode. The search condition column 581 is used to narrow down items to be displayed among items included in the title. In addition, in the item list 582, information on items is displayed in a list as text. In this embodiment, the item code (item ID and number), step, status, character name, priority, time limit, person in charge name, and update date are displayed.

In the title screen 580, a selection box is displayed for each item.
When this selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes batch change support processing (step S109). In this case, the item management unit 212 of the control unit 21 outputs the item edit screen to the display of the client terminal 10. In this item editing screen, a plurality of items can be edited together. It is possible to use a batch change button displayed on the title screen. This item editing screen is provided with a setting field for editing a plurality of items collectively. This item editing screen is provided with setting fields for editing various information related to the item, for example, step, status, ball, time limit, priority, rare degree, character attribute, type, and the like. The item management unit 212 updates the ball information D50, status information D80, step information D90, and the like based on the contents set on the item edit screen.

  When the Gantt chart display button is selected on the title screen, the control unit 21 of the management server 20 executes a Gantt chart display process (step S110). In this case, the display control unit 213 of the control unit 21 outputs the Gantt chart display mode title screen to the display of the client terminal 10.

  As shown in FIG. 15, a search condition column 591 and a Gantt chart 592 are displayed on the title screen 590 in the Gantt chart display mode. The Gantt chart 592 displays the progress status and time limit of each step in each item. This Gantt chart creation process will be described later with reference to FIG.

  The item code displayed on the title screen 570 in the thumbnail display mode and the title screen 580 in the list display mode has a link to the item detail screen.

  When this link is selected, the control unit 21 of the management server 20 executes item detail display processing (step S111). Specifically, the display control unit 213 of the control unit 21 outputs an item detail screen to the display of the client terminal 10.

As shown in FIG. 16, the item detail screen 600 includes an item image display area 601, various item display areas 602, an evolution item display area 603, and a post list display area 604.
The display control unit 213 identifies the check file image having the latest posting date and outputs a thumbnail image to the item image display area 601.

  The item display area 602 displays information related to various items regarding this item. In the present embodiment, item code, evolution level, character name, character attribute, rarity, priority, status, step, deadline, memo, and the like are displayed. Furthermore, in the time limit, the start date and time limit of each step constituting the step group can be set.

  In the evolution item display area 603, thumbnail images of other evolution levels of this item are displayed. Here, the display control unit 213 identifies items of the same item code and check file images set with different evolution levels. Then, the display control unit 213 specifies a check file image having the latest posting date for each evolution level, and outputs a thumbnail image to the evolution item display area 603.

  In the posting list display area 604, a check file image and a reference image uploaded in each step included in the step group are displayed. Here, in the comment information D60 and the image information D70, the display control unit 213 rearranges the posting date and time in the newest order and outputs them to the posting list display area 604. In this case, the comment and image to which the same post ID is assigned are output in association with each other.

Furthermore, on the item detail screen 600, a return button 605, an edit button 606, a posting button 607, and a history display button 608 are displayed.
When the return button 605 is selected, the display control unit 213 returns to the link source screen.

  When the edit button 606 is selected, the control unit 21 of the management server 20 executes item edit processing (step S112). Specifically, the item management unit 212 of the control unit 21 outputs an item editing screen to the display of the client terminal 10. When this item edit screen is used, the item management unit 212 acquires item change information displayed on the item detail screen 600 and updates each registration information.

  When the posting button 607 is selected, the control unit 21 of the management server 20 executes item posting processing (step S113). The item management unit 212 of the control unit 21 outputs the item posting screen to the display of the client terminal 10.

  As shown in FIG. 17, the item posting screen 610 includes a step, status, and ball setting fields 611. Further, an upload button 612, a destination column 613, and a comment column 614 are displayed on the item posting screen 610. In the destination column 613, the account ID of the other party that notifies the upload is set. In the comment field 614, a message for the other party is entered.

  As shown in FIG. 18, when the upload button 612 is selected, a type setting field 615 for an image to be uploaded and a path setting field 616 in which the image is stored are displayed. In the image type setting column 615, one of a check file, a reference image, and a delivery file is selected.

  When the posting button is selected on the item posting screen 610, the item management unit 212 records the comment information D60 and the image information D70 assigned with the posting ID in the item management information storage unit 24 in association with the item information D40. To do. In this case, the logged-in contributor and the posting date and time are recorded in the comment information D60 and the image information D70. Furthermore, the item management unit 212 records the image (check file, reference image, delivery file) designated on the item posting screen 610 in the image storage unit 25 in association with the posting ID. Further, the item management unit 212 transmits the comment input in the comment column 614 to the destination set in the destination column 613.

  When the history display button 608 is selected, the control unit 21 of the management server 20 executes image history display processing (step S114). This process will be described later with reference to FIGS.

(Thumbnail display processing)
Next, the thumbnail display process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a group specifying process (step S201). Specifically, the display control unit 213 of the control unit 21 specifies an item in which the item ID to be output is set from the item management information storage unit 24. In this case, it is specified for each number and evolution level. Then, the display control unit 213 generates display columns for the number and the number of evolution levels on the title screen 530.

  Next, the control unit 21 of the management server 20 executes a color classification process for each group (step S202). Specifically, the display control unit 213 of the control unit 21 identifies display fields to which the same item code is assigned and different evolution levels are set as the same group. When the title screen 570 is adjacent to a display field belonging to another group, the display control unit 213 sets a color scheme different from that of the adjacent display field and is adjacent to a display field belonging to the same group. Sets the same color scheme as the adjacent display field. For example, it is assumed that display columns of item codes “100” to “102” each including a plurality of evolution levels are sequentially adjacent. In this case, each display column of the item code “100” is the first color (white), each display column of the item code “101” is the second color (blue), and each display column of the item code “100” is the first color. As in (white), blue and white are set in stripes for each display field. Thus, for example, when sorting is performed in the order of item codes, items belonging to the same group are displayed adjacently in the same color, and items in different adjacent groups are displayed in different colors. Can be easily grasped. In addition, when rearranged according to other conditions (for example, item update order), even if belonging to the same group, it is not always displayed adjacently, but the group can be grasped by the same color scheme. It becomes easy.

  Next, the control unit 21 of the management server 20 executes the latest post image acquisition process (step S203). Specifically, the display control unit 213 of the control unit 21 acquires a posted image with the latest posting date for each number and evolution level from the image storage unit 25. Then, the display control unit 213 generates a thumbnail of the acquired posted image.

Next, the control unit 21 of the management server 20 executes a thumbnail generation process (step S204). Specifically, the display control unit 213 of the control unit 21 outputs the generated thumbnail to each display column.
In FIG. 13, the same background color (shaded) is used for items in the same group, and a different background color is used for the other adjacent groups.

(Gantt chart creation process)
Next, the Gantt chart creation process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a parent item specifying process (step S301). Specifically, the display control unit 213 of the control unit 21 specifies item information D40 associated with this project (title). Then, items having common item IDs and different numbers and evolution levels are identified as parent items.

  Next, the control unit 21 of the management server 20 executes a process for specifying a child item of the parent item (step S302). Specifically, the display control unit 213 of the control unit 21 specifies step information D90 associated with the item information D40. Then, each step (in this embodiment, rough drawing, line drawing, coloring, finishing, delivery) is specified as a child item.

  Next, the control part 21 of the management server 20 performs the acquisition process of the progress information of a child item (step S303). Specifically, the display control unit 213 of the control unit 21 acquires schedule information D91 associated with the step information D90. Then, a bar corresponding to the progress information is displayed on the child item on the Gantt chart.

  Next, the control unit 21 of the management server 20 executes a progress display process of the parent-child item (step S304). Specifically, the display control unit 213 of the control unit 21 calculates the progress rate of the parent item by dividing the total progress rate value of the child items by the number of child items.

(Image history display processing)
Next, image history display processing will be described with reference to FIGS. The image history display process is executed when the history display button 608 is selected on the item detail screen 600.

  First, the control unit 21 of the management server 20 executes an item specifying process (step S401). Specifically, the history display unit 214 of the control unit 21 specifies an item for which history display is performed using the item ID and number on the item detail screen 600.

  Next, the control unit 21 of the management server 20 executes acquisition processing for all check images (step S402). Specifically, the history display unit 214 of the control unit 21 extracts all check files in which the item ID and number are set from the image storage unit 25. The history display unit 214 acquires an image (check image) of the called check file.

  Next, the control unit 21 of the management server 20 executes a slide display process (step S403). Specifically, the history display unit 214 of the control unit 21 arranges the check images in the upload order (posted date order). Then, the history display unit 214 outputs a history display screen on the display of the client terminal 10.

  As illustrated in FIG. 20, the history display screen 700 includes a page turning button 701 and an image display area 702. The history display unit 214 sequentially outputs check files to the image display area 702 in the order of creation steps on the history display screen in response to a change operation by selecting the page turning button 701. Here, according to the registration date, rough image (1), rough image (2), line image (1), line image (2), coloring,... Check files are recorded in image storage unit 25. If so, the check file images are output to the image display area 702 in the upload order. When the page turning button 701 is selected, it is desirable to change the original image and the next image within the time when the afterimage effect is visually generated. For example, since the time resolution of the human eye is about 50 ms to 100 ms, the change can be easily perceived by changing the time resolution shorter than this time.

According to the above embodiment, the following effects can be obtained.
(1) In the above embodiment, the control unit 21 of the management server 20 executes a title creation process (step S101). Here, the custom field information D15 is acquired. Thereby, common items such as character attributes can be set in the items included in the title.

  (2) In the above embodiment, the control unit 21 of the management server 20 executes category creation processing (step S102). Here, the person in charge information including the setting of the viewing authority is acquired, and the category information D20 including the person in charge information is recorded. Thereby, browsing authority can be efficiently set for every title according to a user.

  Further, group information D30 including information on the step group is recorded. Thereby, even when a plurality of items are included in the title, the item creation process can be determined in common.

  (3) In the above embodiment, the control unit 21 of the management server 20 executes the item setting process (step S103). Here, an individual item creation screen 540 and a multiple item creation screen 550 are used. And the control part 21 of the management server 20 performs an empty item production | generation process (step S104). Thereby, items can be individually registered, or a plurality of items can be registered together.

  (4) In the embodiment described above, the control unit 21 of the management server 20 executes a title selection process (step S106). When the normal mode is set, all the extracted items are displayed. When the name concealment mode is set, the names of other creators are hidden. In the non-display mode, other creator's items are hidden. Thereby, in the normal mode, all information related to the items can be shared. In the name concealment mode, information of different creators such as competitors can be concealed. In this case, by looking at the items of different creators, it is possible to match the consistency (view of the world) such as the style even if the creators are different. In the non-display mode, information sharing of the item image itself can be restricted.

  (5) In the above embodiment, the control unit 21 of the management server 20 executes the thumbnail display process (step S107). Here, the control unit 21 of the management server 20 executes a color classification process for each group (step S202). Thereby, it is possible to accurately grasp related images in a plurality of items. Further, the control unit 21 of the management server 20 executes the latest post image acquisition process (step S203). Here, since they are grouped and displayed according to the evolution level, the status of the item image can be grasped in the related item creation process. Furthermore, in the grouped items, the balance of the item images according to the evolution level (the richness of the character image and the background image) can be grasped.

  (6) In the above embodiment, the control unit 21 of the management server 20 executes list display processing (step S108). When this selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes batch change support processing (step S109). Thereby, the information regarding a some item can be edited collectively.

  (7) In the above embodiment, when the Gantt chart display button is selected, the control unit 21 of the management server 20 executes a Gantt chart display process (step S110). In this case, the control unit 21 of the management server 20 executes a child item specification process (step S302), a child item progress information acquisition process (step S303), and a parent / child item progress display process (step S304). To do. Thereby, it is possible to grasp not only the progress information of related items but also the status of the creation process of individual items in a list.

  (8) In the above embodiment, the control unit 21 of the management server 20 executes the item detail display process (step S111). The display control unit 213 identifies the check file image having the latest posting date and outputs a thumbnail image to the item image display area 601. Thereby, the creation status of the item image can be grasped. Further, the display control unit 213 displays thumbnail images of other evolution levels of this item. Thereby, the creation status of related items can be grasped. Further, the display control unit 213 rearranges the posting date and time in the order of the newest posting in the comment information D60 and the image information D70, and outputs them to the posting list display area 604. Thereby, it is possible to grasp the creation process of the item.

  (9) In the above embodiment, the control unit 21 of the management server 20 executes the image history display process (step S114). Here, the control unit 21 of the management server 20 executes acquisition processing for all check images (step S402). Slide display processing is executed (step S403). Thereby, the change of the item image in the creation process can be grasped. In particular, since the posted check image is output to a specific image display area, the change can be easily grasped by an image change operation.

In addition, you may change the said embodiment as follows.
In the above embodiment, the control unit 21 of the management server 20 executes the thumbnail display process (Step S107), the list display process (Step S108), and the Gantt chart display process (Step S110). Here, the progress of related items may be output as an image. In this case, the display control unit 213 of the control unit 21 acquires the item code to be displayed from the client terminal 10. And the display control part 213 acquires the image with the newest contribution date in each step about all the items relevant to this item. Then, the display control unit 213 outputs a history display screen on the display of the client terminal 10.

  As shown in FIG. 21, the history display screen 710 arranges related items on a first axis (for example, the horizontal axis) and arranges each step on a second axis (vertical axis). Then, the latest check image is output in the matrix of the first axis and the second axis. Thereby, while comparing the image of a related item with a 1st axis direction, a progress condition can be grasped | ascertained with a 2nd axis direction.

In the above embodiment, the control unit 21 of the management server 20 executes thumbnail display processing (step S107). Here, the step and status of this image may be output in association with the thumbnail image. In this case, the display control unit 213 of the control unit 21 outputs the latest step and status recorded in the image information D70 to the title screen in the thumbnail display mode.
As shown in FIG. 22, the title screen 720 in the thumbnail display mode includes a step display 711 and a status display 712.

  In the above embodiment, the control unit 21 of the management server 20 executes a Gantt chart display process (Step S110). In this Gantt chat, thumbnail images of each item may be output.

  In the above embodiment, the control unit 21 of the management server 20 executes image history display processing (step S114). In this case, a page turning button 701 is output to the display of the client terminal 10 on the history display screen 700 including the image display area 702. Here, the status may be output.

  As shown in FIG. 23, the status display 704 of the image displayed in the image display area 702 is output on the history display screen 700. Thereby, not only the change of the image but also the confirmation result of the image can be grasped.

  When the page turning button 701 is selected, the original image and the next image are repeatedly displayed a predetermined number of times (for example, 5 times) at a predetermined time interval (for example, 1 second), and then the next image is displayed. You may make it. Repeated display makes it easy to grasp the changed part.

  In the above embodiment, in the image history display process, the control unit 21 of the management server 20 executes an acquisition process for all check images (step S402) and a slide display process (step S403). Here, the developer may be able to write (red) a correction instruction for the check file image in feedback. In this case, the control unit 21 of the management server 20 assigns a post ID to this feedback and records it in the item management information storage unit 24. Furthermore, the control unit 21 of the management server 20 records image information D70 in which an image ID is assigned to an image in which a correction instruction is written in the check file. In this case, the image in which the correction instruction is written is recorded in the image storage unit 25 as a check file (with a correction instruction). Then, in the image history display process, page turning is performed in the order of a check file image and a check file (with a correction instruction) image. Thereby, the correction instruction given in the feedback can be grasped in the image history display process.

  In the above embodiment, in the thumbnail display process, the control unit 21 of the management server 20 executes the color classification process for each group (step S202). Here, if it is adjacent to a display field belonging to another group, a color scheme different from that of the adjacent display field is set. If it is adjacent to a display field belonging to the same group, the same color scheme as that of the adjacent display field is set. Set. As a result, it is displayed in a striped pattern of two colors in which the background color is alternately changed for each adjacent group. Here, the items forming the group may be set to different colors. For example, when items belonging to different groups are adjacent to each other, the control unit 21 of the management server 20 sequentially sets the display column to the first color (white) and the second color (blue). Furthermore, when the items belonging to the same group are adjacent to each other, the control unit 21 of the management server 20 sets both display fields to the third color (yellow). This makes it easy to recognize items belonging to the same group even when the background color is different every time depending on the order of rearrangement.

Next, technical ideas that can be grasped from the above-described embodiment and other examples will be described below together with their effects.
(A) a system for managing items,
For each project that creates a plurality of items, according to the item creation step, a storage unit that records an item image of an item associated with an item code indicating a collection,
A control unit connected to the client terminal,
The control unit is
From the client terminal, obtain information on the project that displays a list of item images,
Obtaining item images of items belonging to the project from the storage unit, generating a display screen for displaying the item images as a list,
Specifying an aggregate to which the item image belongs, and if an item image belonging to a different aggregate is adjacent on the display screen, set a display for identifying the different aggregate,
An item management system for outputting the display screen to the client terminal.
Therefore, according to the invention described in (a), it is easy to grasp item images belonging to the same aggregate.

(B) In the storage unit, each item image is recorded in association with the registration date and time,
In the creation step, the item image with the latest registration date and time is displayed on the display screen.
Therefore, according to the invention described in (b), it is easy to grasp the latest state even when a plurality of item images are registered according to the creation history.

(C) The item management system according to (a) or (b), wherein the display screen includes a step of creating the item in association with the item image.
Therefore, according to the invention described in (c), it is possible to grasp the creation status of the item image.

(D) The item management according to any one of (a) to (c), wherein an evolution form is specified for each item, and the aggregate is configured by associating items with different evolution forms. system.
Therefore, according to the invention described in (d), images can be listed in consideration of the evolution form.

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Management server, 21 ... Control part, 211 ... Authority management part, 212 ... Item management part, 213 ... Display control part, 214 ... History display part, 22 ... Authority information storage part, 23 ... User information Storage unit, 24 ... Item management information storage unit, 25 ... Image storage unit, 700 ... History display screen.

Claims (6)

A system for managing items,
For each project that creates a plurality of items, according to the item creation step, an item image of the item associated with the search key, a storage unit that records the posting date and time,
A control unit connected to the client terminal,
The control unit is
From the client terminal, obtain information and search key related to the project to display a list of item images,
Obtaining an item image associated with the search key of an item belonging to the project from the storage unit, and generating a display screen for displaying a list of images with the latest posting date and time among the item images,
An item management system for outputting the display screen to the client terminal. The item image is associated with an item code indicating a collective and viewing authority,
  The control unit is
  Obtaining information on the item code from the client terminal,
  Obtaining an item image associated with the item code from the storage unit;
  When the browsing authority of the client terminal is the first authority, a display screen for displaying the creator is displayed together with the acquired item image. When the browsing authority of the client terminal is the second authority, the creator The item management system according to claim 1, wherein a display screen for displaying the acquired item image without displaying the item is generated. The item image is associated with an item creation step for each project for creating a plurality of items, and step information indicating the degree of progress of the creation step is recorded in the storage unit,
  The control unit is
  Obtain information about the project from the client terminal,
  Identify item images belonging to the project as parent items,
  Identify the child items associated with the parent item creation step;
  Based on the step information, the progress of the child item and the progress of the child item are integrated.
The item management system according to claim 1, wherein a screen indicating a degree of progress of the parent item is generated. The item management system according to any one of claims 1 to 3 , wherein an evolution form is specified for each item, and items having different evolution forms are associated with each other . A method for managing items,
The item management system, for each project that creates a plurality of items, according to the item creation step, an item image of the item associated with the search key, a storage unit that records the posting date and time,
A control unit connected to the client terminal,
The control unit is
From the client terminal, obtain information and search key related to the project to display a list of item images,
Obtaining an item image associated with the search key of an item belonging to the project from the storage unit, and generating a display screen for displaying a list of images with the latest posting date and time among the item images,
An item management method, comprising: outputting the display screen to the client terminal. A program for managing items,
The item management system, for each project that creates a plurality of items, according to the item creation step, the item image of the item associated with the search key, a storage unit that records the posting date,
A control unit connected to the client terminal,
The control unit
From the client terminal, obtain information and search key related to the project to display a list of item images,
Obtaining an item image associated with the search key of an item belonging to the project from the storage unit, and generating a display screen for displaying a list of images with the latest posting date and time among the item images,
An item management program that causes the display screen to function as means for outputting to the client terminal.