Vcomputers, Clipboard and Document improvements

[Dusk]

What does this suggestion change/add/remove:
​

1. Ability to Select and Copy Information (e.g., SteamID & Name)​

• Current Issue: Documents do not allow direct selection and copying of critical identifiers when uploaded
• Suggested Fix: Implement a text selection tool that enables copying specific fields like SteamID, names etc..

​

2. Third Option for Document Revision Instead of Only Denial/Approval​

• Current Issue: The current system forces an accept/deny decision with no structured revision process.
• Suggested Fix: Introduce a "Return for Revisions"option, allowing submitters to make corrections based on feedback before outright rejection. This should include:
  
  • Inline comments on errors.
  • Suggested changes with a reason log.
  • A revision tracking system.

​

3. Organization Upgrade for Computers (Tracking & Revisions)​

• Current Issue: Users cannot track grades, submissions, or corrections effectively.
• Suggested Fix: A "Personal Work Hub"within the system that allows:
  
  • Tracking of graded and pending documents.
  • Notifying users when revisions are required.
  • Access to submission history and previous evaluations.

​

4. SCIPNet Submission Location Bugs​

• Current Issue: Some locations are unavailable in the SCIPNet submission list.
• Suggested Fix: Conduct a review of the SCIPNet databaseto:
  
  • Identify missing locations.
  • Remove invalid ones.
  • Ensure all active locations appear in submission options.

​

5. Improved Document Editor Features​

• Better Image Support: Ensure images embed properly without formatting issues.
• Coherent Redaction Tool: Fix buggy redaction, making it removable without deleting an entire line.

These improvements will significantly enhance efficiency for all personnel dealing with documentation, ensuring smoother operations within Research, Security, and Administrative divisions. Let me know if you need further refinement on these proposals.

​

6. Auto-Fill for Repetitive Fields​

• Current Issue: Users must manually input repetitive data (e.g., Name, Rank, SteamID) in multiple documents.
• Suggested Fix: Implement auto-fillfor:
  
  • Name, Rank, and Department
  • SteamID (if linked)
  • Frequently used headers (e.g., test subject, SCP classification)
• Benefit: Reduces clerical errors and saves time.

7. Improved Search & Filtering for Submitted Documents​

• Current Issue: Finding specific documents is tedious, especially for high-volume users.
• Suggested Fix:Implement:
  
  • Search by keywords, author, or date.
  • Filters by approval status (Approved, Pending, Denied, Under Revision).
  • Quick Access folders for frequently used document types.

8. Customizable Notification System​

• Current Issue: Users miss important document updates (revision requests, approvals, deadlines).
• Suggested Fix:Allow users to enable notifications for:
  
  • Document status changes (Approved, Denied, Revision Requested).
  • Deadlines approaching (if applicable).
  • Mentions in comments (when someone requests changes).

9. Archive & Expiry System for Old Documents​

• Current Issue: Overloaded storage with outdated documents.
• Suggested Fix:Add:
  
  • Auto-archiving of old documents after a set period.
  • Soft deletion (deleted files are recoverable for a time).
  • Expiration tags on time-sensitive reports (e.g., outdated research).

10. Role-Based Access & Permission Control​

• Current Issue: Some documents are edited by unauthorized personnel or require specific reviewers.
• Suggested Fix: Implement role-based permissionswhere:
  
  • Only certain ranks can edit/view classified documents.
  • Approvers can lock a document to prevent unauthorized edits.
  • Special access requests can be made for restricted files.

11. Improved Mobile & Tablet Compatibility​

• Current Issue: Limited access on mobile devices, making fieldwork documentation difficult.
• Suggested Fix:Optimize document editing and submission for:
  
  • Tablet interface

12. Quick Access to Frequent Submissions​

• Current Issue: Users must manually find and reopen frequently used forms.
• Suggested Fix: Add a "Favorites" or "Recent Documents"tab, allowing:
  
  • Quick access to frequently used reports.
  • Instant retrieval of ongoing drafts.

​

​

13. Auto-Save Feature for Drafts​

• Current Issue: Users lose progress if they accidentally close or reload their document.
• Suggested Fix: Enable auto-saving every X seconds/minutes to prevent loss of work.
• Benefit: Prevents frustration from lost progress due to disconnects or misclicks.

