Skip to content
This repository was archived by the owner on May 13, 2025. It is now read-only.
This repository was archived by the owner on May 13, 2025. It is now read-only.

tex, markup, build, doc not found in FileInfo's A_metadata.U #41

Open

Description

@MohammadEglil

When I have a look at the a2L script, there is a key for for tex, markup, build or doc but when I would have a look at author metadata collection (A_metadata.U) in on the Mongo database, there are not such keys in FileInfo. For example, if I run echo 'soumith <soumith@fb.com>' | ~/lookup/getValues A2f there are clearly Markdown, pdf, text files etc. but there aren't these before mentioned keys so can we assume there are in the key 'other'?

Activity

  1. changed the title [-]tex, markup, build, doc[/-] [+]tex, markup, build, doc not found in FileInfo's A_metadata.U[/+] on Dec 28, 2022
  2. audrism commented on Dec 28, 2022

    @audrism
    Collaborator

    The extensions for mongodb A_metadata.U and P_metadata.U are categorized in
    AuthSummary.perl and
    prjSummary.perl: see function ext.

    So yes, tex/md are "other". Should additional types be added? if so which?

  3. MohammadEglil commented on Dec 28, 2022

    @MohammadEglil
    Author

    Thank you for the clarifications...in my analysis contributors tend to have around 60 percent of 'other' which is not really insightful. I would appreciate it if the keys in the a2L script would be added to A_metadata.U.

  4. audrism commented on Dec 28, 2022

    @audrism
    Collaborator

    That 60% is not programming languages, however. Why break it down?

  5. MohammadEglil commented on Dec 28, 2022

    @MohammadEglil
    Author

    I am sure some people would like to know the stats on html and css files changed. For me, I am interested in documentation practices so therefore I would like to know the files changed in markdown and maybe txt files.

  6. audrism commented on Dec 29, 2022

    @audrism
    Collaborator

    Is the list of extensions in a2L comprehensive/accurate or are there some improvements you can suggest?

  7. MohammadEglil commented on Dec 29, 2022

    @MohammadEglil
    Author

    I would definitely suggest to have a separate key for html and a separate key for css, other than that it looks fine to me.

  8. self-assigned this
    on Sep 28, 2024
  9. loconous commented on Sep 28, 2024

    @loconous
    Collaborator

    @MohammadEglil, could you verify if this issue is still relevant? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions