METHOD AND SYSTEM FOR CORRECTING A TYPOGRAPHICAL ERROR IN A FILENAME OF AN ATTACHMENT

Abstract

A system (200) for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email) is disclosed. The system (200) includes an extraction module (214) configured to extract a filename associated with the at least one attachment from the draft of the email. The system (200) further includes a spell-check module (216) configured to determine the extracted filename having a typographical error using one or more filename conventions. In an embodiment, the spell-check module (216) is configured to suggest a filename based on the determination of typographical error in the extracted filename. Furthermore, the system (200) includes a correction module (218) configured to correct the typographical errors in the filename of the at least one attachment for the draft of the email based on the suggestion.

Specification

Description:TECHNICAL FIELD
[0001] The present disclosure relates to electronic communication systems, and more particularly, to a method and a system for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email).
BACKGROUND
[0002] Electronic communications (such as electronic messaging or "e-mail or email") have become an indispensable part of modern life, with millions of messages exchanged daily across various platforms. Alongside the content of emails, attachments play a crucial role in conveying information, ranging from documents and presentations to images and multimedia files. However, one of the common challenges in email communication is typographical errors (for example, duplicated letters, misspellings, or inconsistent capitalization) in the attachment filenames. These errors often go unnoticed by users, causing confusion to recipients, difficulty in identifying files, and a lack of professionalism in formal communication. These errors are particularly common when the users are in a hurry or unaware of the mistake.
[0003] While conventional spell-checking tools exist for checking content within emails, the attachment filenames are often overlooked, placing the burden on the users to manually identify and fix the potential typographical errors. However, the manual detection and correction of the typographical errors in the filenames are time-consuming and prone to oversight, especially for the users handling a high volume of emails or attachments. Therefore, there is a higher chance of errors persisting unnoticed until after the email is sent.
[0004] Conventional techniques also lack multi-language support and contextual analysis for the attachment filenames creating additional challenges in non-English settings. In such a scenario, the attachment filenames in non-English languages may not be accurately corrected due to the lack of appropriate dictionaries and context-aware systems.
[0005] Therefore, there exists a need to have an improved solution to overcome the above-mentioned problems associated with the detection and correction of the typographical errors in the attachment filenames.
SUMMARY
[0006] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify essential inventive concepts of the invention nor is it intended for determining the scope of the invention.
[0007] According to an aspect of the present disclosure, a method for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email) is disclosed. The method includes extracting, by an extraction module, a filename associated with the at least one attachment from the draft of the email. The method further includes determining, by a spell-check module, the extracted filename having a typographical error using one or more filename conventions. Furthermore, the method includes suggesting a filename based on the determination of the typographical error in the extracted filename. Furthermore, the method includes correcting, by a correction module, the typographical errors in the filename of the at least one attachment for the draft of the email based on the suggestion.
[0008] According to another aspect of the present disclosure, a system for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email) is disclosed. The system includes an extraction module configured to extract a filename associated with the at least one attachment from the draft of the email. The system further includes a spell-check module configured to determine the extracted filename having a typographical error using one or more filename conventions. In an embodiment, the spell-check module is configured to suggest a filename based on the determination of the typographical error in the extracted filename. The system further includes a correction module configured to correct the typographical errors in the filename of the at least one attachment for the draft of the email based on the suggestion.
[0009] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.
BRIEF DESCRIPTION OF THE FIGURES
[0010] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0011] Figure 1 illustrates a schematic block diagram depicting an environment for implementing a system for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email), in accordance with an embodiment of the present disclosure;
[0012] Figure 2 illustrates a schematic block diagram depicting the system for correcting the typographical error in the filename of the at least one attachment for the draft of the email, in accordance with an embodiment of the present disclosure;
[0013] Figure 3 illustrates a schematic block diagram depicting module(s) of the system for correcting the typographical error in the filename of the at least one attachment for the draft of the email, in accordance with an embodiment of the present disclosure;
[0014] Figure 4 illustrates a flowchart depicting an exemplary method for correcting the typographical error in the filename of the at least one attachment for the draft of the email, in accordance with an embodiment of the present disclosure; and
[0015] Figure 5 illustrates a flowchart of an exemplary method depicting a detailed outline for correcting the typographical error in the filename of the at least one attachment for the draft of the email, in accordance with an embodiment of the present disclosure.
[0016] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
DETAILED DESCRIPTION OF THE FIGURES
[0017] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the various embodiments and specific language will be used to describe the same. It should be understood at the outset that although illustrative implementations of the embodiments of the present disclosure are illustrated below, the present invention may be implemented using any number of techniques, whether currently known or in existence. The present disclosure is not necessarily limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified within the scope of the present disclosure.
[0018] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.
[0019] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0020] It is to be understood that as used herein, terms such as, "includes," "comprises," "has," etc. are intended to mean that the one or more features or elements listed are within the element being defined, but the element is not necessarily limited to the listed features and elements, and that additional features and elements may be within the meaning of the element being defined. In contrast, terms such as, "consisting of" are intended to exclude features and elements that have not been listed.
[0021] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" as used herein, refers to a non-exclusive or unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0022] As is traditional in the field, embodiments may be described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the invention. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the invention.
[0023] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.
[0024] The present disclosure delineates an improved system and method for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email) before transmission. Particularly, the present invention aims to provide an automated solution for the detection and correction of the typographical errors in the filenames, thereby reducing the likelihood of errors and improving the overall clarity and professionalism of email communication. Further, the present disclosure offers support for correcting filenames in various languages and therefore is especially valuable in settings where multiple languages are used.
[0025] Figure 1 illustrates a schematic block diagram depicting an environment 100 for implementing a system 108 for correcting the typographical error in the filename of the at least one attachment for the draft of the email, in accordance with an embodiment of the present disclosure. In an embodiment, the environment 100 may include a sender device 102 (alternatively referred to as a user device 102), and a receiver device 104 that may be connected to the sender device 102 via a network 106. Further, the environment 100 may include a system 108 that may be implemented on the sender device 102 and/or the receiver device 104. In an implementation, the network 106 may include a wireless network or a wired network. For example, the network 106 corresponds to cellular networks or mobile networks, such as third-generation (3G), fourth-generation (4G), fifth-generation (5G), pre-5G, and sixth-generation (6G) networks, or any other wireless communication network such as Wireless fidelity (Wi-Fi) connection, Near-Field communication (NFC) connection, and Bluetooth connection.
[0026] In an embodiment, the sender device 102 may be associated with a sender (alternatively referred to as a user) capable of sending the email to the receiver device 104 via the network 106. The received device 104 may be associated with a recipient for receiving the email.
[0027] In various embodiments, the sender device 102 and/or the receiver device 104 may be a user equipment. In a non-limiting example, the sender device 102 and/or the receiver device 104 may be a smartphone, a laptop computer, a desktop computer, a Personal Computer (PC), a television, a notebook, a tablet, a smartwatch, or any device capable of transmitting and receiving one or more email attachments.
[0028] In an embodiment, the system 108 on the sender device 102, may detect the typographical error in the filename of the attachment for the draft of the email thereby allowing an automatic detection and correction of the typographical error in the filename of the attachment for the draft of an email.
[0029] The system 108 may detect the typographical error in the filename when the user adds the attachment in the draft of the email. Thereafter, the system 108 may offer a plurality of options to the user, such as replacing the filename with a suggested filename, retaining the filename, and manually overriding the filename by proposing a new filename, before sending the email to the receiver device 104. For example, as shown in Figure 1, the user adds an attachment named "Repport.docx" to the draft of the email. The system 108 detects that there is a typographical error in the filename of the attachment and suggests a correct filename to the user. The system 108 also offers three options to the user - (1) to replace the filename "Repport" with the suggested filename "Report", (2) to retain the filename "Repport", and (3) to manually override the filename "Repport" by proposing a new filename. Thereafter, the system 108 may correct the filename or retain the filename or replace the filename with the user-proposed filename based on the user's decision. Thus, the present disclosure reduces potential typographical errors in the filenames thereby ensuring clarity in email communication. The system 108 is now described below in greater detail in conjunction with Figure 2.
[0030] Figure 2 illustrates a block diagram of the system 108, in accordance with an embodiment of the present disclosure. The system 108 is configured to be implemented in the user device 102 having the email client application and works in tandem with the email client application, aimed at the automatic detection and correction of the typographical error in the filename of the at least one attachment for the draft of the email before transmission, thereby improving accuracy, professionalism, and clarity in file management and email communication.
[0031] The system 108 may include, but is not limited to, one or more processor 202, a memory 204, an input/output (I/O) interface 208, one or more modules 210, and data 212. The one or more modules 210 and the memory 204 may be coupled to the one or more processor 202.
[0032] As a non-limiting example, the one or more processor 202 can be a single processing unit or several units, all of which could include multiple computing units. The one or more processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the one or more processors 202 are adapted to fetch and execute computer-readable instructions and data stored in the memory 204. Among other capabilities, the processor 202 may be configured to fetch and execute computer-readable instructions and data stored in the memory 204. The processor 202 may include one or a plurality of processors. The plurality of processors is further implemented as a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit, such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU). The plurality of processors may control the processing of the input data in accordance with a predefined operating rule or an artificial intelligence (AI) model stored in the memory 204. The predefined operating rule or the AI model is provided through training or learning.
[0033] The processor 202 may be disposed in communication with one or more input/output (I/O) devices via an Input/Output (I/O) interface 208. The I/O interface 208 may employ communication code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, and the like, etc. In another embodiment of the present invention, the I/O interface 208 may employ ethernet, industrial wireless Local Area Network (LAN), Process Field Bus (PROFIBUS), Actuator Sensor (AS) Interface, and the like.
[0034] The memory 204 may be configured to store instructions executable by the processor 202. In one embodiment, the memory 204 may communicate via a bus within the system 200. The memory 204 may include but is not limited to, a non-transitory computer-readable storage media, such as various types of volatile and non-volatile storage media including, but not limited to, random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one example, the memory may include a cache or random-access memory (RAM) for the processor 202. In alternative examples, the memory 204 may be separate from the processor 202 such as a cache memory of a processor, the system memory, or other memory. The memory 204 may be an external storage device or a database for storing data. The memory 204 may be operable to store instructions executable by the processor 202. The functions, acts, or tasks illustrated in the figures or described may be performed by the programmed processor for executing the instructions stored in the memory 204. The functions, acts, or tasks are independent of the particular type of instruction set, storage media, processor, or processing strategy and may be performed by software, hardware, integrated circuits, firmware, micro-code, and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing, and the like.
[0035] The one or more modules 210, amongst other things, may include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement data types. The module(s) 210 may also be implemented as, signal processor(s), state machine(s), logic circuitries, and/or any other device or component that manipulates signals based on operational instructions.
[0036] Further, the one or more modules 210 may be implemented in hardware, instructions executed by a processing unit, or by a combination thereof. The processing unit may comprise a computer, a processor, such as the one or more processor 202, a state machine, a logic array, or any other suitable devices capable of processing instructions. The processing unit may be a general-purpose processor which executes instructions to cause the general-purpose processor to perform the required tasks or, the processing unit may be dedicated to performing the required functions. In another embodiment of the present disclosure, the one or more modules 210 may be machine-readable instructions (software) which, when executed by a processor/processing unit 202, perform any of the described functionalities.
[0037] In an embodiment, the one or more modules 210 may include an extraction module 214, a spell-check module 216, a correction module 218, a prompt module 226, an adaption module 228, and a feedback module 230. The spell-check module 216 may further include a default language sub-module 220, a multi-language sub-module 222, and a contextual sub-module. The extraction module 214, the spell-check module 216, the correction module 218, the prompt module 226, the adaption module 228, and the feedback module 230 may be in communication with each other. The data 212 may serve, amongst other things, as a repository for storing data processed, received, and generated by one or more of the one or more modules 210. In an embodiment, the one or more modules 210 may be configured to perform various operations or steps that may be discussed and explained in detail in conjunction with Figure 4 and Figure 5.
[0038] Figure 3 illustrates a schematic block diagram depicting the module(s) 210 of the system 108, in accordance with an embodiment of the present disclosure. The one or more modules 210 may include the one or more instructions that may be executed to cause the system 108, in particular, the processor 202 of the system 108, to execute the one or more instructions.
[0039] In an embodiment, the extraction module 214 may be configured to extract the filename associated with the at least one attachment 304 from the draft of the email 302. In an embodiment, the extraction module 214 may be configured to detect when the at least one attachment 304 is added to the draft of the email 302 to initiate the extraction of the filename. In an embodiment, for extraction of the filename, the extraction module 214 may be configured to identify the at least one attachment 304 added to the draft of the email 302, capture a filename syntax from the at least one attachment 304, segregate the filename and the file extension from the captured filename syntax, and extract the filename associated with the at least one attachment 304 based on the segregation. For example, if the attachment 304 "fghyuiop.docx" is added to the draft of the email, the extraction module 214 may be configured to segregate the filename "fghyuiop" and the file extension ".docx" and then extract the filename "fghyuiop" associated with the attachment 304 for further analysis. In an embodiment, the filename syntax may include the filename and the file extension associated with the captured filename syntax. In an embodiment, the file extension may include ".pptx" for presentations, ".xlsx" for spreadsheets, ".docx" for documents, and the like. In an embodiment, the extraction module 214 may be configured to analyze the segregated file extension to identify a file type associated with the at least one attachment 304. In the above example, from the file extension ".docx", the extraction module 214 may understand that the attachment 304 is a Word document. In an embodiment, the extraction module 214 may be configured to pass the extracted filename to the spell-check module 216.
[0040] In an embodiment, the spell-check module 216 may be configured to determine the extracted filename having the typographical error using one or more filename conventions. In an embodiment, the spell-check module 216 may be configured to use a predefined set of rules for detecting the typographical error in the filename. In an embodiment, the spell-check module 216 may be configured to utilize one or more of the default language sub-module 220, multi-language sub-module 222, and contextual sub-module 224 for determination of the typographical error in the extracted filename using the one or more filename conventions.
[0041] In an embodiment, the default language sub-module 220 may be configured to correlate characters of the extracted filename with characters of one or more linguistic words stored in a default language dictionary. For example, the default language sub-module 220 may be configured to compare the spelling of the extracted filename with the spelling of the one or more linguistic words stored in the default language dictionary. If the default language sub-module 220 is unable to find a match in the default language dictionary based on the comparison, the default language sub-module 220 may be configured to detect that the filename is not a valid word. In such a case, the default language sub-module 220 may be configured to recognize the extracted filename as containing a typographical error. In an embodiment, the default language dictionary may be stored in the memory 204 or may be integrated with the default-language sub-module 220. In the above example where the extracted filename is "fghyuiop", the default language sub-module 220 may be configured to compare the filename "fghyuiop" with the one or more linguistic words stored in the default language dictionary. If the default language sub-module 220 does not find a match in the default language dictionary based on the comparison, the default language sub-module 220 may be configured to recognize that there is a typographical error. Accordingly, the default language sub-module 220 may be configured to consider the extracted filename "fghyuiop" as a potential candidate for correcting the typographical error.
[0042] In an embodiment, the multi-language sub-module 222 may be configured to correlate the characters of the extracted filename with characters of one or more linguistic words stored in a multi-language dictionary based on the detection of a language of the filename. For example, the multi-language sub-module 222 may be configured to check whether the extracted filename is a meaningful term in any of a plurality of languages supported by the multi-language dictionary. In an embodiment, the multi-language sub-module 222 may be configured to identify the language of the extracted filename and check whether the extracted filename is a meaningful term in the identified language. If the multi-language sub-module 222 determines that the extracted filename is not a meaningful term in any of the plurality of supported languages, the multi-language sub-module 222 may be configured to recognize the extracted filename as having a typographical error. In an embodiment, the multi-language dictionary may be a dynamic dictionary stored in the memory 204 or may be integrated with the multi-language sub-module 222. In the above example where the extracted filename is "fghyuiop", the multi-language sub-module 222 may be configured to check whether the filename "fghyuiop" is a meaningful term in any of the plurality of supported languages. If the multi-language sub-module 222 determines that the extracted filename is not a meaningful term in any of the plurality of supported languages, the multi-language sub-module 222 may be configured to consider the filename "fghyuiop" as having a typographical error. Thus, the present disclosure facilitates effective detection and correction of the typographical errors in the attachment filenames regardless of the language in which the filename is written.
[0043] In an embodiment, the contextual sub-module 224 may be configured to correlate the characters of the extracted filename with characters of a pre-stored one or more contextual terminology relating to the identified file type using natural language processing (NLP) techniques. For example, the contextual sub-module 224 may be configured to use the NLP techniques to assess a context of the extracted filename by evaluating the commonly used terms related to the identified file type. In an embodiment, the contextual sub-module 224 may be configured to take into account one or more common business or professional terms related to a plurality of document types, and patterns and conventions associated with a plurality of file types. In an embodiment, the contextual sub-module 224 may be configured to check whether the extracted filename has a semantic meaning relevant to the identified file type thereby enhancing the accuracy of the detection and correction of the typographical error in the filename. If the contextual sub-module 224 determines that the extracted filename is not the relevant term for the identified file type, the contextual sub-module 224 may be configured to identify the extracted filename as having a typographical error. In the above example where the extracted filename is "fghyuiop", the contextual sub-module 224 may be configured to check whether "fghyuiop" is the relevant term for the Word documents (i.e., the identified file type). If the contextual sub-module 224 determines that the extracted filename is not relevant, the contextual sub-module 224 may be configured to recognize the filename "fghyuiop" as having a typographical error. In another example, if the file type is the Word document (file extension is ".docx") and the extracted filename is "Preeview.docx", the contextual sub-module 224 may be configured to recognize that "Preview" is a common term associated with the word documents. Thus, the contextual sub-module 224 may be configured to recognize the extracted filename as having a typographical error.
[0044] In an embodiment, for determination of the typographical error in the extracted filename, the default language sub-module 220 may be configured to check whether there is any spelling error in the extracted filename. If the default language sub-module 220 determines the spelling error, the multi-language sub-module 222 may be configured to determine whether the extracted filename with the typographical error is a meaningful term in any of the plurality of supported languages. If the multi-language sub-module 222 determines that the extracted filename is not the meaningful term, the contextual sub-module 224 may be configured to check whether the extracted filename is the relevant term for the identified file type. It should be noted that these operations can be performed in any order.
[0045] In an embodiment, the spell-check module 216 may be configured to determine the typographical error in the extracted filename based on the correlation of the characters. In an embodiment, while determining the typographical error in the extracted filename based on the correlation of the characters, the spell-check module 216 may be configured to determine at least one of duplicated characters (e.g., "Contractt"), missing letters (e.g., "Cotract"), improper capitalization (e.g., "CONtract"), extra spaces (e.g., "Con tract"), and improper use of special characters (e.g., "Contr@ct"). In an embodiment, the spell-check module 216 may be configured to suggest a filename based on the determination of the typographical error in the extracted filename. In an embodiment, the spell-check module 216 may be configured to suggest more than one filename. For example, the spell-check module 216 may be configured to suggest the filename "Contract" for each of the above-mentioned scenarios (e.g., duplicated characters, missing letters, improper capitalization, extra spaces, and improper use of special characters) for correction of the typographical error. Further, in the above example where the extracted filename is "fghyuiop", upon determining that the extracted filename has the typographical error, the spell-check module 216 may be configured to suggest more meaningful and/or generic filenames associated with the identified file type. For example, the spell-check module 216 may be configured to suggest filenames such as "Document.docx", "File.docx", and "Untitled.docx" for correction of the typographical error. In an embodiment, the generic suggestions may be based on common filenames used for documents without a proper filename. In an embodiment, the spell-check module 216 may be configured to pass the suggested filename(s) to at least one of the prompt module 226 or the adaption module 228.
[0046] In an embodiment, the prompt module 226 may be configured to initiate a prompt to receive a user input, based on the suggested filename, to at least one of accept the suggested filename, retain the extracted file name, and propose a new file name. Particularly, the prompt module 226 presents the suggested filename to the user and provides the options, for example, to (1) accept the suggested filename, (2) retain the extracted filename, or (3) manually override the extracted filename with the new filename of the user's choice. In the above example where the extracted filename is "fghyuiop", the prompt module 226 may be configured to initiate the prompt to receive the user input based on the suggested filenames "Document.docx", "File.docx", and "Untitled.docx" received from the spell-check module 216. In an embodiment, the prompt module 226 may present the suggested filenames and provide the above-mentioned options to the user via a user interface (UI). In an embodiment, if the user chooses to propose the new filename, the prompt module 226 may be configured to allow the user to manually override the extracted filename with the filename of the user's choice via the UI. In an embodiment, the prompt module 226 may be configured to trigger initiation of the prompt to receive the user input on at least one of, the addition of the at least one attachment 304 to the draft of the email 302 and sending of the draft of the email 302. In an embodiment, the prompt module 226 may further be configured to provide a real-time filename suggestion to the user for correcting the typographical error in the filename as soon as the user adds the attachment 304 to the draft of the email 302. In an embodiment, the real-time suggestion may be presented to the user through the UI. In an embodiment, the prompt module 226 may be configured to offer the options to the user for either approving or rejecting the real-time suggestion thereby ensuring that the user remains in control of a final filename. In an embodiment, the prompt module 226 may also be configured to allow the user to review the history of the received user inputs thereby allowing the user to access a record of changes made to the filenames.
[0047] In an embodiment, the correction module 218 may be configured to correct the typographical error in the filename of the at least one attachment 304 for the draft of the email 302 based on the suggestion. In an embodiment, the correction module 218 may be configured to correct the typographical error in the filename based on the received user input on the prompt module 226. For example, if the user chooses to accept the suggested filename, the correction module 218 may be configured to replace the extracted filename with the suggested filename. In such as case, the recipient may receive the attachment 304 with the corrected filename. If the user chooses to retain the extracted filename, the correction module 218 may be configured to maintain the extracted filename. In such a case, the recipient may receive the attachment 304 with the extracted filename. In an embodiment, the correction module 218 may be configured to apply automatic corrections to the typographical error in the filename based on a pre-configured set of rules or user preferences. For example, the correction module 218 may be configured to apply automatic corrections to the typographical error in the filename based on one or more of the user's past filename behaviour and preferences, detection of spelling errors in the filename, contextual analysis of common terms related to documents, and a preconfigured set of appropriate language rules. In an embodiment, the correction module 218 may be configured to correct the filename in any of the plurality of supported languages.
[0048] In an embodiment, the adaption module 228 may be configured to refine the suggested filename(s), received from the spell-check module 216, using at least one machine learning technique based on user behaviour and interaction patterns from previously received user input for correcting the typographical errors in the filename. In an embodiment, the adaption module 228 may be configured to refine the suggested filename(s) based on one or more of the user's past behaviour, filename patterns, filename corrections made by the user, and common filenames preferred by the user. For example, upon detecting that the user has never used the filename "fghyuiop" in the past, the adaption module 228 may be configured to recognize the filename as having the typographical error. In an embodiment, upon detecting that the user has used the filename "fghyuiop" in the past without any correction, the adaption module 228 may be configured to refrain from refining such filenames. In an embodiment, the adaption module 228 may be configured to autocorrect the typographical error in the filename based on the previously received user input. In an embodiment, the adaption module 228 may be configured to override the suggested filename with the refined suggested filename. In an embodiment, if the user chooses to accept the suggested filename, the adaption module 228 may be configured to learn that filenames similar to the extracted filenames should be corrected going forward. In another embodiment, if the user decides to retain the extracted filename, the adaption module 228 may be configured to learn that the filenames similar to the extracted filenames are likely intentional. In those cases, the adaption module 228 may be configured to refrain from recognizing such filenames as having the typographical error going forward. In an embodiment, if the user consistently sends attachments with certain words or phrases in filenames (e.g., "Proposal_v1"), the adaption module 228 may be configured to learn to expect and preserve the words or phrases while still correcting the typographical errors in the filename. In an embodiment, the adaption module 228 may also be configured to predict the potential typographical errors in the filenames based on the user's past patterns and common typographical errors in filenames. In an embodiment, the adaption module 228 may be configured to maintain a record of one or more of the suggested filenames, the received user inputs, and any manual override by the user. Thus, the present disclosure improves the performance of the disclosed system 108 in suggesting corrections in future scenarios, often even before the user finishes typing the complete filename. For example, if gibberish filenames are encountered, the system 108 can adjust its sensitivity based on previous interactions with the user. Thus, the present disclosure allows the disclosed system 108 to adapt and improve its performance based on the user's behaviour.
[0049] In an embodiment, the feedback module 230 may be configured to receive a feedback on the suggested filename being incorrect. In an embodiment, the feedback module 230 may be configured to receive the feedback when the user proposes the new filename. In an embodiment, the feedback module 230 may be configured to integrate the received feedback into a predefined machine learning model to avoid providing similar suggestions going forward, thereby allowing the system 108 to continuously improve and offer better suggestions based on the received user's inputs.
[0050] In an embodiment, the system 108 may be integrated with the email platforms through an Application Programming Interfaces (APIs) integration layer. In an embodiment, the system 108 may be implemented in a cloud-based infrastructure and/or across multiple user devices or platforms (e.g., desktop and mobile). Thus, if the user uses multiple user devices or platforms, the correction made to the filenames may be synchronized across all the user devices via the system's 108 cloud-based architecture. Thus, the present disclosure ensures consistency across multiple platforms, and the corrected filename is reflected in all instances of the email attachment. Further, the cloud-based infrastructure also allows scalability and rapid processing of large volumes of files, ensuring that the system 108 remains lightweight without consuming excessive local resources while providing fast detection and correction of the typographical error in the filename.
[0051] Figure 4 illustrates a flowchart depicting an exemplary method 400 for correcting the typographical error in the filename of the at least one attachment 304 for the draft of the email 302, in accordance with an embodiment of the present disclosure. The method 400 may be a computer-implemented method executed, for example, by the processor 202 and the module(s) 210. For the sake of brevity, constructional and operational features of the system 108 that are already explained in the description of Figure 1, Figure 2, and Figure 3, are not explained in detail in the description of Figure 4.
[0052] The method 400 may begin with step 402 which may include extracting, by the extraction module 214, the filename associated with the at least one attachment 304 from the draft of the email 302. In an embodiment, for extracting the filename associated with the at least one attachment 304, the method 400 may include identifying at least one attachment 304 added to the draft of the email 302, capturing a filename syntax from the at least one attachment 304, segregating the filename and the file extension from the captured filename syntax, and extracting the filename associated with the at least one attachment 304 based on the segregation. In an embodiment, the filename syntax may include the filename and a file extension associated with the captured filename syntax.
[0053] At step 404, the method 400 may include determining, by the spell-check module 216, the extracted filename having the typographical error using the one or more filename conventions. In an embodiment, for determining the extracted filename having the typographical error using the one or more filename conventions, the method 400 may include at least one of correlating, by the default language sub-module 220, the characters of the extracted filename with the characters of the one or more linguistic words stored in the default language dictionary, correlating, by the multi-language sub-module 222, the characters of the extracted filename with the characters of the one or more linguistic words stored in the multi-language dictionary based on the detection of a language of the filename, and correlating, by the contextual sub-module 224, the characters of the extracted filename with the characters of the pre-stored one or more contextual terminology relating to the identified file type using the NLP techniques. The method 400 may further include determining the typographical error in the extracted filename based on the correlation of the characters. In an embodiment, for determining the typographical error, by the spell-check module 216, based on the correlation of characters, the method 400 may include determination of at least one of the duplicated characters, the missing letters, the improper capitalization, the extra spaces, and the improper use of special characters.
[0054] At step 406, the method 400 may include suggesting the filename based on the determination of the typographical error in the extracted filename.
[0055] At step 408, the method 400 may include correcting, by the correction module 218, the typographical errors in the filename of the at least one attachment 304 for the draft of the email 302 based on the suggestion. In an embodiment, the method 400 may include applying, by the correction module 218, automatic corrections to the typographical errors in the filename based on the pre-configured set of rules or user preferences.
[0056] In an embodiment, the method 400 may include analyzing, by the extraction module 214, the segregated file extension to identify the file type associated with the at least one attachment 304.
[0057] In an embodiment, the method 400 may include initiating, by the prompt module 226, the prompt to receive the user input, based on the suggested filename, to at least one of accept the suggested filename, retain the extracted file name, and propose a new file name. In an embodiment, the method 400 may include triggering, by the prompt module 226, the initiation of the prompt to receive the user input on at least one of, addition of the at least one attachment to the draft of the email, and sending of the draft of the email.
[0058] In an embodiment, the method 400 may include refining, by the adaption module 228, the suggested filename using the at least one machine learning technique based on the user's behaviour and interaction patterns from the previously received user input for correcting the typographical errors in the filename. In an embodiment, the method 400 may include overriding, by the adaption module 228, the suggested filename with the refined suggested filename.
[0059] In an embodiment, the method 400 may include autocorrecting, by the adaption module 228, the typographical error in the filename based on the previously received user input.
[0060] In an embodiment, the method 400 may include receiving, by the feedback module 230, the feedback on the suggested filename being incorrect.
[0061] FIG. 5 illustrates a flowchart of an exemplary method 500 depicting a detailed outline for correcting the typographical error in the filename of the at least one attachment 304 for the draft of the email 302, in accordance with an embodiment of the present disclosure. The method 500 may be a computer-implemented method executed, for example, by the processor 202 and the module(s) 210. For the sake of brevity, the constructional and operational features of the system 108 that are already explained in the description of Figure 1, Figure 2, and Figure 3, are not explained in detail in the description of Figure 5.
[0062] The method 500 may begin with step 502 which may include an initiation of composition of the email 302 by the user. In an embodiment, the user may attach the at least one attachment 304 to the draft of the email 302. In one embodiment, for initiating the email composition and attaching at least one attachment 304 to the draft of the email 302, an exemplary pseudo-code is as follows:
DISPLAY "Compose Email"
FILE_TO_ATTACH = USER_SELECTS_FILE()
[0063] At step 504, the method 500 may include detecting, by the extraction module 214, whether the user has added the at least one attachment 304 to the draft of the email 302. If the extraction module 214 detects that the user has not added any attachment to the draft of the email 302, the method 500 may come to an end and the email 302 may be sent to the recipient without any attachment, at step 506. Alternatively, the extraction module 214 detects that the user has added the at least one attachment 304 to the draft of the email 302, the method 500 may proceed to step 508.
[0064] At step 508, the method 500 may include extracting, by the extraction module 214, the filename associated with the at least one attachment 304 from the draft of the email 302. In one embodiment, for extracting the filename associated with the at least one attachment 304, an exemplary pseudo-code is as follows:
FILENAME = EXTRACT_FILENAME(FILE_TO_ATTACH)
[0065] At step 510, the method 500 may include analyzing the extracted filename, by the spell-check module 216, to detect whether there is any typographical error in the extracted filename. The detailed description of Figure 3 and Figure 4 explains the detection of the typographical error in the extracted filename in detail, and the same has not been reproduced here for the sake of brevity. In one embodiment, for determining whether there is any typographical error in the extracted filename, an exemplary pseudo-code is as follows:
CORRECTED_FILENAME = SpellCheckAndAnalyze(FILENAME)
[0066] If the spell-check module 216 determines that there is no typographical error in the extracted filename, the method 500 may come to an end at step 506 and the email 302 may be sent to the recipient, where the extracted filename is used as the attachment's name. Alternatively, if the spell-check module 216 determines the typographical error in the extracted filename, the method 500 may proceed to step 512.
[0067] At step 512, the method 500 may include suggesting, by the prompt module 226, the filename based on the determination of the typographical error in the extracted filename. In an embodiment, the spell-check module 216 may be configured to provide the suggested filename to the prompt module 226 for presenting to the user through the UI, as explained above in conjunction with Figure 3 and Figure 4. In an embodiment, the method 500 may also include initiating, by the prompt module 226, the prompt to receive the user input, based on the suggested filename, to at least one of accept the suggested filename, retain the extracted filename, and propose the new file name. In one embodiment, for suggesting the filename based on the determination of the typographical error in the extracted filename and initiating the prompt to receive the user input based on the suggested filename, an exemplary pseudo-code is as follows:
SUGGEST_CORRECTION
PROMPT_USER_FOR_APPROVAL
[0068] At step 514, the method 500 may include analyzing the user input to determine whether the user decided to accept the suggested filename, retain the extracted filename, or proposed the new filename. If the user chooses to retain the extracted filename, the method 500 may come to an end and the email 302 may be sent to the recipient with the extracted filename as the attachment's name, at step 506. Alternatively, if the user accepts the suggested filename, the method 500 may move to step 516. At step 516, the method may include replacing, by the correction module 218, the extracted filename with the suggested filename. Thereafter, the method 500 may come to an end and the email 302 may be sent to the recipient with the suggested filename as the attachment's name, at step 506. Additionally, if the user chooses to manually override the extracted filename, the method 500 may move to step 516. At step 516, the method 500 may include replacing the extracted filename with the new filename received from the user via the UI, as explained above in conjunction with Figure 3. Thereafter, the method 500 may come to an end and the email 302 may be sent to the recipient with the new filename as the attachment's name, at step 506. In one embodiment, for correction or retention of the extracted filename based on the user input, an exemplary pseudo-code is as follows:
IF correctionNeeded THEN
USER_APPROVAL=PROMPT_USER_FOR_APPROVAL(correctedFilename)
IF USER_APPROVAL == "approve" THEN
RETURN correctedFilename
ELSE
RETURN filename
END IF
ELSE
RETURN filename
END IF
END FUNCTION
[0069] The disclosed pseudo-codes outline the step-by-step process for implementing an embodiment of the present invention, detailing how the present disclosure achieves the automatic detection and correction of the typographical errors in the filenames of the email attachments before transmission to the recipient thereby improving the user experience.
[0070] In various embodiments, the present disclosure at least provides advantages such as enhancing professionalism, avoiding confusion due to erroneous filenames, and streamlining file management by ensuring consistent and accurate naming conventions. More preferably, the present disclosure provides the following advantages:
a) The present disclosure provides the automatic detection and correction of the typographical errors in the filenames thereby saving the user's time by eliminating the need for manual reviewing of the filenames, thereby ensuring a more efficient workflow.
b) The present disclosure uses the NLP techniques and contextual analysis, thereby ensuring that the filenames are both accurate and meaningful, and improving overall communication efficacy.
c) The present disclosure offers real-time detection and correction of the typographical error, thereby reducing the cognitive load on users. Thus, the present disclosure significantly minimizes interruptions in the workflow, allowing the users to focus on content rather than worrying about the accuracy of filenames. Further, the present disclosure ensures anticipation of common typographical errors based on the user's patterns and suggests corrections even before the file is sent, thereby preventing issues proactively.
d) The present disclosure supports multi-language dictionaries and contextual learning, thereby allowing the detection and correction of the typographical errors in the filenames written in different languages.
e) The present disclosure significantly increases the efficiency of the automatic detection and correction of the typographical errors in the filenames over time, as the adaption module 228 adapts to the user's specific naming conventions, thereby improving accuracy in suggesting correct filenames.
f) The present disclosure ensures that the filenames are correct from the point of email attachment, thereby improving the long-term document organization and retrieval. Thus, the present disclosure improves productivity in environments where document management is a critical part of daily operations.
g) The present disclosure ensures that the detection and correction of the typographical errors in the filenames happen within a secure environment. Particularly, the present disclosure ensures that all filename processing is conducted locally or within secure cloud services, with no access to the file's content. The present disclosure ensures that only the filenames are processed, thereby ensuring privacy and compliance with data protection regulations.
[0071] Therefore, the present not only provides numerous advantages, but also overcomes numerous drawbacks related to the correction of the attachment filenames by operating in real-time, offering suggestions or automatic corrections, while providing the user the option to approve or override the suggested filenames. Further, by automating the detection and correction of the typographical errors in the filenames, the present disclosure may improve email efficiency and reduce human error related to attachment filenames, thereby providing an intelligent and automated solution.
[0072] Further, the present disclosure for correcting the typographical error in the filename of the at least one attachment 304 for the draft of the email 302 has various potential applications across different domains and industries.
[0073] In various embodiments, the present disclosure may be implemented in various sectors such as personal email management, corporate, project management software, document sharing platforms, legal and financial services, customer relationship management (CRM) systems, cloud storage solutions, mobile applications, automated workflow systems, e-commerce platforms, healthcare systems, research and academic institutions, digital marketing tools, and artificial intelligence and machine learning models. However, the implementation of the present disclosure in the above-mentioned sectors should not be construed as a limitation of the present disclosure. The implementation of the present disclosure in the abovementioned sectors and the application are discussed in the below paragraphs.
[0074] Personal Email Management: The present disclosure may enable integration of the disclosed auto-correction feature into popular email clients thereby significantly enhancing user experience by ensuring that the attachments being shared are appropriately named.
[0075] Corporate: In corporate environments, where email communication is vital for collaboration and information sharing, the present disclosure may ensure professionalism and reduce errors in document sharing.
[0076] Project Management Software: In project management software, where the users frequently attach files, the present disclosure may ensure that document names are clear, making it easier for teams to locate and identify the shared documents.
[0077] Document Sharing Platforms: In the document sharing platforms, the present disclosure may ensure that the users upload files with correctly formatted and meaningful names thereby making it easier for them to retrieve the files later.
[0078] Legal and Financial Services: In law firms and financial institutions, the present disclosure may benefit the document management systems by ensuring that sensitive documents are accurately named, thereby further preventing miscommunication and maintaining compliance.
[0079] CRM Systems: The CRMs can utilize the present disclosure to ensure that the files uploaded to the client profiles or records are correctly named. Thus, the present disclosure may help the CRMs in keeping organized records and accordingly improving data management.
[0080] Cloud Storage Solutions: The present disclosure may significantly benefit the cloud storage services by offering their users the ability to automatically correct filenames upon upload, thereby ensuring that the files are stored with clear, professional names for easy retrieval.
[0081] Mobile Applications: The present disclosure may be integrated with mobile applications for emailing and file management thereby enabling the users with real-time filename correction on-the-go.
[0082] Automated Workflow Systems: The present disclosure may significantly benefit the workflow automation platforms by ensuring that any documents generated or shared through automated processes have correct filenames.
[0083] E-commerce Platforms: The present disclosure may be implemented in the e-commerce sites to help sellers maintain consistent and correct filenames for product images and documents, thereby enhancing the clarity and professionalism of listings.
[0084] Healthcare Systems: In healthcare institutions, the present disclosure may be implemented in their systems to ensure that patient-related documents have accurate filenames, thereby improving the organization of medical records.
[0085] Research and Academic Institutions: The present disclosure may be implemented in academic submission systems to ensure that students submit their assignments, theses, or dissertations with correctly formatted filenames, thereby promoting professionalism and reducing confusion for educators when grading.
[0086] Digital Marketing Tools: The present disclosure may be implemented within content management system (CMS) platforms to ensure that documents and content are correctly named, thereby facilitating better search engine optimization practices and content organization.
[0087] Artificial Intelligence (AI) and Machine Learning Models: The present disclosure may be implemented in AI training tools to ensure that datasets uploaded for model training have correctly formatted filenames, which is crucial for model accuracy and data management.
[0088] Therefore, the present disclosure spans across various sectors and scenarios where efficient detection and correction of the typographical errors in filename of the at least one attachment enhances communication, improves organization, and reduces errors in file management and sharing processes.
[0089] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device or a combination of hardware devices and software modules.
[0090] It is understood that terms including "unit" or "module" at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.
[0091] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0092] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.
[0093] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.
[0094] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.
[0095] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
, Claims:1. A method (400) for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email), the method (400) comprising:
extracting (402), by an extraction module (214), a filename associated with the at least one attachment from the draft of the email;
determining (404), by a spell-check module (216), the extracted filename having a typographical error using one or more filename conventions;
suggesting (406) a filename based on the determination of the typographical error in the extracted filename; and
correcting (408), by a correction module (218), the typographical error in the filename of the at least one attachment for the draft of the email based on the suggestion.
2. The method (400) as claimed in claim 1, wherein extracting the filename associated with the at least one attachment comprises:
identifying at least one attachment added to the draft of the email;
capturing a filename syntax from the at least one attachment, wherein the filename syntax comprises the filename and a file extension associated with the captured filename syntax;
segregating the filename and the file extension from the captured filename syntax; and
extracting the filename associated with the at least one attachment based on the segregation.
3. The method (400) as claimed in claim 1, comprising analyzing, by the extraction module (214), the segregated file extension to identify file type associated with the at least one attachment.
4. The method (400) as claimed in claim 1, wherein determining the extracted filename having the typographical error using the one or more filename conventions comprises at least one of:
correlating, by a default language sub-module (220), the characters of the extracted filename with characters of one or more linguistic words stored in a default language dictionary;
correlating, by a multi-language sub-module (222), the characters of the extracted filename with characters of one or more linguistic words stored in a multi-language dictionary based on detection of a language of the filename; and
correlating, by a contextual sub-module (224), the characters of the extracted filename with characters of a pre-stored one or more contextual terminology relating to the identified file type using natural language processing (NLP) techniques; and
determining the typographical error in the extracted filename based on the correlation of the characters.
5. The method (400) as claimed in claim 4, wherein determining, by the spell-check module (216), the typographical error based on the correlation of characters comprises determination of at least one of duplicated characters, missing letters, improper capitalization, extra spaces, and improper use of special characters.
6. The method (400) as claimed in claim 1, comprising initiating, by a prompt module (226), a prompt to receive a user input, based on the suggested filename, to at least one of accept the suggested filename, retain the extracted file name, and propose a new file name.
7. The method (400) as claimed in claim 6, comprising refining, by an adaption module (228), the suggested filename using at least one machine learning technique based on user behaviour and interaction patterns from previously received user input for correcting the typographical errors in the filename.
8. The method (400) as claimed in claim 7, comprising autocorrecting, by the adaption module (228), the typographical error in the filename based on the previously received user input.
9. The method (400) as claimed in claim 7, comprising overriding, by the adaption module (228), the suggested filename with the refined suggested filename.
10. The method (400) as claimed in claim 6, comprising triggering, by the prompt module (226), the initiation of the prompt to receive the user input on at least one of, addition of the at least one attachment to the draft of the email, and sending of the draft of the email.
11. The method (400) as claimed in claim 1, comprising receiving, by a feedback module (230), feedback on the suggested filename being incorrect.
12. The method (400) as claimed in claim 1, comprising applying, by the correction module (218), automatic corrections to the typographical errors in the filename based on a pre-configured set of rules or user preferences.
13. A system (200) for correcting a typographical error in a filename of at least one attachment for a draft of an electronic mail (email), the system (200) comprising:
an extraction module (214) configured to extract a filename associated with the at least one attachment from the draft of the email;
a spell-check module (216) configured to determine the extracted filename having a typographical error using one or more filename conventions, wherein the spell-check module is configured to suggest a filename based on the determination of the typographical error in the extracted filename; and
a correction module (218) configured to correct the typographical error in the filename of the at least one attachment for the draft of the email based on the suggestion.
14. The system (200) as claimed in claim 13, wherein the extraction module (214), for extraction of the filename associated with the at least one attachment, is configured to:
identify at least one attachment added to the draft of the email;
capture a filename syntax from the at least one attachment, wherein the filename syntax comprises the filename and a file extension associated with the captured filename syntax;
segregate the filename and the file extension from the captured filename syntax; and
extract the filename associated with the at least one attachment based on the segregation.
15. The system (200) as claimed in claim 13, wherein the extraction module (214) is configured to analyze the segregated file extension to identify file type associated with the at least one attachment.
16. The system (200) as claimed in claim 13, wherein the spell-check module (216), for determination of the extracted filename having the typographical error using the one or more filename conventions, comprises:
a default language sub-module (220) configured to correlate the characters of the extracted filename with characters of one or more linguistic words stored in a default language dictionary;
a multi-language sub-module (222) configured to correlate the characters of the extracted filename with characters of one or more linguistic words stored in a multi-language dictionary based on detection of a language of the filename; and
a contextual sub-module (224) configured to correlate the characters of the extracted filename with characters of a pre-stored one or more contextual terminology relating to the identified file type using natural language processing (NLP) techniques; and
wherein the spell-check module (216) is configured to determine the typographical error in the extracted filename based on the correlation of the characters.
17. The system (200) as claimed in claim 16, wherein the spell-check module (216), while determination of the typographical error based on the correlation of characters, is configured to determine at least one of duplicated characters, missing letters, improper capitalization, extra spaces, and improper use of special characters.
18. The system (200) as claimed in claim 13, comprising a prompt module (226) configured to initiate a prompt to receive a user input, based on the suggested filename, to at least one of accept the suggested filename, retain the extracted file name, and propose a new file name.
19. The system (200) as claimed in claim 18, comprising an adaption module (228) configured to refine the suggested filename using at least one machine learning technique based on user behaviour and interaction patterns from previously received user input for correcting the typographical errors in the filename.
20. The system (200) as claimed in claim 19, wherein the adaption module (228) is configured to autocorrect the typographical error in the filename based on the previously received user input.
21. The system (200) as claimed in claim 19, wherein the adaption module (228) is configured to override the suggested filename with the refined suggested filename.
22. The system (200) as claimed in claim 18, wherein the prompt module (226) is configured to trigger the initiation of the prompt to receive the user input on at least one of, addition of the at least one attachment to the draft of the email, and sending of the draft of the email.
23. The system (200) as claimed in claim 13, comprising a feedback module (230) configured to receive a feedback on the suggested filename being incorrect.
24. The system (200) as claimed in claim 13, wherein the correction module (218) is configured to apply automatic corrections to the typographical errors in the filename based on a pre-configured set of rules or user preferences.

Documents