Has something similar been suggested before? If so, why is your suggestion different?:
No

Possible Positives of the suggestion (At least 2):
Any updates at all to the SCIPNET, Documents and Clipboards are almost always a positive.
Better RP with documents
Better interaction with Junior Personnel if the system allows individuals to experiment without fear of having a bad document
System is convoluted, almost like clockwork, deviation in documentation is only dependent on external features like images to set documents apart. Which is not fair for everyone's case as some are more inventive than others

Possible Negatives of the suggestion:
Development Time

Based on the Positives & Negatives, why should this suggestion be accepted:
I think the current system in general needs a complete rework as this is the only Unique system RSD has and its outdated and buggy. Not to mention RSD is entirely dependent on the documents and clipboard system to function properly, with a better system you will see more interest and activity.​

 

[Clementine]

+ Support

I find that typing on the clipboards can be both the best and worst thing about playing on the server. A change to the workflow and how work is graded could benefit research. There is already a monetary system in place for documents that achieve the "Excellent" rating, which would have to go if you could revise a document, but aside from that, I agree with every other change.

 

[Dusk]

+ Support

I find that typing on the clipboards can be both the best and worst thing about playing on the server. A change to the workflow and how work is graded could benefit research. There is already a monetary system in place for documents that achieve the "Excellent" rating, which would have to go if you could revise a document, but aside from that, I agree with every other change.

There would be a system that stamps submitted documents after approval.
Could be extended to documents that are submitted. Any documents that are edited after the fact to adjust quality for rewards would be a punishable offence enforced by ISD considering they are technically like RAISA at this point.

 

[Niox]

+Support

 

[Zen]

+Support
Honestly, the whole of SCiPNet is just kinda bad and the whole thing could do with a redo. I feel like it's likely that things like this will be rejected, though, because a lot of people don't really use SCiPNet (ignoring the fact that part of that is because it's so bad). Some basic things either can't be done at all, or require Senior Admins to do, like making directories, and things like deleting documents or directories or moving stuff around requires Superadmins.

 

[GameRush_cz]

+Support
Honestly, the whole document and especially the computer network feels like it has been thrown together when the server first launched and has not been touched since. It feels super outdated. A good overhall could actually make these things worth while. Also I would love the notification system, as there have been many times where I uploaded a research document, logged off and then I did not know anything about how it was graded.
Finally, I would add one more thing. A change so that if you are actively writing a document, hacking etc. (just active in a UI of any sorts) you do not get detected as AFK. It is really annoying and distracting that you have to do some movement periodically to not be counted as AFK.

 

[Marvin Garden]

Has something similar been suggested before? If so, why is your suggestion different?:
No

Accepted - Major ScipNET Overhaul (Big Read!)

The Suggestion This suggestion would see the overhaul of ScipNET through a variety of features and accounts for the current ScipNET features on the Dev Tracker. See them here and here. So, even though I am suggesting new things, these new things are in addition to the already approved...

civilnetworks.net

Accepted - Changes to clipboard

What does this suggestion change/add/remove: In the clipboard add watermarks for each department IE: Research, E11, ISD/O1/A1, DEA, GSD ect As seen below add sections to check the regiment you want to have the background as. Has something similar been suggested before? If so, why is your...

civilnetworks.net

Accepted - Rework the SCiPnet Computer Searching/Sorting System

What does this suggestion change/add/remove: [Changing the way you use the in-game computer mainly involves improving document searching. I want a sort button where you can arrange items based on different criteria like the date it was uploaded, clearance level, and your own documents. An...

civilnetworks.net

A vcomputers overhaul has been on the dev tracker for ages, its just not a high priority.

 

[Dusk]

I took a look at those and I still have some suggestions not mentioned in the others. Most of which stems from SCiPnet overhauls, but I believe the basic overhaul on documentation and the process leading up to SCiPnet

 

[Reiner Zephyran]

Please make my job easier
+Support

 

[Emilia Foddg]

There are plans to improve VComputers as the result of prior suggestions - Although I can see that a significant amount of what you've proposed is unique to this suggestion; I don't see any immediate issues, but I've never interacted with VComputers enough (outside of documents) to make an informed contribution.
+Support