Skip to content

Commit b3e13cb

Browse files
authored
Merge pull request #61 from meenulekha/update-user-guide
Update UserGuide.md
2 parents 56c4ecd + abe01b4 commit b3e13cb

File tree

1 file changed

+79
-1
lines changed

1 file changed

+79
-1
lines changed

docs/UserGuide.md

Lines changed: 79 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ The Hackathon Participant Management Application is designed to help organizers
1616
- [Exporting a selected participants](#exporting-selected-participants--link)
1717
- [Removing a person](#removing-a-person--remove)
1818
- [Clearing all entries](#clearing-all-entries--clear)
19+
- [Adding an event](#adding-an-event--addevent)
20+
- [Listing all events](#listing-all-events--listevent)
21+
- [Removing an event](#removing-an-event--deleteevent)
22+
- [Locating events by keywords](#locating-events-by-keywords--findevent)
1923
- [Exiting the program](#exiting-the-program--exit)
2024
- [Saving the data](#saving-the-data)
2125
- [Editing the data file](#editing-the-data-file)
@@ -52,6 +56,14 @@ The Hackathon Participant Management Application is designed to help organizers
5256
* `Update update John Dow /number 89898989` : Updates the information of the person named "John Doe"
5357

5458
* `Comment John Doe`
59+
60+
* `addevent en/Meeting ed/11-06-2024 ec/staff` : Adds an event named `meeting`.
61+
62+
* `deleteevent 8` : Deletes the 8th event shown in the list.
63+
64+
* `findevent meeting` : Finds events which names contain "meeting".
65+
66+
* `listevent` : Lists all events.
5567

5668
* `clear` : Deletes all contact information.
5769

@@ -76,7 +88,7 @@ The Hackathon Participant Management Application is designed to help organizers
7688
* Parameters can be in any order.<br>
7789
e.g. if the command specifies `n/NAME p/PHONE_NUMBER`, `p/PHONE_NUMBER n/NAME` is also acceptable.
7890

79-
* Extraneous parameters for commands that do not take in parameters (such as `help`, `list`, `exit` and `clear`) will be ignored.<br>
91+
* Extraneous parameters for commands that do not take in parameters (such as `help`, `list`, `listevent`, `exit` and `clear`) will be ignored.<br>
8092
e.g. if the command specifies `help 123`, it will be interpreted as `help`.
8193

8294
* If you are using a PDF version of this document, be careful when copying and pasting commands that span multiple lines as space characters surrounding line-breaks may be omitted when copied over to the application.
@@ -222,6 +234,68 @@ Example: You have successfully deleted participant John Doe.
222234
Precise expected outputs when the command fails
223235
* Error: no contact with id <id>. (when name is not in the list)
224236

237+
### Adding an event: `addevent`
238+
239+
Adds an event to HackLink.
240+
241+
Format: `add en/EVENTNAME ed/EVENTDATE c/EVENTCATEGORY`
242+
243+
<div markdown="span" class="alert alert-primary">:bulb:
244+
</div>
245+
246+
Examples:
247+
* `add addevent en/meeting ed/11-06-2024 ec/staff`
248+
* `add addevent en/conference ed/22-06-2024 ec/participant`
249+
250+
Cautions / Warnings for Addevent:
251+
* There should be no <span style="color:yellow">“/”</span> in each parameter.
252+
* Category should be one of Participant, Sponsor, and Staff.
253+
254+
### Listing all events : `listevent`
255+
256+
Shows a list of all events in HackLink.
257+
Example: `Total: <total number of data>`
258+
The table will show all the data
259+
260+
Format: `listevent`
261+
262+
### Removing an event : `deleteevent`
263+
264+
Remove specific events from the database.
265+
266+
Format: `deleteevent <id>`
267+
Example:
268+
`deleteevent 1`
269+
Acceptable values for each parameter
270+
* `<id>`: the id of the event in the list
271+
272+
Precise expected outputs when the command succeeds
273+
* You have successfully deleted <category> <name>.
274+
Example: You have successfully deleted event meeting.
275+
Precise expected outputs when the command fails
276+
* Error: no event with id <id>. (when event is not in the list)
277+
278+
### Locating events by keywords : `findevent`
279+
280+
Finds events which contain any of the given keywords.
281+
282+
Format: `findevent KEYWORD [MORE_KEYWORDS]`
283+
284+
* The search is case-insensitive. e.g `meeting` will match `Meeting`
285+
* The order of the keywords does not matter. e.g. `Lecture git` will match `git Lecutre`
286+
* Full text of a event is searched.
287+
* Only full words will be matched e.g. `Seminar` will not match `Seminars`
288+
* Events matching at least one keyword will be returned (i.e. `OR` search).
289+
e.g. `Lecture 1` will return `Lecture 2`, `Lecture 3`
290+
291+
Examples:
292+
* `findevent meeting` returns `meeting 1` and `meeting 2`
293+
* `findevent lecture` returns `AI lecture`, `OS lecture`<br>
294+
* `findevent participant` returns all events for participants in the list
295+
296+
### Exporting selected participants : `link`
297+
Produce a csv file with selected participants' contact information to provide to sponsor.
298+
The csv file will be saved in the selectedParticipants folder with the name list.csv.
225299

226300
### Clearing all entries : `clear`
227301

@@ -289,4 +363,8 @@ Action | Format, Examples
289363
**Find** | `find KEYWORD [MORE_KEYWORDS]`<br> e.g., `find James Jake`
290364
**List** | `list`
291365
**Comment** | `comment <name>, <notes>`
366+
**AddEvent** | `addevent en/EVENTNAME ed/EVENTDATE ec/EVENTCATEGORY`<br> e.g., `addevent en/meeting3 ed/11-06-2024 ec/staff`
367+
**ListEvent** | `listevent`
368+
**DeletEvent** | `deleteevent INDEX`<br> e.g., `deleteevent 8`
369+
**FindEvent** | `findevent KEYWORD [MORE_KEYWORDS]`<br> e.g., `findevent meeting`
292370
**Help** | `help`

0 commit comments

Comments
 (0)