Analogía entre el juego y un poema de Fernando Pessoa

8.1. Introduction

Newsgroup reader, request and administrator are the main structure of the newsgroup. In this structure, we have a security model for system. Users come to a JSP interface that allows them to sign up to newsgroup. The user can request several optional permission levels: to read messages, to post messages, and to become admin for particular newsgroups. This request is confirmed by the administrator before the user can access the newsgroup.

Besides permissions, the system gives the user the option to get the copy of the newsgroup message to his or her regular email account. Users can also optionally received attachments posted to newsgroups, and can receive their own newsgroup postings by email. These options give the user a flexible control mechanism to use newsgroups.

The administrator for a newsgroup has always the option to confirm user requests, modify user access, and add new users to a newsgroup. By having multiple administrators, the system doesn’t depend on one administrator to control system. Each newsgroup may have multiple administrators to use systems. However, all the users must register to Jetspeed in order to use the newsgroups.

This system has dynamic structure to show multiple newsgroup lists on the page, if the user has access to use that newsgroups, user have the option to select desired newsgroup from the list. According to user’s rights, the messages will be shown on the group. The JSP page is used for this structure. All the user rights and request are stored in the Oracle Database, and Java Script is used for user-friendliness.

In this section, request and administrator information are stored in the database. User requests for selected newsgroup.

8.2. Newsgroup Structure

The following summarizes the permissions that can be requested when registering for a newsgroup. These are confirmed or denied by the administrator for that group.

Permissions

rA, read access: You want to read messages using the NewsReader.

wA, write access: You want to send messages to this newsgroup.

aA, admin access: You want to administer this newsgroup.

eN, email notification: You want to receive other people's messages.

aN, attachment notication: You want to receive attachments messages might have.

ccN, CC notification: You want to receive your message as well.

Steps for using the newsgroup structure figure shown below:

Newsgroups (read, write,admin, eN, ccN, aN)

access options

User Newsgroup Database user re

quest User select

Administrator write,admin, eN, ccN, aN)Newsgroups (read, access options confirm

delete

modify

get request

confirmed user rights

Newsgroups User request to use newsgroup user ne wsgrou p list tep2

Step3 _{( to get message id's)}RSS File

XML file(to get specific message) messages

Step1

8.2.1.

Step 1: Request

User makes request for any newsgroup which is open to the users. In order to make a request you need to enter email address in the email sections because the system has the structure for using email for attachment notify, cc Notify and email Notify.

There are four sections for request section.

1. Current rights (unchanged): for newsgroups. For this section, users only see their confirmed rights for newsgroups.

2. Pending request: User's pending will be shown in this section.

3. Unselected newsgroup: for that user hasn’t selected that newsgroup yet. 4. Current rights: User can modify their access in this newsgroup section.

The first part cannot be modified or deleted by user, but for the other section, user can have a request or modify the newsgroups.

Newsgroup current right section: User can see their current registered newsgroup list. In this newsgroup list, they can observe their rights for newsgroups without changing their rights. When the user makes a request for newsgroups, their request is kept in the database. It will be stored in the request table until their request is confirmed by the administrator. After the requests are confirmed by the administrator, users can automatically use the confirmed newsgroups.

In order to distinguish the newsgroups, checkbox name is unique for each newsgroup. For example, "group_cgnews" is different than the "group_cgreports". "group_" string added to the beginning of the each newsgroup name. The difference is shown below:

<td width="10%" height="34"><b>cgnews</td>

<td width="5%" height="34"><input type="checkbox" name="group_cgnews" value="read" checked disabled></td>

<td width="10%" height="34"><b>cgreports</td>

<td width="5%" height="34"><input type="checkbox" name="group_cgreports" value="read" checked disabled></td>

User has to check the Select checkbox for requested newsgroup. Otherwise, the request will not be accepted.

8.2.2.

Step2: Confirmation

The current system has an option for selection mechanism for newsgroup. We define roles for newsgroup. Admin role, user role, and top admin role defined in the system. This allows us to define other roles, when we need to define and use. This structure allows dynamic structure in the newsgroup.

8.2.3.

Step3: News reader

OKC newsgroup displayer uses RSS URI to construct the e-mail/newsgroup hierarchy and to get the body of messages. The NewsFeeder (described in Section 6) constructs the RSS file at the request of the

NewsReader. The NewsReader is then responsible for formatting the display of the news group postings. XSL is used to extract data from XML file in order to show the required messages to the users. OKC newsgroup displayer checks the user’s access rights by using the database. User access rights allow users to read from and write into newsgroup topics. Figure shown below explain the scenario.

Newsgroup